Part II – Data Loading and Tabulation Master Files
- Canadian Cancer Registry Overview
- CCR System Guide Document Organization
- Part II Document organization – Data Loading and TMF
- Changes to the CCR Data Loading and TMF for the 2009 and 2010 Reference Years
Changes to the CCR Data Loading and TMF for the 2007 and 2008 Reference Years
- Statistics Canada Contacts
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.
The CCR System Guide has been separated into three parts to improve access and navigation. Although the three parts are separate, the three documents should be used in conjunction with each other. The different sections of the three-part CCR System Guide often refer to each other. The CCR System Guide is now composed of:
Part I: CCR Data Dictionary provides explanation on the reporting of data, including the scope and detailed information on the input and derived variables.
Part II: CCR Data Loading and Tabulation Master Files provides information on the data loading process, including in-depth descriptions of the various edits performed on the data. Part II also provides information on the Tabulation Master Files, including the scope, content and layout. Part II is followed by several appendices that contain sup
porting information such as explicit code set tables, guidelines to assist coders and other supportive information.
Part III: CCR Core Reference Tables provides detailed information on the CCR Core Reference Tables such as descriptions of the tables, their usage and any revisions made. Part III is an accompanying document to the Core Reference Tables 2010.xls.
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.
Please refer to the relevant section in the System Guide – Data Loading and TMF for more details related to these changes.
Section |
Item (s) |
Description of change |
Effective (reference year |
---|
3.3.1 |
Table 21 Impact of data formatting step on patient data items |
New variables added – P20, P21 |
2010 |
---|
3.3.1 |
Table 22 Impact of data formatting step on tumour data items |
New variables added – T58 – T87, change in name for variables T31 and T52, , change in length of variables T24 and T25 and they are now left justified. |
2010 |
---|
3.4.1 |
PVAL20, PVAL21 |
New edits added for Date of birth flag, Date of death flag |
2010 |
---|
3.3.1, 3.4.2,4.3 |
Table 22, Table 25, TVAL27-TVAL41, TVAL52, TCOR1, and TCOR18, Table 36 - TMF record layout |
Variable Names changed - CS version 1st to CS version input original (acronym changed from TCSFVER to TCSVERINORIG), CS reg nodes eval to CS lymph nodes eval (acronym changed from TCSRNEVAL to TCSLNEVAL). |
2010 |
---|
3.4.2, 3.5.2, 4.3 |
TVAL27-TVAL41, TCOR1, TCOR18, Table 36 - TMF record layout |
Length of CS Extension and CS lymph nodes has been changed from 2 to 3. |
2010 |
---|
3.4.2 |
TABLE 25 |
New edits added TVAL58 – TVAL83 |
2010 |
---|
3.4.2 |
TVAL24, TVAL25 |
Edits updated for new code Positive histology PLUS (10) |
2010 |
---|
3.4.2 |
TVAL58 – TVAL60 |
New edits added for Date of diagnosis flag, Date of conclusive diagnosis flag, and Date of multiple tumours flag |
2010 |
---|
3.4.2 |
TVAL42 – TVAL51 |
Edits no longer applicable (AJCC variables no longer reported) |
2009 |
---|
3.4.2, 3.5.2 |
TVAL65-TVAL83, TCOR1, TCOR18 |
New edits added, and edits modified for new site-specific factors 7 - 25 |
2010 |
---|
3.4.2, 3.5.2 |
TVAL61, TVAL62, TCOR36, TCOR37 |
New edits added for new variables T61 Grade path value and T62 Grade path system |
2010 |
---|
3.4.2 |
TVAL27-TVAL41, TVAL52 |
CS version input current added to edits |
2010 |
---|
3.4.2 |
TVAL64 |
New edit added for new variable T64 CS version input current |
2010 |
---|
3.4.2 |
TVAL63 |
New edit added for new variable T63 Lymph-vascular invasion |
2010 |
---|
3.4.2 |
TVAL84 – TVAL87 |
New edits added for new variables T84 CS Mets at Dx – bone, T85 – CS Mets at Dx Brain, T86 – CS Mets at Dx Liver, T87 – CS Mets at Dx Lung |
2010 |
---|
3.5.1 |
PCOR1 |
New variables added P20, P21 |
|
---|
3.5.2 |
TCOR1 |
New variables added – T58 – T83, change in name for variables T31 and T52. Change in length of the variables T24, T25, T28, T30. |
2010 |
---|
3.5.2 |
TCOR13 |
New sub-edits added and existing edits modified to account for new code 10 - Positive histology plus added to Method used to establish date of diagnosis and Diagnostic confirmation |
|
---|
3.5.2 |
TCOR19-TCOR24 |
Edits no longer applicable (AJCC variables no longer reported) |
2009 |
---|
3.5.2 |
TCOR34 |
Business rules and edit logic changed : Modified to accept additional combinations. |
2008 |
---|
3.7.1, 3.7.3 |
Add/Update patient record processing |
New variables added: Core data items P20 and P21 |
2010 |
---|
3.7.2. 3.7.4 |
Add/Update tumour record processing |
New variables added: Core data items T53 to T63, T84 to T87, and CS data items T64 to T83. |
2010 |
---|
4.2.2 |
Table 35 Algorithm used to eliminate duplicate tumours from IARC TMF |
Behaviour/site ranking to take precedence for duplicate tumours |
2008 |
---|
4.2.2 |
New table : Table 35b |
Ranking of behaviour to identify the most 'malignant' tumour: |
2008 |
---|
4.3 |
Table 36 TMF record layout modified |
Variables were renamed, changed in length and new variables added. There was also a re-order in the table affecting some positions of variables. |
2010 |
---|
Appendix D |
Appendix D - Multiple primary tumour rules for CCR |
Laterality codes changed and were modified for all years. |
2007 (changed in guide 2010) |
---|
Appendices |
Appendix K |
Flavours of null table |
2010 |
---|
Table
Changes to the CCR Data Loading and TMF for the 2007 and 2008 Reference Years
Step 2: Core data items validation |
New validation edits added, TVAL53-57 |
2008 |
Step 7: CS data items validation |
New validation edit TVAL52 added in to step |
2007 |
CS fatal error |
CS data item T52 added |
2007 |
CS error |
CS data item T52 added |
2007 |
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 |
Validation Edits –
PVAL6
PVAL7
PVAL8
PVAL9
PVAL13 |
Business rules changed – acceptable accented characters specified |
2007 |
Tumour validation edits – Table 25 |
New Tumour validation edits – TVAL53, TVAL54, TVAL55, TVAL56, TVAL57 |
2008 |
New Tumour validation edit – TVAL52 |
2007 |
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 |
Tumour validation edits –TVAL8 |
Business rules, Edit logic and Feedback report messages added – SGC 2006 |
2006 |
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 |
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 |
Tumour validation edits –
TVAL52 |
New validation edit added |
2007 |
Tumour validation edits –
TVAL53
TVAL54
TVAL55
TVAL56
TVAL57 |
New validation edits added |
2008 |
Tumour correlation edits – Table 27 |
New correlation edits – TCOR26, TCOR27 |
2008 |
Tumour correlation edits – Table 27 |
New correlation edits – TCOR13 |
2007 |
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 |
Tumour correlation edits – TCOR3 |
Business rules and Edit logic changed: includes combinations where census tract indicates area outside CMA |
2006 |
Tumour correlation edits – TCOR10
TCOR11 |
Referenced fields, Business rules, Edit logic and Feedback report messages changed: Verification now includes Date of diagnosis. |
2007 |
Tumour correlation edits – TCOR13 |
New correlation edit added |
2007 |
Tumour correlation edits – TCOR18 |
Referenced fields and Edit logic updated: T52 added as a new CS variable |
2007 |
Tumour correlation edits – TCOR26, TCOR27, TCOR29 – TCOR35 |
New correlation edits |
2008 |
Data item match edits –
DIM6 |
Revision – Edit no longer used after 2006 |
2006 |
Add tumour record processing – CS data items |
Added new data item T52 |
2007 |
Patient derived variable calculation |
PD7 – Name of variable changed |
2007 |
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 |
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 |
Table 37 – Derived variable calculations at TMF time |
PD2 – Vital status now derived at TMF time |
2007 |
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.
PTCRs employees are encouraged to bring forward any questions by contacting one of the following:
For additional information regarding the processing of CCR data, please contact:
Colette Brassard
Section Chief
Operations and Integration Division
Statistics Canada
Tel: 613-951-7282
Fax: 613-951-0709
For any subject matter related questions/queries, please contact:
Kim Boyuk
Chief, Cancer Statistics
Health Statistics Division
Statistics Canada
Tel: 613-951-2510
Fax: 613-951-0792
Hollie Anderson
Manager, Canadian Cancer Registry
Health Statistics Division
Statistics Canada
Tel: 613-951-0757
Fax: 613-951-0792
- Data importing
- Data conditioning
- Data editing
- Data posting
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
expr1 AND expr2
The expression is true if and only if both expr1 and expr2 are true, otherwise the expression is false. |
expr1 OR expr2
The expression is true whenever expr1 or expr2 is true, otherwise the expression is false. |
NOT expr1
The expression is true only if it does not equal expr1, otherwise the expression is false. |
Table 15
Comparison operators
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. |
Expr1 BETWEEN (expr2, expr3)
Assesses whether expr1 is greater than or equal to expr2 and less than or equal to expr3. |
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
AVERAGE (X1, X2, ..., Xn)
Returns the arithmetic mean of X: X1+X2+...+Xn / n. This function ignores NULL values. |
BLANK(x1)
Returns x1 blank character(s). |
CALCULATE_CCR_CHECK_DIGIT (str1)
Returns a CCR_ID check digit based on str1. |
CONTAINS_WORD (str1, str2, x1)
Assesses whether str1 contains a word of at least x1 character(s) from str2. |
IS_COMPOSED_OF (str1, str2)
Assesses whether str1 is only composed of characters from str2. |
IS_VALID_DATE (str1)
Assesses whether str1 is a calendar date. |
LENGTH (str1)
Returns the length of str1 including trailing blanks. |
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
str1 || str2
Returns a unique string containing str1 and str2 concatenated (juxtaposed). |
Table 18
Set operators and symbols
[Expr1,...]
[A-Z]
[A]
Indicates an explicit list of values, a range of values or set of values known as Set A. |
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:
- Validation edits: Enforce business rules on each individual field.
- Correlation edits: Enforce business rules between valid fields on the same input record.
- 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
Patient validation (PVAL) |
Enforce business rules on Patient fields. |
Tumour validation (TVAL) |
Enforce business rules on Tumour fields. |
Patient correlation (PCOR) |
Enforce business rules between valid Patient fields. |
Tumour correlation (TCOR) |
Enforcebusiness rules between valid Tumour fields. |
Key input match (KIM) |
Ensure that Input patient and Tumour records respect the submission rules in terms of matching keys. |
Key base match (KBM) |
Ensure that Input patient and Tumour records respect the actual state of the CCR in terms of matching keys. |
Data item match (DIM) |
Enforce the business rules between data items (other than keys) found on different records. |
Pre–posting match (PPM) |
Identify error–free4 Input records that cannot be posted to CCR because some other related Input records are either missing or in error. |
3.1.5 Edits order of execution and edit control
Because of the dependencies between the edits, edit processing must respect a given order of execution. Since CS and AJCC <abbr title="Tumour, Node, Metastases">TNM</abbr> data item edits depend on core data items, core data item edits must be done first. For each of the following steps, the number of eligible input records will depend on the outcome of preceding steps.
Step 1: Core data items minimum requirements assessment
The core data items minimum requirements consist of an Input record with a valid record type and date of transmission and no missing core data items (P1-P19 or T1-T26). The following edits must be successful in order to respect the minimum requirements:
- Patient records: PCOR1, PVAL4 and PVAL19.
- Tumour records: TCOR1, TVAL5 and TVAL26.
Step 2: Core data items validation
Remaining core data items validation edits (PVAL1-19, TVAL1-26 and TVAL53-57) can be performed on the Input records that respect the core data items minimum requirements. The following order must be respected:
- PVAL11 before PVAL12;
- PVAL14 before PVAL15 and PVAL17;
- TVAL12 before TVAL8 and TVAL9;
Step 3: Core data items correlation, key input match and key base match edits
These edits are run based on the outcome of the core data item validation edits. That is, for a given edit, only the Input records where all referenced fields have been successfully validated are eligible. (This implies that Input records that do not respect the minimum requirements or that fail a required field validation edit are not eligible.) These edits can be run in any order.
Step 4: Core data item match edits
Those edits can only be performed on Input records that have no core data items errors. A special processing order must be respected. See Section 3.6.3 Data Item Match Edits for details.
Step 5: Core data items pre-posting match edits
Those edits can only be performed on Input records that have no core data items errors. These edits can be run in any order.
Step 6: CS data items minimum requirements assessment
CS data items minimum requirements consist of an input tumour record with valid date of diagnosis and no missing CS data items. The following edit must be successful in order to respect the minimum requirements:
Tumour records: TCOR18.
Step 7: CS data items validation
CS Validation edits (TVAL27 to 41 and TVAL52) can be performed on the input tumour records that respect the CS minimum requirements and where all core referenced fields are valid. These edits can be run in any order.
Step 8: AJCC TNM data items minimum requirements assessment
AJCC TNM data items minimum requirements consist of an input tumour record with valid date of diagnosis, ICD-O-2/3 topography, ICD-O-3 histology and ICD-O-3 behaviour and no missing AJCC TNM data items. The following edit must be successful in order to respect the minimum requirements SITE-SPECIFIC MEANING: Tumour records: TCOR19.
Step 9: AJCC TNM data items validation
AJCC TNM validation edits (TVAL42 to 51) can be performed on the input tumour records that respect the AJCC TNM minimum requirements and where all core referenced fields are valid. These edits can be run in any order.
Step 10: AJCC TNM data items correlation
These edits are run based on the outcome of previous validation edits. That is, for a given edit, only the Input records where all referenced fields (core and AJCC TNM) have been successfully validated are eligible. These edits can be run in any order.
See section 3.1.9 flowchart of the data loading process for an illustration of the edits dependencies.
3.1.6 Sub-edits order of execution
Except for data item match Sub-edits; all sub-edits from a given edit may be performed in any order. See Section 3.6.3.1 Special order of execution for more details about data item match Sub-edits special order of execution.
3.1.7 Message types
The severity of an error is expressed by its corresponding message's type. The following list describes each possible message type and gives an indication of when they are issued and how they change the editing process flow.
Fatal error: When a group of data items does not respect the minimum requirements. Related editing is stopped.
Core fatal error: Core data items (P1 to P21 and T1 to T26) (except T5 – Input record type), T53 to T63, and T84 to T87) do not respect the minimum requirements. The input record will not undergo any other edits and will be rejected.
CS fatal error: CS data items (T27 to T41 and T52 (CSV1) OR T27 to T41,T52 and T64 to T83 (CSV2))do not respect the minimum requirements. CS data items will not undergo any other related edits and will not be loaded on the CCR database. CS Fatal error does not prevent valid core and AJCC TNM data items from being loaded on the CCR database.1
AJCC TNM Fatal error: AJCC TNM data items (T42 to T51) do not respect the minimum requirements. AJCC TNM data items will not undergo any other related edits and will not be loaded on the CCR database. AJCC TNM fatal error does not prevent valid core and CS data items from being loaded on the CCR database.5
Error: Normal edits failure. Editing is not stopped. Unless specified otherwise, the input record can be edited by other edits based on the validity of their corresponding referenced fields.
Core error: Error found in core patient (P1 to P21) or Tumour (T1 to T26) data items. Core error causes the Input record to be rejected.
CS error: Error found in CS data items (T27 to T41 and T52 (CSV1) OR T27 to T41, T52 and T64 to T83 (CSV2))). CS data items will not be loaded on the CCR database.CS error does not prevent valid core and AJCC TNM data items from being loaded on the CCR database.5
AJCC TNM error: Error found in AJCC TNM data items (T42 to T51). AJCC TNM data items will not be loaded on the CCR database. AJCC TNM error does not prevent valid core and CS data items from being loaded on the CCR database.5
Warning: Informative message to PTCR. Warnings do not prevent Inputrecords from being loaded on the CCR.
3.1.8 Edit description pages
For ease of use, each edit is described using a standard format: name, purpose, referenced fields, business rules, edit logic and feedback report messages. When needed, other parameters, revisions and notes are also added to give more detail. The following table describes each possible section.
Table 20
Edit presentation breakdown
A unique name for the edit. |
Edit main purpose. |
List of all input file fields (or part of fields) involved in the edit. |
List of additional parameters needed to perform the edit. |
Rules that describe the eligible field value or relationship between many field values. These rules are written in plain English. |
Each Sub-edit condition that identifies invalid records. These conditions are usually written using logical expressions. |
List of all possible edit messages. |
List of all changes that have been applied to the edit over time. |
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.
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.
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:
- Data formatting;
- Old classification filtering;
- ICD-O-2/3 topography calculation;
- ICD-O-3 histology and behaviour calculation; and,
- Laterality adjustment.
The steps listed above must be executed in sequential order. Each step may alter the reported data. Refer to the corresponding section below for a description of how these reported data are altered.
3.3.1 Data formatting
Description
Data formatting is composed of three operations:
Left justified: Removes blank character preceding the data item value.
Uppercase: Converts all lower case alphabetic characters to uppercase letters.
Converts lower case French accents (é, è, ê, ë, ç…) to corresponding uppercase letters (é à É). Special characters and digits remain unchanged.
Removal of trailing blanks: Removes any blank characters trailing the data item value. Data items containing only blank characters will be converted to NULL. This is an important assumption used in the data editing phase.
Purpose
Data formatting reduces PTCR response burden by fixing small formatting errors that would otherwise cause an input record to be rejected. It also converts blank data items to NULL values in order to be compliant with the data editing specification.
Logic
- Left justification is applied on any fields longer than 1 character.
- Uppercase is applied on any fields that may contain letters.
- Removal of trailing blanks is applied on all fields.
The following two tables summarize the impact of the data formatting step on patient and tumour data items. X and – indicate whether the corresponding transformation is applicable or not.
Table 21
Impact of data formatting step on patient data items
Patient reporting province/territory |
X |
- |
X |
Patient identification number |
X |
X |
X |
CCR identification number |
X |
- |
X |
Patient record type |
- |
- |
X |
Type of current surname |
- |
- |
X |
Current surname |
X |
X |
X |
First given name |
X |
X |
X |
Second given name |
X |
X |
X |
Third given name |
X |
X |
X |
Sex |
- |
- |
X |
Date of birth |
X |
- |
X |
Province/territory or country of birth |
X |
- |
X |
Birth surname |
X |
X |
X |
Date of death |
X |
- |
X |
Province/territory or country of death |
X |
- |
X |
Death registration number |
X |
- |
X |
Underlying cause of death |
X |
X |
X |
Autopsy confirming cause of death |
- |
- |
X |
Patient date of transmission |
X |
- |
X |
Date of birth flag |
X |
- |
X |
Date of death flag |
X |
- |
X |
Table 22
Impact of data formatting step on tumour data items
Tumour reporting province/territory |
X |
- |
X |
Tumour patient identification number |
X |
X |
X |
Tumour reference number |
X |
X |
X |
CCR identification number |
X |
- |
X |
Tumour record type |
- |
- |
X |
Name of place of residence |
X |
X |
X |
Postal code |
X |
X |
X |
Standard geographic code |
X |
- |
X |
Census tract |
X |
- |
X |
Health insurance number |
X |
X |
X |
Method of diagnosis |
- |
- |
X |
Date of diagnosis |
X |
- |
X |
ICD–9 cancer code |
X |
- |
X |
Source classification flag |
- |
- |
X |
ICD–O–2/3 Topography |
X |
X |
X |
ICD–O–2 Histology |
X |
- |
X |
ICD–O–2 Behaviour |
X |
- |
X |
Filler |
- |
- |
- |
Laterality |
- |
- |
X |
Filler |
- |
- |
- |
ICD–O–3 Histology |
X |
- |
X |
ICD–O–3 Behaviour |
- |
- |
X |
Grade, differentiation or cell indicator |
- |
- |
X |
Method used to establish the date of diagnosis |
X |
- |
X |
Diagnostic confirmation |
X |
- |
X |
Date of transmission |
X |
- |
X |
CS tumour size |
X |
- |
X |
CS extension |
X |
- |
X |
CS tumour size/ext eval |
- |
- |
X |
CS lymph nodes |
X |
- |
X |
CS lymph nodes eval |
- |
- |
X |
Regional nodes examined |
X |
- |
X |
Regional nodes positive |
X |
- |
X |
CS mets at dx |
X |
- |
X |
CS mets eval |
- |
- |
X |
CS site-specific factor 1 |
X |
- |
X |
CS site-specific factor 2 |
X |
- |
X |
CS site-specific factor 3 |
X |
- |
X |
CS site-specific factor 4 |
X |
- |
X |
CS site-specific factor 5 |
X |
- |
X |
CS site-specific factor 6 |
X |
- |
X |
AJCC clinical T |
X |
X |
X |
AJCC clinical N |
X |
X |
X |
AJCC clinical M |
X |
X |
X |
AJCC pathologic T |
X |
X |
X |
AJCC pathologic N |
X |
X |
X |
AJCC pathologic M |
X |
X |
X |
AJCC clinical TNM stage group |
X |
X |
X |
AJCC pathologic TNM stage group |
X |
X |
X |
AJCC TNM stage group |
X |
X |
X |
AJCC TNM edition number |
X |
- |
X |
CS version input original |
X |
- |
X |
Ambiguous terminology diagnosis |
- |
- |
X |
Date of conclusive diagnosis |
X |
- |
X |
Type of multiple tumours reported as one primary |
X |
- |
X |
Date of multiple tumours |
X |
- |
X |
Multiplicity counter |
X |
- |
X |
Date of diagnosis flag |
X |
- |
X |
Date of conclusive diagnosis flag |
X |
- |
X |
Date of multiple tumours flag |
X |
- |
X |
Grade path Value |
- |
- |
X |
Grade path System |
- |
- |
X |
Lymph-vascular invasion |
- |
- |
X |
CS version input current |
X |
- |
X |
CS site-specific factor 7 |
X |
- |
X |
CS site-specific factor 8 |
X |
- |
X |
CS site-specific factor 9 |
X |
- |
X |
CS site-specific factor 10 |
X |
- |
X |
CS site-specific factor 11 |
X |
- |
X |
CS site-specific factor 12 |
X |
- |
X |
CS site-specific factor 13 |
X |
- |
X |
CS site-specific factor 14 |
X |
- |
X |
CS site-specific factor 15 |
X |
- |
X |
CS site-specific factor 16 |
X |
- |
X |
CS site-specific factor 17 |
X |
- |
X |
CS site-specific factor 18 |
X |
- |
X |
CS site-specific factor 19 |
X |
- |
X |
CS site-specific factor 20 |
X |
- |
X |
CS site-specific factor 21 |
X |
- |
X |
CS site-specific factor 22 |
X |
- |
X |
CS site-specific factor 23 |
X |
- |
X |
CS site-specific factor 24 |
X |
- |
X |
CS site-specific factor 25 |
X |
- |
X |
CS Mets at Dx - Bone |
- |
- |
X |
CS Mets at Dx - Brain |
- |
- |
X |
CS Mets at Dx - Liver |
- |
- |
X |
CS Mets at Dx - Lung |
- |
- |
X |
Revision
Tumour variables T58 – T87 have been added to the record layout. There have been name changes to T31 and T52, and the length of T24 and T25 have been modified so they must now be left justified. |
Tumour input variables T53 to T57 have been added to the record layout. Different formatting processes are done to each new variable. |
T52 – CS version input original (formerly CS Version 1st) – tumour input variable added to record layout. It is left justified and trailing blanks are removed. |
In order to reduce response burden, some data items will automatically be uppercased, left justified and right truncated (removal of trailing blanks) by the CCR system.
T3 – Tumour reference number: Values will not be zero left filled anymore. |
3.3.2 Old classification filtering
Description
This step deletes disease classification information reported by PTCRs older than that indicated by the source classification flag.
Purpose
This step eliminates the possibility of incoherence between source classification data (as identified by the source classification flag) and any former classification data.
Logic
- If the Source classification flag indicates that ICD-9 is the source classification, then all reported data are kept as is.
- If the Source classification flag indicates that ICD-O-2 is the source classification, then reported ICD-9 Cancer Code is replaced by '0000'.
- If the Source classification flag indicates that ICD-O-3 is the source classification, then reported ICD-9 Cancer Code and ICD-O-2 Histology are replaced by '0000' and reported ICD-O-2 Behaviour is replaced by '0'.
- In any other case, all reported data are kept as is.
This step will not create a feedback message. The following examples and table illustrate possible scenarios.
Example 1: If source classification flag indicates ICD-9, then no change.
Example 2: If source classification flag indicates ICD-O-2, then ICD-9 is not loaded.
Example 3: If source classification flag indicates ICD-O-3, then ICD-9 and ICD-O-2H/B are not loaded. ICD-O-2/3T is kept since it also belongs to ICD-O-3.
Table 23
Old classification filtering
Before |
1 |
175 |
C509 |
8521 |
3 |
8521 |
3 |
After |
1 |
175 |
C509 |
8521 |
3 |
8521 |
3 |
Before |
2 |
175 |
C509 |
8521 |
3 |
8521 |
3 |
After |
2 |
0000 |
C509 |
8521 |
3 |
8521 |
3 |
Before |
4 |
175 |
C509 |
8521 |
3 |
8521 |
|
After |
4 |
0000 |
C509 |
0000 |
0 |
8521 |
3 |
3.3.3 ICD-O-2/3 Topography calculation
Background
For cases diagnosed from 1992 to 2000, the Canadian Council of Cancer Registries adopted the International Classification of Diseases for Oncology, Second Edition (ICD-O-2) as the standard for reporting diagnostic information to the Canadian Cancer Registry (CCR). This classification was chosen because it provides detailed information on the site (topography), the histology and the behaviour of the neoplasm. The site codes are based on the malignant neoplasms section (C00-C80) of the International Statistical Classification of Diseases and Related Health Problems, Tenth revision (ICD-10). The morphology codes are revised and expanded from its predecessor, the ICD-O-1. The International Classification of Diseases is a classification system which covers the broad range of diseases and other health problems for which health care services may be rendered. The ICD has been in use in Canada for many decades for morbidity (hospitalization) and mortality (death) reporting. The Ninth revision (ICD-9), in use since 1979, has been replaced by the ICD-10 for morbidity and mortality. Chapter 2 of the ICD-9 (Neoplasms) provides a classification of tumours, primarily by site and includes behaviour. The ICD-O-2 supplements site information with tumour morphology detail. This greater level of specificity makes ICD-O more suitable for cancer registration purposes.
By 1992, the data year for which the CCR became operational, all provincial/territorial cancer registries except Ontario and Québec had implemented the ICD-O-2 for reporting tumour site and morphology. Ontario and Québec had adopted the ICD-O-2 for reporting tumour morphology information, but continued to report the site of tumours using the ICD-9, for administrative reasons. In order to bring all data to a common basis, the ICD-9 to ICD-O-2 conversion was created, cooperatively by Statistics Canada, the Ontario Cancer Treatment and Research Foundation and the Fichier des tumeurs du Québec.
Description
This step computes ICD-O-2/3 Topography code from the reported ICD-9 Cancer code when needed.
Purpose
This step ensures that, for each reported tumour, the site is described using the ICD-O-3 classification. This facilitates the comparison between all tumours reported to the CCR.
Logic
If
ICD-O-2/3 Topography = '0000' and
Source classification flag = '1' then
If ICD-9 Cancer code is found in ICD-9 to ICD-O-2 conversion table
6 then
ICD-O-2/3 Topography = ICD-O-2/3 Topography code associated to ICD-9 Cancer code in ICD-9 to ICD-O-2 conversion table.
Else (ICD-9 Cancer code is NULL or NOT found in ICD-9 to ICD-O-2 conversion table)
Warning saying "ICD-O-2/3 Topography calculation: Conversion failed." is sent to the reporting
PTCR.
End If
End If
Directions
The process of converting coded information from one disease classification system to another can result in a distortion or loss of original diagnostic detail. Whenever possible, it is recommended that the original descriptive diagnosis be coded directly, using the preferred, most recent classification system.
Registries using both the ICD-O-2/3 topography and the ICD-9 to code tumour sites are requested to report only ICD-O-2/3 topography codes to the CCR. ICD-9 codes should only be reported to the CCR if ICD-O-2/3 topography codes are not available.
3.3.4 ICD-O-3 Histology and behaviour calculation
Background
For cases diagnosed from 2001 onwards, the Canadian Council of Cancer Registries adopted the International Classification of Diseases for Oncology, Third edition (ICD-O-3) as the standard for reporting diagnostic information to the Canadian Cancer Registry (CCR). The topography section of the Third edition remains the same as the Second edition; however it includes revised morphologies and new classifications especially for lymphomas and leukemias. This classification was adopted because it represents the most current classification of diseases for oncology.
Description
This step computes the ICD-O-3 Histology and the ICD-O-3 behaviour from reported ICD-O-2 histology and ICD-O-2 behaviour when needed.
Purpose
This step ensures that, for each reported tumour, the histology and behaviour are described using the ICD-O-3 classification. This facilitates the comparison between all tumours reported to the CCR.
If
ICD-O-3 Histology = '0000' and
ICD-O-3 Behaviour = '0' and
Source Classification Flag = '1' or '2' 'then
If
ICD-O-2/3 Topography, ICD-O-2 Histology and
ICD-O-2 Behaviour combination is found in ICD-O-2 to ICD-O-3 conversion table
6 then
ICD-O-3 Histology = ICD-O-3 Histology code associated to ICD-O-2/3 Topography, ICD-O-2 Histology and ICD-O-2 Behaviour combination in ICD-O-2 to ICD-O-3 conversion table
ICD-O-3 Behaviour = ICD-O-3 Behaviour code associated to ICD-O-2/3 Topography, ICD-O-2 Histology and ICD-O-2 Behaviour combination in ICD-O-2 to ICD-O-3 conversion table
If the Review Flag associated to ICD-O-2/3 Topography, ICD-O-2 Histology and ICD-O-2 Behaviour combination in ICD-O-2 to ICD-O-3 conversion table = '1' then
Warning saying "ICD-O-3 Histology and Behaviour calculation: Values must be manually reviewed." is sent to the reporting
PTCR.
Else (ICD-O-2/3 Topography is NULL or ICD-O-2 Histology is NULL or ICD-O-2 Behaviour is NULLor the combination is NOT found in ICD-O-2 to ICD-O-3 conversion table)
Warning saying "ICD-O-3 Histology and Behaviour calculation: Conversion failed." is sent to the reporting
PTCR.
End If
End If
This step ensures that, for each reported tumour, the histology and behaviour are described using the ICD-O-3 classification. This facilitates the comparison between all tumours reported to the CCR
3.3.5 Laterality adjustment
Background
Although the ICD-9 and the ICD-O-3 may be used for similar purposes, they are not totally compatible. Since the ICD-9 and the ICD-O-3 use different topographic groupings, there are cases where the laterality code may be coherent with a given ICD-9 Cancer code but may be incoherent with the closest corresponding ICD-O-2/3 topography code. Thus, for these exceptional cases, the laterality code must be altered to be compliant with the ICD-O-3 classification.
Description
This step alters the laterality code when specific ICD-9 Cancer codes are reported as source classification data and corresponding ICD-O-2/3 topography codes conflict with the reported laterality code due to classification incompatibility.
Purpose
This step reduces PTCR response burden by fixing classification incompatibility issues that would otherwise cause an input record to be rejected.
Logic
If
Source Classification Flag = '1' and
ICD-9 Cancer Code in ['1460','2021','2022','2382'] and
Laterality = '0' then
Laterality = '9'
Warning saying "Laterality Adjustment: Laterality code has been changed from '0' to '9' in order to be compliant with ICD-O-3 classification." is sent to the reporting
PTCR.
End if
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
Validates the Patient reporting province/territory code. |
Validates the Patient identification number. |
Validates the CCR identification number. |
Validates the Patient record type code. |
Validates the Type of current surname code. |
Validates the Current surname. |
Validates the First given name. |
Validates the Second given name. |
Validates the Third given name. |
Validates the Sex code. |
Validates the Date of birth. |
Validates the Province/territory or country of birth code. |
Validates Birth surname. |
Validates Date of death. |
Validates the Province/territory or country of death code. |
Validates Death registration number. |
Validates the Underlying cause of death code. |
Validates Autopsy confirming cause of death code. |
Validates Patient record date of transmission. |
Validates Date of birth flag. |
Validates Date of death flag. |
PVAL1
This edit validates the patient reporting province/territory code.
Table
Referenced fields (PVAL1)
2 |
Patient reporting province/territory |
PREPPROV |
Table
Other parameters (PVAL1)
2 |
Province/territory code of the PTCR that is submitting the data. |
Business rules
For Input patient records
- Patient reporting province/territory must be equal to province/territory code of the PTCR submitting the data7.
Table
Edit logic (PVAL1)
P1 <> PTCR_CODE |
Record rejected |
Table
Feedback report messages (PVAL1)
Patient reporting province/territory code does not match PTCR province/territory code. |
Core error |
Table
Revision (PVAL1)
Not applicable |
PVAL2
Purpose
This edit validates the patient identification number.
Table
Referenced fields (PVAL2)
12 |
Patient identification number |
PPIN |
Business rules
On any type of Input patient record
, Patient identification number
- Must be exclusively composed of any of the following:
- Uppercase letters: A to Z
- Numbers: 0 to 9
- Cannot be exclusively composed of zeros.
Table
Edit logic (PVAL2)
IS_COMPOSED_OF (P2, '0') |
Record rejected |
NOT IS_COMPOSED_OF (P2, 'ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789') |
Record rejected |
Table
Feedback report messages (PVAL2)
Patient identification number cannot be exclusively composed of zeros. |
Core error |
Patient identification number is not exclusively composed of uppercase letters and/or numbers. |
Core error |
Table
Revision (PVAL2)
Business rule changed: Apostrophes, hyphens, periods and inner spaces are not accepted anymore. |
PVAL3
Purpose
This edit validates the CCR identification number.
Table
Referenced fields (PVAL3)
9 |
CCR identification number |
CCR_ID |
8 |
First 8 digits of P3 (CCR ID sequence number) |
Not applicable |
1 |
9th digit of P3 (CCR ID check digit) |
Not applicable |
1 |
Patient record type |
PRECTYPE |
Business rules
For Update and Delete Patient records,
CCR identification number
- Must be exclusively composed of numbers: 0 to 9
- Must be 9 digits long.
- Cannot be all zeros.
- Must have a valid check digit8.
Table
Edit logic (PVAL3)
P4 IN ['2', '3'] AND (LENGTH (P3) <> 9 OR NOT IS_COMPOSED_OF (P3, '0123456789')) |
Record rejected |
P4 IN ['2', '3'] AND P3 = '000000000' |
Record rejected |
P4 IN ['2', '3'] AND P3 <> '000000000' AND LENGTH (P3) = 9 AND IS_COMPOSED_OF (P3, '0123456789') AND P3.CHECK_DIGIT <> CALCULATE_CCR_CHECK_DIGIT (P3.ID) |
Record rejected |
Table
Feedback report messages (PVAL3)
CCR identification number is not 9 digits long. |
Core error |
CCR identification number cannot be all zeros. |
Core error |
CCR identification number is invalid. |
Core error |
Table
Revision (PVAL3)
Not applicable |
PVAL4
Purpose
This edit validates the patient record type code.
Table
Referenced fields (PVAL4)
1 |
Patient record type |
PRECTYPE |
Business rules
For Input Patient records,
Patient record type
- Cannot be blank.
- Must be one of the Eligible patient record type codes9.
Table
Edit logic (PVAL4)
P4 IS NULL OR P4 NOT IN [Eligible Patient record type codes] |
Record rejected |
Table
Feedback report messages(PVAL4)
Patient record type code is missing or invalid. |
Core fatal error |
Table
Revision (PVAL4)
Not applicable |
PVAL5
Purpose
This edit validates the type of current surname code.
Table
Referenced fieldds (PVAL5)
1 |
Patient record type |
PRECTYPE |
1 |
Type of current surname |
PTYP_CUR |
Business rules
For Add and Update Patient records
- Type of Current Surname must be one of the Eligible type of current surname codes10.
Table
Edit logic (PVAL5)
P4 IN ['1', '2'] AND P5 NOT IN [Eligible type of current surname codes] |
Record rejected |
Table
Feedback report messages (PVAL5)
Type of current surname code is invalid. |
Core error |
Table
Revision (PVAL5)
Not applicable |
PVAL6
Purpose
This edit validates the current surname.
Table
Referenced fields (PVAL6)
1 |
Patient record type |
PRECTYPE |
25 |
Current surname |
PCURSNAM |
Business rules
For Add and Update Patient records
- Current surname can be blank.
- If Current surname is not blank then
- It must be exclusively composed of any of the following:
- Letters: A to Z (upper or lowercase)
- Accented characters: Â À Ç É Ê Ë È Î Ï Ô Û Ü (upper or lowercase)
- Special characters: space ( ), period (.), apostrophe ('), hyphen (-)
- It must contain at least one letter.
Table
Edit logic (PVAL6)
P4 IN ['1', '2'] AND P6 IS NOT NULL AND NOT IS_COMPOSED_OF (UPPER (P6), 'ABCDEFGHIJKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ .'-') |
Record rejected |
P4 IN ['1', '2'] AND P6 IS NOT NULL AND IS_COMPOSED_OF (UPPER (P6), 'ABCDEFGHIJKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ .'-') AND NOT CONTAINS_WORD (UPPER (P6), 'ABCDEFGHIJKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ', 1) |
Record rejected |
Table
Feedback report messages (PVAL6)
Current surname is not exclusively composed of acceptable letters, accented characters or special characters. |
Core error |
Current surname does not contain at least one letter. |
Core error |
Table
Revision (PVAL6)
Business rules changed: Acceptable accented characters are specified. |
Business rules changed: Titles are now allowed in current surname. |
PVAL7
Purpose
This edit validates the first given name.
Table
Referenced fields (PVAL7)
1 |
Patient record type |
PRECTYPE |
15 |
First given name |
PGNAME_1 |
Business rules
For Add and Update Patient records
- First given name can be blank.
- If First given name is not blank then
- It must be exclusively composed of any of the following:
- Letters: A to Z (upper or lowercase)
- Accented characters: Â À Ç É Ê Ë È Î Ï Ô Û Ü (upper or lowercase)
- Special characters: space ( ), period (.), apostrophe ('), hyphen (-)
- It must contain at least one letter.
Table
Edit logic (PVAL7)
P4 IN ['1', '2'] AND P7 IS NOT NULL AND NOT IS_COMPOSED_OF (UPPER (P7), 'ABCDEFGHIJKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ .'-') |
Record rejected |
P4 IN ['1', '2'] AND P7 IS NOT NULL AND IS_COMPOSED_OF (UPPER (P7),'ABCDEFGHIJKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ .'-') AND NOT CONTAINS_WORD (UPPER (P7), 'ABCDEFGHIJKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ', 1) |
Record rejected |
Table
Feedback report messages (PVAL7)
First given name is not exclusively composed of acceptable letters, accented characters or special characters. |
Core error |
First given name does not contain at least one letter. |
Core error |
Table
Revision (PVAL7)
Business rules changed: Acceptable accented characters are specified. |
PVAL8
Purpose
This edit validates the second given name.
Table
Referenced fields (PVAL8)
1 |
Patient record type |
PRECTYPE |
15 |
Second given name |
PGNAME_2 |
Business rules
For Add and Update Patient records
- Second given name can be blank.
- If Second given name is not blank then
- It must be exclusively composed of any of the following:
- Letters: A to Z (upper or lowercase)
- Accented characters: Â À Ç É Ê Ë È Î Ï Ô Û Ü (upper or lowercase)
- Special characters: space ( ), period (.), apostrophe ('), hyphen (-)
- It must contain at least one letter
Table
Edit logic(PVAL8)
P4 IN ['1', '2'] AND P8 IS NOT NULL AND NOT IS_COMPOSED_OF (UPPER (P8), 'ABCDEFGHIJKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ .'-') |
Record rejected |
P4 IN ['1', '2'] AND P8 IS NOT NULL AND IS_COMPOSED_OF (UPPER (P8), 'ABCDEFGHIJKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ .'-') AND NOT CONTAINS_WORD (UPPER (P8), 'ABCDEFGHIJKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ', 1) |
Record rejected |
Table
Feedback report messages (PVAL8)
Second given name is not exclusively composed of acceptable letters, accented characters or special characters. |
Core error |
Second given name does not contain at least one letter. |
Core error |
Table
Revision (PVAL8)
Business rules changed: Acceptable accented characters are specified. |
PVAL9
Purpose
This edit validates the third given name.
Table
Referenced fields (PVAL9)
1 |
Patient record type |
PRECTYPE |
7 |
Third given name |
PGNAME_3 |
Business rules
For Add and Update Patient records
- Third given name can be blank.
- If Third given name is not blank then
- It must be exclusively composed of any of the following:
- Letters: A to Z (upper or lowercase)
- Accented characters: Â À Ç É Ê Ë È Î Ï Ô Û Ü (upper or lowercase)
- Special characters: space ( ), period (.), apostrophe ('), hyphen (-)
- It must contain at least one letter.
Table
Edit logic (PVAL9)
P4 IN ['1', '2'] AND P9 IS NOT NULL AND NOT IS_COMPOSED_OF (UPPER (P9), 'ABCDEFGHIJKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ .'-') |
Record rejected |
P4 IN ['1', '2'] AND P9 IS NOT NULL AND IS_COMPOSED_OF (UPPER (P9), 'ABCDEFGHIJKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ .'-') AND NOT CONTAINS_WORD (UPPER (P9), 'ABCDEFGHIJKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ', 1) |
Record rejected |
Table
Feedback report messages (PVAL9)
Third given name is not exclusively composed of acceptable letters, accented characters or special characters. |
Core error |
Third given name does not contain at least one letter. |
Core error |
Table
Revision (PVAL9)
Business rules changed: Acceptable accented characters are specified. |
PVAL10
Purpose
This edit validates the sex code.
Table
Referenced fields (PVAL10)
1 |
Patient record type |
PRECTYPE |
1 |
Sex |
PSEX |
Business rules
For Add and Update Patient records
- Sex must be one of the Eligible sex codes11.
Table
Edit logic (PVAL10)
P4 IN ['1', '2'] AND P10 NOT IN [Eligible sex codes] |
Record rejected |
Table
Feedback report messages (PVAL10)
Sex code is invalid. |
Core error |
Table
Revision (PVAL10)
Not applicable |
PVAL11
Purpose
This edit validates the date of birth.
Table
Referenced fields (PVAL11)
1 |
Patient record type |
PRECTYPE |
8 |
Date of birth |
PDATBIR |
4 |
First 4 digits of P11 (year of date of birth) |
Not applicable |
2 |
5th and 6th digits of P11 (month of date of birth) |
Not applicable |
2 |
7th and 8th digits of P11 (day of date of birth) |
Not applicable |
Table
Other parameters (PVAL11)
2 |
Reference year |
Business rules
For Add and Update Patient records,
Date of birth
- Must be 8 digits long.
- Must be between January 1st, 1875 and December 31st of Reference year inclusively.
- If Year is unknown then Month must be unknown.
- If Month is unknown then Day must be unknown.
- If Year, Month and Day are known then it must be a valid calendar date.
- If Year and Month are known and Day is unknown then month must be a valid month.
Table
Edit logic (PVAL11)
P4 IN ['1', '2'] AND (LENGTH (P11) <> 8 OR NOT IS_COMPOSED_OF (P11, '0123456789')) |
Record rejected |
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 |
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 |
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 |
P4 IN ['1', '2'] AND LENGTH (P11) = 8 AND IS_COMPOSED_OF (P11, '0123456789') AND P11.YEAR <> '9999' AND P11.MONTH NOT IN ['01'-'12', '99'] AND P11.DAY = '99' |
Record rejected |
Table
Feedback report messages (PVAL11)
Date of birth is not 8 digits long. |
Core error |
Date of birth: Improper use of the 'Unknown' code. |
Core error |
Date of birth must be between the year 1875 and the current reference year inclusively. |
Core error |
Date of birth is not a valid calendar date. |
Core error |
Date of birth is not a valid partial date: month is invalid. |
Core error |
Table
Revision (PVAL11)
Not applicable |
PVAL12
Purpose
This edit validates the province/territory or country of birth code.
Table
Referenced fields (PVAL12)
1 |
Patient record type |
PRECTYPE |
4 |
First 4 characters of P11 (year of date of birth) |
Not applicable |
3 |
Province/territory or country of birth |
PPROVBIR |
Business rules
For Add and Update Patient records
- If Date of birth is before 1996 then Province/territory or country of birth must be one of the Eligible Province/territory and country codes prior to 199612.
- If Date of birth is on or after 1996 then Province/territory or country of birth must be one of the Eligible Province/territory and country codes in and after 199612
- If Date of birth is unknown then Province/territory or country of birth must be either one of the Eligible Province/territory and country codes prior to 199612 or Eligible Province/territory and country codes in and after 199612.
Table
Edit logic (PVAL12)
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 |
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 |
P4 IN ['1', '2'] AND P11.YEAR = '9999' AND P12 NOT IN [Eligible Province/territory and country code prior to 1996] AND P12 NOT IN [Eligible Province/territory and country code in and after 1996] |
Record rejected |
Table
Feedback report messages (PVAL12)
Province/territory or country of birth code is invalid for Date of birth prior to 1996. |
Core error |
Province/territory or country of birth code is invalid for Date of birth in and after 1996. |
Core error |
Province/territory or country of birth code is invalid. |
Core error |
Table
Revision PVAL12)
Business rules changed: Province/territory or country of birth code is now validated against Province/territory or country codes valid at time of birth. |
PVAL13
Purpose
This edit validates birth surname.
Table
Referenced fields (PVAL13)
1 |
Patient record type |
PRECTYPE |
25 |
Birth surname |
PBIRNAM |
Business rules
For Add and Update Patient records
- Birth surname can be blank.
- If Birth surname is not blank then
- It must be exclusively composed of any of the following:
- Letters: A to Z (upper or lowercase)
- Accented characters: Â À Ç É Ê Ë È Î Ï Ô Û Ü (upper or lowercase)
- Special characters: space ( ), period (.), apostrophe ('), hyphen (-)
- It must contain at least one letter.
Table
Edit logic (PVAL13)
P4 IN ['1', '2'] AND P13 IS NOT NULL AND NOT IS_COMPOSED_OF (UPPER (P13), 'ABCDEFGHIJKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ .'-') |
Record rejected |
P4 IN ['1', '2'] AND P13 IS NOT NULL AND IS_COMPOSED_OF (UPPER (P13), 'ABCDEFGHIJKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ .'-') AND NOT CONTAINS_WORD (UPPER (P13), 'ABCDEFGHIJKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ', 1) |
Record rejected |
Table
Feedback report messages (PVAL13)
Birth surname is not exclusively composed of acceptable letters, accented characters or special characters. |
Core error |
Birth surname does not contain at least one letter. |
Core error |
Table
Revision Feedback report messages (PVAL13)
Business rules changed: Acceptable accented characters are specified. |
PVAL14
Purpose
This edit validates date of death.
Table
Referenced fields (PVAL14)
1 |
Patient record type |
PRECTYPE |
8 |
Date of death |
PDATDEA |
4 |
First 4 digits of P14 (year of date of death) |
Not applicable |
2 |
5th and 6th digits of P14 (month of date of death) |
Not applicable |
2 |
7th and 8th digits of P14 (day of date of death) |
Not applicable |
4 |
First 4 digits of P19 (year of date of transmission) |
Not applicable |
2 |
5th and 6th digits of P19 (Month of date of transmission) |
Not applicable |
2 |
7th and 8th digits of P19 (Day of date of transmission) |
Not applicable |
Business rules
For Add and Update Patient records,
Date of death
- Must be 8 digits long.
- Can be all zeros (when patient is not known to have died).
- Must be between January 1st, 1992 and Date of transmission inclusively.
- If Year is unknown then Month must be unknown.
- If Month is unknown then Day must be unknown.
- If Year, Month and Day are known then it must be a valid calendar date.
- If Year and Month are known and Day is unknown then Month must be a valid month.
Table
Edit logic (PVAL14)
P4 IN ['1', '2'] AND (LENGTH (P14) <> 8 OR NOT IS_COMPOSED_OF (P14, '0123456789')) |
Record rejected |
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 |
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 |
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 |
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 |
P4 IN ['1', '2'] AND LENGTH (P14) = 8 AND IS_COMPOSED_OF (P14, '0123456789') AND P14.YEAR NOT IN ['0000', '9999'] AND P14.MONTH NOT IN ['00', '01'-'12', '99'] AND P14.DAY = '99' |
Record rejected |
Table
Feedback report messages (PVAL14)
Date of death is not 8 digits long. |
Core error |
Date of death: Improper use of 'Patient is not known to have died' code. |
Core error |
Date of death must be between January 1st, 1992 and the Date of Transmission inclusively. |
Core error |
Date of death: Improper use of 'Unknown' code. |
Core error |
Date of death is not a valid calendar date. |
Core error |
Date of death is not a valid partial date: month is invalid. |
Core error |
Table
Revision (PVAL14)
Business rules changed: Date of death cannot be beyond Date of transmission. |
PVAL15
Purpose
This edit validates the province/territory or country of death code.
Table
Referenced fields (PVAL15)
1 |
Patient record type |
PRECTYPE |
4 |
First 4 characters of P14 (year of date of death) |
Not applicable |
3 |
Province/territory or country of death |
PPROVDEA |
Business rules
For Add and Update Patient records
- If Date of death is before 1996 then Province/territory or country of death must be one of the Eligible province/territory and country codes prior to 199612.
- If Date of death is on or after 1996 then Province/territory or country of death must be one of the Eligible province/territory and country codes in and after 199612.
- If Date of death is unknown then Province/territory or country of death must be either one of the Eligible province/territory and country codes prior to 199612 or Eligible province/territory and country codes in and after 199612.
Table
Edit Logic (PVAL15)
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 |
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 |
P4 IN ['1', '2'] AND P14.YEAR = '9999' AND P15 NOT IN [Eligible Province/Territory or Country of Death codes in and after 1996] AND P15 NOT IN [Eligible province/territory or country codes prior to 1996] |
Record rejected |
Table
Feedback report messages (PVAL15)
Province/territory or country of death code is invalid for Date of death prior to 1996. |
Core error |
Province/territory or country of death code is invalid for Date of death in and after 1996. |
Core error |
Province/territory or country of death code is invalid. |
Core error |
Table
Revision (PVAL15)
Business rules changed: Province/territory or country of death code is now validated against Province/territory or country codes valid at time of death. |
PVAL16
Purpose
This edit validates the death registration number.
Table
Referenced fields (PVAL16)
1 |
Patient record type |
PRECTYPE |
6 |
Death registration number |
PDEAREG |
Business rules
For Add and Update Patient records,
Death registration number
- Must be exclusively composed of numbers: 0 to 9
- Must be 6 digits long
Table
Edit logic (PVAL16)
P4 IN ['1', '2'] AND (LENGTH (P16) <> 6 OR NOT IS_COMPOSED_OF (P16, '0123456789')) |
Record rejected |
Table
Feedback report messages (PVAL16
Death registration number is not 6 digits long. |
Core error |
Table
Revision (PVAL16)
Not applicable |
PVAL17
Purpose
This edit validates the underlying cause of death code.
Table
Referenced fields (PVAL17)
1 |
Patient record type |
PRECTYPE |
4 |
First 4 characters of P14 (year of date of death) |
Not applicable |
P17 |
3 |
Underlying cause of death |
PCAUSDEA |
Business rules
For Add and Update Patient records
- IF Date of death is unknown then Underlying cause of death must be coded as 'Unknown/unavailable Underlying cause of death'.
- IF Date of death is before 2000 then Underlying cause of death must be one of the Eligible ICD-9 underlying cause of death codes12.
- IF Date of death is between 2000 and 2002 inclusively then Underlying cause of death must be one of the Eligible ICD-10 underlying cause of death codes in 2000-200212
- IF Date of death is in or after 2003 then Underlying cause of death must be one of the Eligible ICD-10 underlying cause of death codes in 2003 and after13.
Table
Edit logic (PVAL17)
P4 IN ['1', '2'] AND P14.YEAR = '9999' AND P17 <> '0009' |
Record rejected |
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 |
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 |
P4 IN ['1', '2'] AND P14.YEAR NOT IN ['0000', '9999'] AND P14.YEAR >= 2003 AND P17 NOT IN [ICD-10 – Cause of death in 2003 and after] |
Record rejected |
Table
Feedback report messages (PVAL17)
Underlying cause of death must be set to unknown when the Date of death is unknown. |
Core error |
Underlying cause of death code is either invalid or not eligible for Date of death prior to 2000. |
Core error |
Underlying cause of death code is either invalid or not eligible for Date of death between 2000 and 2002 inclusively. |
Core error |
Underlying cause of death code is either invalid or not eligible for Date of death in or after 2003. |
Core error |
Table
Revision (PVAL17)
Business rules added:
If Date of death is unknown then Underlying cause of death must be coded as 'Unknown/unavailable Underlying cause of death'.
If Date of death is in 2003 or after then Underlying cause of death must be coded using the latest revision of ICD-10 Underlying cause of death (2003 and after). |
PVAL18
Purpose
This edit validates autopsy confirming cause of death code.
Table
Referenced fields (PVAL18)
1 |
Patient record type |
PRECTYPE |
1 |
Autopsy confirming cause of death |
PAUTOPSY |
Business rules
For Add and Update Patient records
- Autopsy confirming cause of death must be one of the eligible autopsy confirming cause of death codes14.
Table
Edit logic (PVAL18)
P4 IN ['1', '2'] AND P18 NOT IN [Eligible Autopsy confirming cause of death codes] |
Record rejected |
Table
Feedback report messages (PVAL18)
Autopsy confirming cause of death code is invalid. |
Core error |
Table
Revision (PVAL18)
Not applicable |
PVAL19
Purpose
This edit validates the patient record date of transmission.
Table
Referenced fields (PVAL19)
8 |
Patient Date of transmission |
PDATTRAN |
4 |
First 4 digits of P19 (year of date of transmission) |
Not applicable |
2 |
5th and 6th digits of P19 (month of date of transmission) |
Not applicable |
2 |
7th and 8th digits of P19 (day of date of transmission) |
Not applicable |
Table
Other parameters (PVAL19)
8 |
Statistics Canada loading date: date on the Statistics Canada computer clock when the data are loaded on the CCR database. |
Business rules
For Input Patient records
, Patient Date of transmission
- Cannot be blank
- Must be exclusively composed of numbers: 0 to 9
- Must be 8 digits long
- Must be a valid calendar date
- Must be within the previous 10 months from Statistics Canada loading date
Table
Edit logic (PVAL19)
P19 IS NULL |
Record rejected |
P19 IS NOT NULL AND (LENGTH (P19) <> 8 OR NOT IS_COMPOSED_OF (P19, '0123456789')) |
Record rejected |
P19 IS NOT NULL AND LENGTH (P19) = 8 AND IS_COMPOSED_OF (P19, '0123456789') AND NOT IS_VALID_DATE (P19) |
Record rejected |
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 |
P19 IS NOT NULL AND LENGTH (P19) = 8 AND IS_COMPOSED_OF (P19, '0123456789') AND IS_VALID_DATE (P19) AND P19 < (LOAD_DATE – 10 months) |
Record rejected |
Table
Feedback report messages (PVAL19)
Patient Date of transmission is missing. |
Core fatal error |
Patient Date of transmission is not 8 digits long. |
Core fatal error |
Patient Date of transmission is not a valid calendar date. |
Core fatal error |
Patient Date of transmission is after Statistics Canada loading date. |
Core fatal error |
Patient Date of transmission is more than 10 months before Statistics Canada loading date. |
Core fatal error |
Table
Revision (PVAL19)
Not applicable |
PVAL20
Purpose
This edit validates the date of birth flag.
Table
Referenced fields (PVAL20)
1 |
Patient record type |
PRECTYPE |
1 |
Date of birth flag |
PDATBIRFLAG |
Business rules
For Add and Update Patient records
- Date of death flag must be one of the Eligible date of death flag codes.
Table
Edit logic (PVAL20)
P4 IN ['1', '2'] AND P12 NOT IN [Eligible date of death flag codes] |
Record rejected |
Table
Feedback report messages (PVAL20)
Date of death flag code is invalid. |
Core fatal error |
Table
Revision (PVAL20)
New edit added. |
PVAL21
Purpose
This edit validates the date of death flag.
Table
Referenced fields (PVAL21)
1 |
Patient record type |
PRECTYPE |
1 |
Date of death flag |
PDATDEAFLAG |
Business rules
For Add and Update Patient records
- Date of death flag must be one of the Eligible date of death flag codes.
Table
Edit logic (PVAL21)
P4 IN ['1', '2'] AND P12 NOT IN [Eligible date of death flag codes] |
Record rejected |
Table
Feedback report messages (PVAL21)
Date of death flag code is invalid. |
Core fatal error |
Table
Table
Revision (PVAL21)
New edit added |
3.4.2 Tumour validation edits
The following table summarizes the purpose of each individual edit of this category.
Table 25 Tumour validation edits summary
Table
Table 25 Tumour validation edits summary
Validates the Tumour reporting province/territory code. |
Validates the Tumour patient identification number. |
Validates the Tumour reference number. |
Validates the CCR identification number. |
Validates the Tumour record type code. |
Validates the Name of place of residence. |
Validates the Postal code. |
Validates the Standard geographic code. |
Validates the Census tract. |
Validates the Health insurance number (HIN). |
Validates the Method of diagnosis code. |
Validates the Date of diagnosis. |
Validates the ICD-9 cancer code. |
Validates the Source classification flag. |
Validates the ICD-O-2/3 Topography code. |
Validates the ICD-O-2 Histology code. |
Validates the ICD-O-2 Behaviour code. |
Not applicable |
Validates the Laterality code. |
Not applicable |
Validates the ICD-O-3 Histology code. |
Validates the ICD-O-3 Behaviour code. |
Validates the grade, differentiation or cell indicator code. |
Validates the Method used to establish the date of diagnosis code. |
Validates the Diagnostic confirmation code. |
Validates the Date of transmission. |
Validates CS tumour size. |
Validates CS extension. |
Validates CS tumour size/ext eval. |
Validates CS lymph nodes. |
Validates CS lymph nodes eval. |
Validates Regional nodes examined. |
Validates Regional nodes positive. |
Validates CS mets at dx. |
Validates CS mets eval. |
Validates CS site-specific factor 1. |
Validates CS site-specific factor 2. |
Validates CS site-specific factor 3. |
Validates CS site-specific factor 4. |
Validates CS site-specific factor 5. |
Validates CS site-specific factor 6. |
Validates AJCC clinical T. |
Validates AJCC clinical N. |
Validates AJCC clinical M. |
Validates AJCC pathologic T. |
Validates AJCC pathologic N. |
Validates AJCC pathologic M. |
Validates AJCC clinical TNM stage group. |
Validates AJCC pathologic TNM stage group. |
Validates AJCC TNM stage group. |
Validates AJCC edition number code. |
Validates CS version input original. |
Validates Ambiguous terminology diagnosis. |
Validates Date of conclusive diagnosis. |
Validates Type of multiple tumours reported as one primary. |
Validates Date of multiple tumours. |
Validates multiplicity counter. |
Validates Date of diagnosis flag. |
Validates Date of conclusive diagnosis flag. |
Validates Date of multiple tumours flag. |
Validates Grade path value. |
Validates Grade path system. |
Validates Lymph-vascular invasion. |
Validates CS Version input current. |
Validates site-specific factors 7 - 25 |
Validates CS Mets at Dx - Bone |
Validates CS Mets at Dx - Brain |
Validates CS Mets at Dx - Liver |
Validates CS Mets at Dx - Lung |
TVAL1
Purpose
This edit validates the Tumour reporting province/territory code.
Table
Referenced Fields (TVAL1)
2 |
Tumour reporting province/territory |
TREPPROV |
Table
Other parameters (TVAL1)
2 |
Province/territory code of the PTCR that is submitting the data. |
Business rules
For Input Tumour records
- Tumour reporting province/territory must be equal to province/territory code of the PTCR that is submitting the data15.
Table
Edit logic (TVAL1)
T1 <> PTCR_CODE |
Record rejected |
Table
Feedback report messages (TVAL1)
Tumour reporting province/territory code does not match PTCR province/territory code. |
Core error |
Table
Revision (TVAL1)
Not applicable |
TVAL2
Purpose
This edit validates the tumour patient identification number.
Table
Referenced fields (TVAL2)
12 |
Tumour patient identification number |
TPIN |
Business rules
For Input Tumour records
, Patient identification number
- Must be exclusively composed of any of the following:
- Uppercase letters: A to Z
- Numbers: 0 to 9
- Cannot be exclusively composed of zeros.
Table
Edit logic (TVAL2)
IS_COMPOSED_OF (T2, '0') |
Record rejected |
NOT IS_COMPOSED_OF (T2, 'ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789') |
Record rejected |
Table
Feedback report messages (TVAL2)
Patient identification number cannot be exclusively composed of zeros. |
Core error |
Patient identification number is not exclusively composed of uppercase letters and/or numbers. |
Core error |
Table
Revision (TVAL2)
Business rule changed: Apostrophes, hyphens, periods and inner spaces are not accepted anymore. |
TVAL3
Purpose
This edit validates the tumour reference number.
Table
Referenced fields (TVAL3)
9 |
Tumour reference number |
TTRN |
Business rules
For Input Tumour records
, Tumour reference number
- Must be exclusively composed of any of the following:
- Numbers: 0 to 9
- Uppercase letters: A to Z
- Special characters: space ( ), period (.), apostrophe ('), hyphens (-)
- Cannot be exclusively composed of zeros.
Table
Edit logic (TVAL3)
IS_COMPOSED_OF (T3, '0') |
Record rejected |
NOT IS_COMPOSED_OF (T3, 'ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789 -'.') |
Record rejected |
Table
Feedback report messages (TVAL3)
Tumour reference number cannot be exclusively composed of zeros. |
Core error |
Tumour reference number is not exclusively composed of acceptable letters, numbers or special characters. |
Core error |
Table
Revision (TVAL3)
Business rule added: Tumour reference number cannot be exclusively composed of zeros. |
TVAL4
Purpose
This edit validates the CCR identification number.
Table
Referenced fields (TVAL4)
9 |
CCR identification number |
CCR_ID |
8 |
First 8 digits of T4 (CCR ID sequence number) |
Not applicable |
1 |
9th digit of T4 (CCR ID check digit) |
Not applicable |
Business rules
For Input Tumour records
- If CCR identification number is reported then
- Must be exclusively composed of numbers: 0 to 9
- Must be 9 digits long;
- Cannot be all zeros;
- Must have a valid check digit16.
Table
Edit logic (TVAL4)
T4 IS NOT NULL AND (LENGTH (T4) <> 9 OR NOT IS_COMPOSED_OF (T4, '0123456789')) |
Record rejected |
T4 = '000000000' |
Record rejected |
T4 IS NOT NULL AND T4 <> '000000000' AND LENGTH (T4) = 9 AND IS_COMPOSED_OF (T4, '0123456789') AND T4.CHECK_DIGIT <> CALCULATE_CCR_CHECK_DIGIT (T4.ID) |
Record rejected |
Table
Feedback report messages (TVAL4)
CCR identification number is not 9 digits long. |
Core error |
CCR identification number cannot be all zeros. |
Core error |
CCR identification number is invalid. |
Core error |
Table
Revision (TVAL4)
Not applicable |
TVAL5
Purpose
This edit validates the tumour record type code.
Table
Referenced fields (TVAL5)
1 |
Tumour record type |
TRECTYPE |
Business rules
For Input Tumour records,
Tumour record type
- Cannot be blank.
- Must be one of the Eligible tumour record type codes17 .
Table
Edit logic (TVAL5)
T5 IS NULL OR T5 NOT IN [Eligible tumour record type codes] |
Record rejected |
Table
Feedback report messages (TVAL5)
Tumour record type code is missing or invalid. |
Core fatal error |
Table
Revision (TVAL5)
Not applicable |
TVAL6
Purpose
This edit validates the name of place of residence.
Table
Referenced fileds (TVAL6)
1 |
Tumour record type |
TRECTYPE |
25 |
Name of place of residence |
TPLACRES |
Business rules
For Add and Update Tumour records
- Name of place of residence can be blank.
- If Name of place of residence is not blank then it can be any combination of the following:
- Letters: A to Z (upper or lowercase)
- Accented characters: Â À Ç É Ê Ë È Î Ï Ô Û Ü (upper or lowercase)
- Special characters: space ( ), period (.), apostrophe ('), hyphen (-), exclamation mark (!), ampersand (&), forward slash (/), parentheses ["("and")"], number sign (#), comma (,)
- It must contain a word of at least 2 letters.
Table
Edit logic TVAL6)
T5 IN ['1', '2'] AND T6 IS NOT NULL AND IS NOT COMPOSED OF (UPPER (T6), 'ABCDEFGHILKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ.'-!&/()#,') |
Record rejected |
T5 IN ['1', '2'] AND T6 IS NOT NULL AND IS_COMPOSED_OF (UPPER (T6), 'ABCDEFGHILKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ .'-!&/()#,') AND NOT CONTAINS_WORD (UPPER (T6), 'ABCDEFGHILKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ', 2) |
Record rejected |
Table
Feedback report messages (TVAL6)
Name of place of residence is not exclusively composed of acceptable letters, accented characters or special characters. |
Core error |
Name of place of residence does not contain a word of at least 2 letters. |
Core error |
Table
Revision (TVAL6)
Business rules changed: Acceptable accented characters and special characters are specified. Edit logic: New edit logic added. Feedback report messages: New message added. |
TVAL7
Purpose
This edit validates the postal code.
Table
Referenced fields (TVAL7)
1 |
Tumour record type |
TRECTYPE |
6 |
Postal code |
TPOSTCOD |
1 |
1st character of T7 |
Not applicable |
1 |
2nd character of T7 |
Not applicable |
1 |
3rd character of T7 |
Not applicable |
1 |
4th character of T7 |
Not applicable |
1 |
5th character of T7 |
Not applicable |
1 |
6th character of T7 |
Not applicable |
Business rules
For Add and Update Tumour records
, Postal code
- Must be 6 characters long.
- Can be unknown.
- If not unknown then
- 1st, 3rd and 5th characters must be uppercase letters: A-Z
- 2nd, 4th and 6th characters must be numbers: 0-9
Table
Edit logic (TVAL7)
T5 IN ['1', '2'] AND (LENGTH(T7) <> 6 OR (T7 <> '999999' AND (T7.FIRST NOT IN [A-Z] OR T7.SECOND NOT IN [0-9] OR T7.THIRD NOT IN [A-Z] OR T7.FOURTH NOT IN [0-9] OR T7.FIFTH NOT IN [A-Z] OR T7.SIXTH NOT IN [0-9]))) |
Record rejected |
Table
Feedback report messages (TVAL7)
Postal code has an invalid format. |
Core error |
Table
Revision (TVAL7)
Not applicable |
TVAL8
Purpose
This edit validates the Standard geographic code.
Table
Referenced fields (TVAL8)
1 |
Tumour record type |
TRECTYPE |
7 |
Standard geographic code |
TCODPLAC |
4 |
First 4 digits of T12 (year of date of diagnosis) |
Not applicable |
Business rules
For Add and Update Tumour records
- If Date of diagnosis is between 1992 and 1995 then Standard geographic code must be one of the Eligible Standard geographic classification codes from 1992 to 199512.
- If Date of diagnosis is between 1996 and 2000 then Standard geographic code must be one of the Eligible Standard geographic classification codes from 1996 to 200012.
- If Date of diagnosis is between 2001 and 2005 then Standard geographic code must be one of the Eligible Standard geographic classification codes from 2001 to 200512.
- If Date of Diagnosis is between 2006 and 2010 then Standard geographic code must be one of the Eligible Standard geographic classification codes from 2006 and 2010.
Table
Edit logic (TVAL8)
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 |
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 |
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 |
T5 IN ['1', '2'] AND T12.YEAR BETWEEN ('2006', '2010') AND T8 NOT IN [Eligible Standard Geographic Classification codes from 2006 to 2010] |
Record rejected |
Table
Feedback report messages (TVAL8)
Standard geographic code is invalid according to the Standard geographic classification – 1991. |
Core error |
Standard geographic code is invalid according to the Standard geographic classification – 1996. |
Core error |
Standard geographic code is invalid according to the Standard geographic classification – 2001. |
Core error |
Standard geographic code is invalid according to the Standard geographic classification – 2006. |
Core error |
Table
Revision (TVAL8)
Business rules, Edit logic and Feedback report messages added: SGC – 2006 added |
Business rules, Edit logic and Feedback report messages added: SGC – 2001 added |
Business rules, Edit logic and Feedback report messages added: SGC – 1996 added |
TVAL9
Purpose
This edit validates the census tract.
Table
Referenced fields (TVAL9)
1 |
Tumour record type |
TRECTYPE |
9 |
Census tract |
TCENTRAC |
4 |
First 4 digits of T12 (year of date of diagnosis) |
Not applicable |
Business rules
For Add and Update Tumour records
- If Date of diagnosis is between 1992 and 1995 then Census tract must be reported and must be one of the Eligible Census tracts from 1992 to 199512.
- If Date of diagnosis is between 1996 and 2000 then Census tract must be reported and must be one of the Eligible Census tracts from 1996 to 200012.
- If Date of diagnosis is between 2001 and 2005 then Census tract must be reported and must be one of the Eligible Census tracts from 2001 to 200512
- If Date of Diagnosis is 2006 and onwards then Census Tract must not be reported (field should be left blank).
Table
Edit logic (TVAL9)
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 |
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 |
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 |
T5 IN ['1', '2'] AND T12.YEAR >= ('2006') AND T9 <> NULL |
Record rejected |
Table
Feedback report messages (TVAL9)
Census tract is invalid according to the Census tract Data Dictionary – 1991. |
Core error |
Census tract is invalid according to the Census tract Data Dictionary – 1996. |
Core error |
Census tract is invalid according to the Census tract Data Dictionary – 2001. |
Core error |
Census tract must not be reported for cases diagnosed in 2006 and onwards. |
Core error |
Table
Revision (TVAL9)
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) |
Business rules, Edit logic and Feedback report messages added: Eligible Census tracts – 2001 added |
Business rules, Edit logic and Feedback report messages added: Eligible Census tracts – 1996 added |
TVAL10
Purpose
This edit validates the health insurance number (HIN).
Table
Referenced fields (TVAL10)
1 |
Tumour record type |
TRECTYPE |
15 |
Health insurance number |
THIN |
Business rules
For Add and Update Tumour records,
- If Health insurance number is reported then
- It must be at least 6 characters long.
- It must be exclusively composed of any of the following:
- Uppercase letters: A to Z
- Numbers: 0 to 9
Table
Edit logic (TVAL10)
T5 IN ['1', '2'] AND T10 IS NOT NULL AND LENGTH (T10) < 6 |
Record rejected |
T5 IN ['1', '2'] AND T10 IS NOT NULL AND NOT IS_COMPOSED_OF (T10, 'ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789') |
Record rejected |
Table
Feddback report messages (TVAL10)
Health insurance number is less than 6 characters long. |
Core error |
Health insurance number is not exclusively composed of uppercase letters and/or numbers. |
Core error |
Table
Revision (TVAL10)
Not applicable |
TVAL11
Purpose
This edit validates the method of diagnosis code.
Table
Referenced fields (TVAL11)
1 |
Tumour record type |
TRECTYPE |
1 |
Method of diagnosis |
TMETHDIAG |
Business rules
For Add and Update Tumour records
- Method of diagnosis must be one of the Eligible method of diagnosis codes18.
Table
Edit logic (TVAL11)
T5 IN ['1', '2'] AND T11 NOT IN [Eligible method of diagnosis codes] |
Record rejected |
Table
Feedback report messages (TVAL11)
Method of diagnosis code is invalid. |
Core error |
Table
Revision (TVAL11)
Not applicable |
TVAL12
Purpose
This edit validates the date of diagnosis.
Table
Referenced fields (TVAL12)
1 |
Tumour record type |
TRECTYPE |
8 |
Date of diagnosis |
TDATDIAG |
4 |
First 4 digits of T12 (year of date of diagnosis) |
Not applicable |
2 |
5th and 6th digits of T12 (month of date of diagnosis) |
Not applicable |
2 |
Last 2 digits of T12 (day of date of diagnosis) |
Not applicable |
Table
Other parameters (TVAL12)
4 |
Reference year |
Business rules
For Add and Update Tumour records
, Date of Diagnosis
- Must be exclusively composed of numbers: 0 to 9.
- Must be 8 digits long.
- Must be between January 1st, 1992 and December 31st of Reference year inclusively.
- Year cannot be unknown.
- If Month is unknown then Day must be unknown.
- If Year, Month and Day are known then it must be a valid calendar date.
- If Year and Month are known and Day is unknown then Month must be a valid month.
Table
Edit logic (TVAL12)
T5 IN ['1', '2'] AND (LENGTH (T12) <> 8 OR NOT IS_COMPOSED_OF (T12, '0123456789')) |
Record rejected |
T5 IN ['1', '2'] AND LENGTH (T12) = 8 AND IS_COMPOSED_OF (T12, '0123456789') AND T12.MONTH = '99' AND T12.DAY <> '99' |
Record rejected |
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 |
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 |
T5 IN ['1', '2'] AND LENGTH (T12) = 8 AND IS_COMPOSED_OF (T12, '0123456789') AND T12.MONTH NOT IN ['01'-'12', '99'] AND T12.DAY = '99' |
Record rejected |
Table
Feedback report messages (TVAL12)
Date of diagnosis is not composed of 8 numbers. |
Core error |
Date of diagnosis: Improper use of 'Unknown' code. |
Core error |
Date of diagnosis must be between January 1st, 1992 and December 31st of Reference year inclusively. |
Core error |
Date of diagnosis is not a valid calendar date. |
Core error |
Date of diagnosis is not a valid partial date: month is invalid. |
Core error |
Table
Revision (TVAL12)
Not applicable |
TVAL13
Purpose
This edit validates the ICD-9 cancer code.
Table
Referenced fields (TVAL13)
1 |
Tumour record type |
TRECTYPE |
4 |
ICD-9 cancer code |
TICD_9 |
Business rules
For Add and Update Tumour records
- If ICD-9 Cancer code is reported then it must be one of the Eligible ICD-9 Cancer codes19.
Table
Edit logic (TVAL13)
T5 IN ['1', '2'] AND T13 <> '0000' AND T13 NOT IN [Eligible ICD-9 Cancer codes] |
Record rejected |
Table
Feedback report messages (TVAL13)
ICD-9 Cancer code is either invalid or not eligible for the CCR system. |
Core error |
Table
Revision (TVAL13)
Not applicable |
TVAL14
Purpose
This edit validates the source classification flag.
Table
Referenced fields (TVAL14)
1 |
Tumour record type |
TRECTYPE |
1 |
Source classification flag |
TSCF |
Business rules
For Add and Update Tumour records
- Source classification flag must be one of the Eligible source classification flags20.
Table
Edit logic (TVAL14)
T5 IN ['1', '2'] AND T14 NOT IN [Eligible source classification flags] |
Record rejected |
Table
Feedback report messages (TVAL14)
Source classification flag is invalid. |
Core error |
Table
Revision (TVAL14)
Not applicable |
TVAL15
Purpose
This edit validates the ICD-O-2/3 topography code.
Table
Referenced fields (TVAL15)
1 |
Tumour record type |
TRECTYPE |
4 |
ICD-O-2/3 Topography |
TICD_O2T |
Business rules
For Add and Update Tumour records
- ICD-O-2/3 Topography must be one of the Eligible ICD-O-2/3 Topography codes12.
Table
Edit logic (TVAL15)
T5 IN ['1', '2'] AND T15 NOT IN [Eligible ICD-O-2/3 Topography codes] |
Record rejected |
Table
Feedback report messages (TVAL15)
ICD-O-2/3 Topography code is either invalid or not eligible for the CCR System. |
Core error |
Table
Revision (TVAL15)
Not applicable |
TVAL16
Purpose
This edit validates the ICD-O-2 histology code.
Table
Referenced fields (TVAL16)
1 |
Tumour record type |
TRECTYPE |
4 |
ICD-O-2/3 Topography |
TICD_O2T |
4 |
ICD-O-2 Histology |
TICD_O2H |
Business rules
For Add and Update Tumour records
- If ICD-O-2 Histology is reported then it must be one of the Eligible ICD–O–2 Histology codes12.
Table
Edit logic (TVAL16)
T5 IN ['1', '2'] AND T15 <> '0000' AND T16 NOT IN [Eligible ICD-O-2 Histology codes] |
Record rejected |
Table
Feedback report messages (TVAL16)
ICD-O-2 Histology code is either invalid or not eligible for the CCR System. |
Core error |
Table
Revision (TVAL16)
Not applicable |
TVAL17
Purpose
This edit validates the ICD-O-2 Behaviour code.
Table
Referenced fields (TVAL17)
1 |
Tumour record type |
TRECTYPE |
1 |
ICD-O-2 Behaviour |
TICD_O2B |
Business rules
For Add and Update Tumour records
- If ICD-O-2 Behaviour is reported then it must be one of the Eligible ICD–O–2 Behaviour codes21.
Table
Edit logic (TVAL17)
T5 IN ['1', '2'] AND T17 NOT IN [Eligible ICD–O–;2 Behaviour codes] |
Record rejected |
Table
Feedback report messages (TVAL17)
ICD-O-2 Behaviour code is either invalid or not eligible for the CCR system. |
Core error |
Table
Revision (TVAL17)
Not applicable |
TVAL18
Purpose
Not applicable
Table
Referenced fields (TVAL18)
4 |
Filler |
Not applicable |
Business rules
For Input Tumour records
- Filler can be anything, including blank.
Table
Edit logic (TVAL18)
Not applicable |
Not applicable |
Table
Feedback report messages (TVAL18)
Not applicable |
Not applicable |
Table
Revision (TVAL18)
Edit removed: Filler can be anything, including blank. |
Note
This empty validation is kept as a placeholder for future requirement implementation.
TVAL19
Purpose
This edit validates the laterality code.
Table
Referenced fields (TVAL19)
1 |
Tumour record type |
TRECTYPE |
1 |
Laterality |
TLATERAL |
Business rules
For Add and Update Tumour records
- Laterality must be one of the Eligible laterality codes22.
Table
Edit logic (TVAL19)
T5 IN ['1', '2'] AND T19 NOT IN [Eligible laterality codes] |
Record rejected |
Table
Feedback report messages (TVAL19)
Laterality code is invalid. |
Core error |
Table
Revision (TVAL19)
Not applicable |
TVAL20
Purpose
Not applicable
Table
Referenced fields (TVAL20)
1 |
Filler |
Not applicable |
Business rules
For Input Tumour records
- Filler can be anything, including blank.
Table
Edit logic TVAL20)
Not applicable |
Not applicable |
Table
Feedback report messages (TVAL20)
Not applicable |
Not applicable |
Table
Revision (TVAL20)
Edit removed: Filler can be anything, including blank. |
Note:
This empty validation is kept as a placeholder for future requirement implementation.
TVAL21
Purpose
This edit validates the ICD-O-3 Histology code.
Table
Referenced fields (TVAL21)
1 |
Tumour record type |
TRECTYPE |
4 |
ICD-O-3 Histology |
TICD_O3H |
Business rules
For Add and Update Tumour records
- ICD-O-3 Histology must be one of the Eligible ICD–O–3 Histology codes12,23.
Table
Edit logic (TVAL21)
T5 IN ['1', '2'] AND T21 NOT IN [Eligible ICD-O-3 Histology codes] |
Record rejected |
Table
Feedback report messages (TVAL21)
ICD-O-3 Histology code is either invalid or not eligible for the CCR System. |
Core error |
Table
Revision (TVAL21)
Edit renamed: Current edit was formerly known as Validation edit No.21M. |
TVAL22
Purpose
This edit validates the ICD-O-3 Behaviour code.
Table
Referenced fields TVAL22)
1 |
Tumour record type |
TRECTYPE |
1 |
ICD-O-3 Behaviour |
TICD_O3B |
Business rules
For Add and Update Tumour records
- ICD-O-3 Behaviour must be one of the Eligible ICD–O–3 Behaviour codes24.
Table
Edit logic (TVAL22)
T5 IN ['1', '2'] AND T22 NOT IN [Eligible ICD–O–3 Behaviour codes] |
Record rejected |
Table
Feedback report messages TVAL22)
ICD-O-3 Behaviour code is either invalid or not eligible for the CCR system. |
Core error |
Table
Revision (TVAL22)
Edit reorganized: Edit formerly known as Validation edit No.22 moved to TVAL26. Edit renamed: Current edit was formerly known as Validation edit No.21B. |
TVAL23
Purpose
This edit validates the grade, differentiation or cell indicator code.
Table
Referenced fields (TVAL23)
1 |
Tumour record type |
TRECTYPE |
1 |
Grade, differentiation or cell indicator |
TGRADE |
Business rules
For Add and Update Tumour records
- Grade, differentiation or cell indicator must be one of the Eligible grade, differentiation or cell indicator codes25.
Table
Edit logic (TVAL23)
T5 IN ['1', '2'] AND T23 NOT IN [Eligible grade, differentiation or cell indicator codes] |
Record rejected |
Table
Feedback report messages (TVAL23)
Grade, differentiation or cell indicator code is invalid. |
Core error |
Table
Revision (TVAL23)
Edit reorganized: Edit formerly known as Validation edit No.23 moved to TVAL24. Edit added: New edit. |
TVAL24
Purpose
This edit validates the method used to establish the date of diagnosis code.
Table
Referenced fields (TVAL24)
1 |
Tumour record type |
TRECTYPE |
4 |
First 4 digits of T12 (year of date of diagnosis) |
Not applicable |
1 |
Method used to establish the date of diagnosis |
TMETHUSED |
Business rules
For Add and Update Tumour records
- Method used to establish the date of diagnosis must be one of the Eligible method used to establish the date of diagnosis codes26.
Table
Edit logic (TVAL24)
T5 IN ['1', '2'] AND (T12.YEAR >= '1992' and T12.YEAR <= '2009') AND T24 NOT IN [0,1,2,3,4,5,6,7,8,9] |
Record rejected |
T5 IN ['1', '2'] AND (T12.YEAR >= '2010') AND T24 NOT IN [0,1,2,3,4,5,6,7,8,9,10] |
Record rejected |
Table
Feedback report messages (TVAL24)
Method used to establish the date of diagnosis code is invalid (Date of diagnosis 1992 to 2009). |
Core error |
Method used to establish the date of diagnosis code is invalid (Date of diagnosis 2010 and onwards). |
Core error |
Table
Revision(TVAL24)
Referenced Fields: T12.YEAR added Edit Logic: New sub-edit added, T12.YEAR added and new code added to eligible method used to establish the date of diagnosis codes. Feedback report messages: New feedback report message added for new sub-edit. |
Edit reorganized: Edit formerly known as Validation edit No.24 moved to TVAL25. Edit renamed: Current edit formerly known as Validation edit No.23. |
TVAL25
Purpose
This edit validates the diagnostic confirmation code.
Table
Referenced fields (TVAL25)
1 |
Tumour record type |
TRECTYPE |
4 |
First 4 digits of T12 (year of date of diagnosis) |
Not applicable |
1 |
Diagnostic Confirmation |
TMETHCONF |
Business rules
For Add and Update Tumour records
- Diagnostic confirmation must be one of the Eligible diagnostic confirmation codes27.
Table
Edit logic (TVAL25)
T5 IN ['1', '2'] AND (T12.YEAR >= '1992' and T12.YEAR <= '2009') AND T25 NOT IN [0,1,2,3,4,5,6,7,8,9] |
Record rejected |
T5 IN ['1', '2'] AND (T12.YEAR >= '2010') AND T25 NOT IN [0,1,2,3,4,5,6,7,8,9,10] |
Record rejected |
Table
Feedback report messages (TVAL25)
Diagnostic confirmation code is invalid (Date of diagnosis 1992 to 2009) |
Core error |
Diagnostic confirmation code is invalid (Date of diagnosis 2010 and onwards). |
Core error |
Table
Revision (TVAL25)
Referenced Fields: T12.YEAR added Edit Logic: New sub-edit added, T12.YEAR added and new code added to eligible diagnostic confirmation codes. Feedback report messages: New feedback report message added for new sub-edit. |
Edit renamed: Current edit formerly known as Validation edit No.24. |
TVAL26
Purpose
This edit validates the tumour date of transmission.
Table
Referenced fields (TVAL26)
8 |
Tumour date of transmission |
TDATTRAN |
4 |
First 4 digits of T26 (year of date of transmission) |
Not applicable |
2 |
5th and 6th digits of T26 (month of date of transmission) |
Not applicable |
2 |
7th and 8th digits of T26 (day of date of transmission) |
Not applicable |
Table
Other parameters (TVAL26)
8 |
Statistics Canada loading date: Date on the Statistics Canada computer clock when the data are loaded on the CCR database. |
Business rules
For Input Tumour records
, Tumour date of transmission
- Cannot be blank.
- Must be exclusively composed of numbers: 0 to 9.
- Must be 8 digits long.
- Must be a valid calendar date.
- Must be within the previous 10 months from Statistics Canada loading date.
Table
Edit logic (TVAL26)
T26 IS NULL |
Record rejected |
T26 IS NOT NULL AND (LENGTH (T26) <> 8 OR NOT IS_COMPOSED_OF (T26, '0123456789')) |
Record rejected |
T26 IS NOT NULL AND LENGTH (T26) = 8 AND IS_COMPOSED_OF (T26, '0123456789') AND NOT IS_VALID_DATE (T26) |
Record rejected |
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 |
T26 IS NOT NULL AND LENGTH (T26) = 8 AND IS_COMPOSED_OF (T26, '0123456789') AND IS_VALID_DATE (T26) AND T26 < (LOAD_DATE – 10 months) |
Record rejected |
Table
Feedback report messages (TVAL26)
Tumour date of transmission is missing. |
Core fatal error |
Tumour date of transmission is not 8 digits long. |
Core fatal error |
Tumour date of transmission is not a valid calendar date. |
Core fatal error |
Tumour date of transmission is after Statistics Canada loading date. |
Core fatal error |
Tumour date of transmission is more than 10 months before Statistics Canada loading date. |
Core fatal error |
Table
Revision (TVAL26)
Edit renamed: Current edit formerly known as Validation edit No.22. |
TVAL27
Purpose
This edit validates CS tumour size.
Table
Referenced fields (TVAL27)
1 |
Tumour record type |
TRECTYPE |
4 |
First 4 digits of T12 (year of date of diagnosis) |
Not applicable |
4 |
ICD-O-2/3 Topography |
TICD_O2T |
4 |
ICD–O–3 Histology |
TICD_O3H |
3 |
CS tumour size |
TCSTSIZE |
3 |
CS extension |
TCSEXTN |
1 |
CS tumour size/ext eval |
TCSEVAL |
3 |
CS lymph nodes |
TCSLNODE |
1 |
CS lymph nodes eval |
TCSLNEVAL |
2 |
Regional nodes examined |
TCSRNEXAM |
2 |
Regional nodes positive |
TCSRNPOS |
2 |
CS mets at dx |
TCSMDIAG |
1 |
CS mets eval |
TCSMEVAL |
3 |
CS site-specific factor 1 |
TCSSSF1 |
3 |
CS site-specific factor 2 |
TCSSSF2 |
3 |
CS site-specific factor 3 |
TCSSSF3 |
3 |
CS site-specific factor 4 |
TCSSSF4 |
3 |
CS site-specific factor 5 |
TCSSSF5 |
3 |
CS site-specific factor 6 |
TCSSSF6 |
6 |
CS version input original |
TCSVERINORIG |
6 |
CS version input current |
TCSVERINCUR |
Business rules
For Add and Update Tumour records within the
CCR collaborative staging scope
28 and with at least one known CS variable
- CS tumour size must be valid according to the recommended version of the AJCC CS Algorithm with respect to the CS schema (derived from ICD-O-2/3 Topography and ICD-O-3 Histology).
Table
Edit logic (TVAL27)
T5 IN ['1', '2'] AND T12.YEAR >= '2004' AND T64 = NULL AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T52 <>'999999') AND NOT VALID_CS_TUMOUR_SIZE(T15, T21, T27) |
CS data items filled with 'R' at posting. |
Edit for CSV2 to follow |
|
Table
Feedback report messages (TVAL27)
CS tumour size is invalid for the corresponding CS Schema, based on the recommended version of the AJCC CS Algorithm (using CSV1). |
CS error |
Edit for CSV2 to follow |
|
Table
Revision (TVAL27)
Referenced Fields: Name and acronym of CS version 1st(TCSFVER) changed to CS version input original (TCSVERINORIG). Name and acronym of CS reg nodes eval (TCSRNEVAL) changed to CS lymph node eval (TCSLNEVAL).Length of CS Extension and CS lymph nodes has been changed from 2 to 3. CS Version input current has been added. Edit Logic and Feedback report messages: CS Version input current is checked to make sure fields are the correct length according to CS Version 1 or CS Version 2. |
Referenced fields, Business Rules, Edit logic and Feedback report messages updated: Validation is now done using the recommended version of the AJCC CS algorithm |
Edit added: New edit. |
TVAL28
Purpose
This edit validates CS extension.
Table
Referenced fields (TVAL28)
1 |
Tumour record type |
TRECTYPE |
4 |
First 4 digits of T12 (year of date of diagnosis) |
Not applicable |
4 |
ICD-O-2/3 Topography |
TICD_O2T |
4 |
ICD–O–3 Histology |
TICD_O3H |
3 |
CS tumour size |
TCSTSIZE |
3 |
CS extension |
TCSEXTN |
1 |
CS tumour size/ext eval |
TCSEVAL |
3 |
CS lymph nodes |
TCSLNODE |
1 |
CS lymph nodes eval |
TCSLNEVAL |
2 |
Regional nodes examined |
TCSRNEXAM |
2 |
Regional nodes positive |
TCSRNPOS |
2 |
CS mets at dx |
TCSMDIAG |
1 |
CS mets eval |
TCSMEVAL |
3 |
CS site-specific factor 1 |
TCSSSF1 |
3 |
CS site-specific factor 2 |
TCSSSF2 |
3 |
CS site-specific factor 3 |
TCSSSF3 |
3 |
CS site-specific factor 4 |
TCSSSF4 |
3 |
CS site-specific factor 5 |
TCSSSF5 |
3 |
CS site-specific factor 6 |
TCSSSF6 |
6 |
CS version input original |
TCSVERINORIG |
6 |
CS version input current |
TCSVERINCUR |
Business rules
For Add and Update Tumour records within the
CCR Collaborative staging scope
28 and with at least one known
CS variable,
- CS extension must be valid according to the recommended version of the AJCC CS Algorithm with respect to the CS schema (derived from ICD-O-2/3 Topography and ICD-O-3 Histology).
Table
Edit logic (TVAL28)
T5 IN ['1', '2'] AND T12.YEAR >= '2004' AND T64 = NULL AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T52 <> '999999') AND NOT VALID_CS_EXTENSION(T15, T21, T28) |
CS data items filled with 'R' at posting. |
Edit for CSV2 to follow |
|
Table
Feedback report messages (TVAL28)
CS extension is invalid for the corresponding CS schema, based on the recommended version of the AJCC CS Algorithm (using CSV1). |
CS error |
Edit for CSV2 to follow |
|
Table
Revision (TVAL28)
Referenced Fields: Name and acronym of CS version 1st (TCSFVER) changed to CS version input original (TCSVERINORIG). Name and acronym of CS reg nodes eval (TCSRNEVAL) changed to CS lymph node eval (TCSLNEVAL). Length of CS Extension and CS lymph nodes has been changed from 2 to 3. CS Version input current has been added. Edit Logic and Feedback report messages: CS Version input current is checked to make sure fields are the correct length according to CS Version 1 or CS Version 2. |
Referenced fields, Business Rules, Edit logic and Feedback report messages updated: Validation is now done using the recommended version of the AJCC CS algorithm |
Edit added: New edit. |
TVAL29
Purpose
This edit validates CS tumour size/ext eval.
Table
Referenced fields (TVAL29)
1 |
Tumour record type |
TRECTYPE |
4 |
First 4 digits of T12 (year of date of diagnosis) |
Not applicable |
4 |
ICD-O-2/3 Topography |
TICD_O2T |
4 |
ICD–O–3 Histology |
TICD_O3H |
3 |
CS tumour size |
TCSTSIZE |
3 |
CS extension |
TCSEXTN |
1 |
CS tumour size/ext eval |
TCSEVAL |
3 |
CS lymph nodes |
TCSLNODE |
1 |
CS lymph nodes eval |
TCSLNEVAL |
2 |
Regional nodes examined |
TCSRNEXAM |
2 |
Regional nodes positive |
TCSRNPOS |
2 |
CS mets at dx |
TCSMDIAG |
1 |
CS mets eval |
TCSMEVAL |
3 |
CS site-specific factor 1 |
TCSSSF1 |
3 |
CS site-specific factor 2 |
TCSSSF2 |
3 |
CS site-specific factor 3 |
TCSSSF3 |
3 |
CS site-specific factor 4 |
TCSSSF4 |
3 |
CS site-specific factor 5 |
TCSSSF5 |
3 |
CS site-specific factor 6 |
TCSSSF6 |
6 |
CS version input original |
TCSVERINORIG |
6 |
CS version input current |
TCSVERINCUR |
Business rules
For Add and Update Tumour records within the
CCR collaborative staging scope
28 and with at least one known CS variable
- CS tumour size/ext eval must be valid according to the recommended version of the AJCC CS Algorithm with respect to the CS schema (derived from ICD-O-2/3 Topography and ICD-O-3 Histology).
Table
Edit logic (TVAL29)
T5 IN ['1', '2'] AND T12.YEAR >= '2004' AND T64 = NULL AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T52 <> '999999') AND NOT VALID _CS_TUMOUR_SIZE/EXT_EVAL(T15, T21, T29) |
CS data items filled with 'R' at posting. |
Edit for CSV2 to follow |
|
Table
Feedback report messages (TVAL29)
CS tumour size/ext eval is invalid for the corresponding CS schema, based on the recommended version of the AJCC CS Algorithm (using CSV1). |
CS error |
Edit for CSV2 to follow |
|
Table
Revision (TVAL29)
Referenced Fields: Name and acronym of CS version 1st (TCSFVER) changed to CS version input original (TCSVERINORIG). Name and acronym of CS reg nodes eval (TCSRNEVAL) changed to CS lymph node eval (TCSLNEVAL). Length of CS Extension and CS lymph nodes has been changed from 2 to 3. CS Version input current has been added. Edit Logic and Feedback report messages: CS Version input current is checked to make sure fields are the correct length according to CS Version 1 or CS Version 2. |
Referenced fields, Business Rules, Edit logic and Feedback report messages updated: Validation is now done using the recommended version of the AJCC CS algorithm. |
Edit added: New edit. |
TVAL30
Purpose
This edit validates CS lymph nodes.
Table
Referenced fields (TVAL30)
1 |
Tumour record type |
TRECTYPE |
4 |
First 4 digits of T12 (year of date of diagnosis) |
Not applicable |
4 |
ICD-O-2/3 Topography |
TICD_O2T |
4 |
ICD–O–3 Histology |
TICD_O3H |
3 |
CS tumour size |
TCSTSIZE |
3 |
CS extension |
TCSEXTN |
1 |
CS tumour size/ext eval |
TCSEVAL |
3 |
CS lymph nodes |
TCSLNODE |
1 |
CS lymph nodes eval |
TCSLNEVAL |
2 |
Regional nodes examined |
TCSRNEXAM |
2 |
Regional nodes positive |
TCSRNPOS |
2 |
CS mets at dx |
TCSMDIAG |
1 |
CS mets eval |
TCSMEVAL |
3 |
CS site-specific factor 1 |
TCSSSF1 |
3 |
CS site-specific factor 2 |
TCSSSF2 |
3 |
CS site-specific factor 3 |
TCSSSF3 |
3 |
CS site-specific factor 4 |
TCSSSF4 |
3 |
CS site-specific factor 5 |
TCSSSF5 |
3 |
CS site-specific factor 6 |
TCSSSF6 |
6 |
CS version input original |
TCSVERINORIG |
6 |
CS version input current |
TCSVERINCUR |
Business rules
For Add and Update Tumour records within the
CCR collaborative staging scope
28 and with at least one known CS variable
- CS lymph nodes must be valid according to the recommended version of the AJCC CS Algorithm with respect to the CS schema (derived from ICD-O-2/3 Topography and ICD-O-3 Histology).
Table
Edit logic (TVAL30)
T5 IN ['1', '2'] AND T12.YEAR >= '2004' AND T64 = NULL AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T52 <> '999999') AND NOT VALID CS_LYMPH_NODES(T15, T21, T30) |
CS data items filled with 'R' at posting. |
Edit for CSV2 to follow |
|
Table
Feedback report messages (TVAL30)
CS lymph nodes is invalid for the corresponding CS schema, based on the recommended version of the AJCC CS Algorithm (using CSV1). |
CS error |
Edit for CSV2 to follow |
|
Table
Revision (TVAL30)
Referenced Fields: Name and acronym of CS version 1st (TCSFVER) changed to CS version input original (TCSVERINORIG). Name and acronym of CS reg nodes eval (TCSRNEVAL) changed to CS lymph node eval (TCSLNEVAL). Length of CS Extension and CS lymph nodes has been changed from 2 to 3. CS Version input current has been added. Edit Logic and Feedback report messages: CS Version input current is checked to make sure fields are the correct length according to CS Version 1 or CS Version 2. |
Referenced fields, Business Rules, Edit logic and Feedback report messages updated: Validation is now done using the recommended version of the AJCC CS algorithm |
Edit added: New edit. |
TVAL31
Purpose
This edit validates CS lymph nodes eval.
Table
Referenced fields (TVAL31)
1 |
Tumour record type |
TRECTYPE |
4 |
First 4 digits of T12 (year of date of diagnosis) |
Not applicable |
4 |
ICD-O-2/3 Topography |
TICD_O2T |
4 |
ICD–O–3 Histology |
TICD_O3H |
3 |
CS tumour size |
TCSTSIZE |
3 |
CS extension |
TCSEXTN |
1 |
CS tumour size/ext eval |
TCSEVAL |
3 |
CS lymph nodes |
TCSLNODE |
1 |
CS lymph nodes eval |
TCSLNEVAL |
2 |
Regional nodes examined |
TCSRNEXAM |
2 |
Regional nodes positive |
TCSRNPOS |
2 |
CS mets at dx |
TCSMDIAG |
1 |
CS mets eval |
TCSMEVAL |
3 |
CS site-specific factor 1 |
TCSSSF1 |
3 |
CS site-specific factor 2 |
TCSSSF2 |
3 |
CS site-specific factor 3 |
TCSSSF3 |
3 |
CS site-specific factor 4 |
TCSSSF4 |
3 |
CS site-specific factor 5 |
TCSSSF5 |
3 |
CS site-specific factor 6 |
TCSSSF6 |
6 |
CS version input original |
TCSVERINORIG |
6 |
CS version input current |
TCSVERINCUR |
Business rules
For Add and Update Tumour records within the
CCR collaborative staging scope
28 and with at least one known CS variable
- CS lymph nodes eval must be valid according to the recommended version of the AJCC CS Algorithm with respect to the CS schema (derived from ICD-O-2/3 Topography and ICD-O-3 Histology).
Table
Edit logic (TVAL31)
T5 IN ['1', '2'] AND T12.YEAR >= '2004' AND T64 = NULL AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T52 <> '999999') AND NOT VALID_CS_REG_NODES_EVAL(T15, T21, T31) |
CS data items filled with 'R' at posting. |
Edit for CSV2 to follow |
|
Table
Feedback report messages (TVAL31)
CS lymph nodes eval is invalid for the corresponding CS Schema, based on the recommended version of the AJCC CS Algorithm.(using CSV1) |
CS error |
Edit for CSV2 to follow |
|
Table
Revision (TVAL31)
Referenced Fields: Name and acronym of CS version 1st (TCSFVER) changed to CS version input original (TCSVERINORIG). Name and acronym of CS reg nodes eval (TCSRNEVAL) changed to CS lymph node eval (TCSLNEVAL). Length of CS Extension and CS lymph nodes has been changed from 2 to 3. CS Version input current has been added. Edit Logic and Feedback report messages: CS Version input current is checked to make sure fields are the correct length according to CS Version 1 or CS Version 2. |
Referenced fields, Business Rules, Edit logic and Feedback report messages updated: Validation is now done using the recommended version of the AJCC CS algorithm |
Edit added: New edit. |
TVAL32
Purpose
This edit validates regional nodes examined.
Table
Referenced fields (TVAL32)
1 |
Tumour record type |
TRECTYPE |
4 |
First 4 digits of T12 (year of date of diagnosis) |
Not applicable |
4 |
ICD-O-2/3 Topography |
TICD_O2T |
4 |
ICD–O–3 Histology |
TICD_O3H |
3 |
CS tumour size |
TCSTSIZE |
3 |
CS extension |
TCSEXTN |
1 |
CS tumour size/ext eval |
TCSEVAL |
3 |
CS lymph nodes |
TCSLNODE |
1 |
CS lymph nodes eval |
TCSLNEVAL |
2 |
Regional nodes examined |
TCSRNEXAM |
2 |
Regional nodes positive |
TCSRNPOS |
2 |
CS mets at dx |
TCSMDIAG |
1 |
CS mets eval |
TCSMEVAL |
3 |
CS site-specific factor 1 |
TCSSSF1 |
3 |
CS site-specific factor 2 |
TCSSSF2 |
3 |
CS site-specific factor 3 |
TCSSSF3 |
3 |
CS site-specific factor 4 |
TCSSSF4 |
3 |
CS site-specific factor 5 |
TCSSSF5 |
3 |
CS site-specific factor 6 |
TCSSSF6 |
6 |
CS version input original |
TCSVERINORIG |
6 |
CS version input current |
TCSVERINCUR |
Business rules
For Add and Update Tumour records within the
CCR collaborative staging scope
28 and with at least one known CS variable
- Regional nodes examined must be valid according to the recommended version of the AJCC CS Algorithm with respect to the CS schema (derived from ICD-O-2/3 Topography and ICD-O-3 Histology).
Table
Edit logic (TVAL32)
T5 IN ['1', '2'] AND T12.YEAR >= '2004' AND T64 = NULL AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T52 <> '999999') AND NOT VALID_REGIONAL_NODES_EXAMINED(T15, T21, T32) |
CS data items filled with 'R' at posting. |
Edit for CSV2 to follow |
|
Table
Feedback report messages (TVAL32)
Regional nodes examined is invalid for the corresponding CS schema, based on the recommended version of the AJCC CS Algorithm (using CSV1). |
CS error |
Edit for CSV2 to follow |
|
Table
Revision (TVAL32)
Referenced Fields: Name and acronym of CS version 1st (TCSFVER) changed to CS version input original (TCSVERINORIG). Name and acronym of CS reg nodes eval (TCSRNEVAL) changed to CS lymph node eval (TCSLNEVAL). Length of CS Extension and CS lymph nodes has been changed from 2 to 3. CS Version input current has been added. Edit Logic and Feedback report messages: CS Version input current is checked to make sure fields are the correct length according to CS Version 1 or CS Version 2. |
Referenced fields, Business Rules, Edit logic and Feedback report messages updated: Validation is now done using the recommended version of the AJCC CS algorithm |
Edit added: New edit. |
TVAL33
Purpose
This edit validates regional nodes positive.
Table
Referenced fields (TVAL33)
1 |
Tumour record type |
TRECTYPE |
4 |
First 4 digits of T12 (year of date of diagnosis) |
Not applicable |
4 |
ICD-O-2/3 Topography |
TICD_O2T |
4 |
ICD–O–3 Histology |
TICD_O3H |
3 |
CS tumour size |
TCSTSIZE |
3 |
CS extension |
TCSEXTN |
1 |
CS tumour size/ext eval |
TCSEVAL |
3 |
CS lymph nodes |
TCSLNODE |
1 |
CS lymph nodes eval |
TCSLNEVAL |
2 |
Regional nodes examined |
TCSRNEXAM |
2 |
Regional nodes positive |
TCSRNPOS |
2 |
CS mets at dx |
TCSMDIAG |
1 |
CS mets eval |
TCSMEVAL |
3 |
CS site-specific factor 1 |
TCSSSF1 |
3 |
CS site-specific factor 2 |
TCSSSF2 |
3 |
CS site-specific factor 3 |
TCSSSF3 |
3 |
CS site-specific factor 4 |
TCSSSF4 |
3 |
CS site-specific factor 5 |
TCSSSF5 |
3 |
CS site-specific factor 6 |
TCSSSF6 |
6 |
CS version input original |
TCSVERINORIG |
6 |
CS version input current |
TCSVERINCUR |
Business rules
For Add and Update Tumour records within the
CCR collaborative staging scope
28 and with at least one known CS variable
- Regional nodes positive must be valid according to the recommended version of the AJCC CS Algorithm with respect to the CS schema (derived from ICD-O-2/3 Topography and ICD-O-3 Histology).
Table
Edit logic (TVAL33)
T5 IN ['1', '2'] AND T12.YEAR >= '2004' AND T64 = NULL AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T52 <> '999999') AND NOT VALID_REGIONAL_NODES_POSITIVE(T15, T21, T33) |
CS data items filled with 'R' at posting. |
Edit for CSV2 to follow |
|
Table
Feedback report messages TVAL33)
Regional nodes positive is invalid for the corresponding CS Schema, based on the recommended version of the AJCC CS Algorithm.(using CSV1). |
CS error |
Edit for CSV2 to follow |
|
Table
Revision (TVAL33)
Referenced Fields: Name and acronym of CS version 1st (TCSFVER) changed to CS version input original (TCSVERINORIG). Name and acronym of CS reg nodes eval (TCSRNEVAL) changed to CS lymph node eval (TCSLNEVAL). Length of CS Extension and CS lymph nodes has been changed from 2 to 3. CS Version input current has been added. Edit Logic and Feedback report messages: CS Version input current is checked to make sure fields are the correct length according to CS Version 1 or CS Version 2. |
Referenced fields, Business Rules, Edit logic and Feedback report messages updated: Validation is now done using the recommended version of the AJCC CS algorithm |
Edit added: New edit. |
TVAL34
Purpose
This edit validates CS mets at dx.
Table
Referenced fields (TVAL34)
1 |
Tumour record type |
TRECTYPE |
4 |
First 4 digits of T12 (year of date of diagnosis) |
Not applicable |
4 |
ICD-O-2/3 Topography |
TICD_O2T |
4 |
ICD–O–3 Histology |
TICD_O3H |
3 |
CS tumour size |
TCSTSIZE |
3 |
CS extension |
TCSEXTN |
1 |
CS tumour size/ext eval |
TCSEVAL |
3 |
CS lymph nodes |
TCSLNODE |
1 |
CS lymph nodes eval |
TCSLNEVAL |
2 |
Regional nodes examined |
TCSRNEXAM |
2 |
Regional nodes positive |
TCSRNPOS |
2 |
CS mets at dx |
TCSMDIAG |
1 |
CS mets eval |
TCSMEVAL |
3 |
CS site-specific factor 1 |
TCSSSF1 |
3 |
CS site-specific factor 2 |
TCSSSF2 |
3 |
CS site-specific factor 3 |
TCSSSF3 |
3 |
CS site-specific factor 4 |
TCSSSF4 |
3 |
CS site-specific factor 5 |
TCSSSF5 |
3 |
CS site-specific factor 6 |
TCSSSF6 |
6 |
CS version input original |
TCSVERINORIG |
6 |
CS version input current |
TCSVERINCUR |
Business rules
For Add and Update Tumour records within the
CCR collaborative staging scope
28 and with at least one known CS variable
- CS mets at dx must be valid according to the recommended version of the AJCC CS Algorithm with respect to the CS schema (derived from ICD-O-2/3 Topography and ICD-O-3 Histology).
Table
Edit logic (TVAL34)
T5 IN ['1', '2'] AND T12.YEAR >= '2004' AND T64 = NULL AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38 <>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T52 <> '999999') AND NOT VALID_CS_METS_AT_DX(T15, T21, T34) |
CS data items filled with 'R' at posting. |
Edit for CSV2 to follow |
|
Table
Feedback report messages (TVAL34)
CS mets at dx is invalid for the corresponding CS schema, based on the recommended version of the AJCC CS Algorithm (using CSV1) |
CS error |
Edit for CSV2 to follow |
|
Table
Revision (TVAL34)
Referenced Fields: Name and acronym of CS version 1st (TCSFVER) changed to CS version input original (TCSVERINORIG). Name and acronym of CS reg nodes eval (TCSRNEVAL) changed to CS lymph node eval (TCSLNEVAL). Length of CS Extension and CS lymph nodes has been changed from 2 to 3. CS Version input current has been added. Edit Logic and Feedback report messages: CS Version input current is checked to make sure fields are the correct length according to CS Version 1 or CS Version 2. |
Referenced fields, Business Rules, Edit logic and Feedback report messages updated: Validation is now done using the recommended version of the AJCC CS algorithm |
Edit added: New edit. |
TVAL35
Purpose
This edit validates CS mets eval.
Business rules
Table
Referenced fields (TVAL35)
1 |
Tumour record type |
TRECTYPE |
4 |
First 4 digits of T12 (year of date of diagnosis) |
Not applicable |
4 |
ICD-O-2/3 Topography |
TICD_O2T |
4 |
ICD–O–3 Histology |
TICD_O3H |
3 |
CS tumour size |
TCSTSIZE |
3 |
CS extension |
TCSEXTN |
1 |
CS tumour size/ext eval |
TCSEVAL |
3 |
CS lymph nodes |
TCSLNODE |
1 |
CS lymph nodes eval |
TCSLNEVAL |
2 |
Regional nodes examined |
TCSRNEXAM |
2 |
Regional nodes positive |
TCSRNPOS |
2 |
CS mets at dx |
TCSMDIAG |
1 |
CS mets eval |
TCSMEVAL |
3 |
CS site-specific factor 1 |
TCSSSF1 |
3 |
CS site-specific factor 2 |
TCSSSF2 |
3 |
CS site-specific factor 3 |
TCSSSF3 |
3 |
CS site-specific factor 4 |
TCSSSF4 |
3 |
CS site-specific factor 5 |
TCSSSF5 |
3 |
CS site-specific factor 6 |
TCSSSF6 |
6 |
CS version input original |
TCSVERINORIG |
6 |
CS version input current |
TCSVERINCUR |
For Add and Update Tumour records within the
CCR collaborative staging scope
28 and with at least one known CS variable
- CS mets eval must be valid according to the recommended version of the AJCC CS Algorithm with respect to the CS schema (derived from ICD-O-2/3 Topography and ICD-O-3 Histology).
Table
Edit logic (TVAL35)
T5 IN ['1', '2']AND T12.YEAR >= '2004' AND T64 = NULL AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T52 <> '999999') AND NOT VALID_CS_METS_EVAL(T15, T21, T35) |
CS data items filled with 'R' at posting. |
Edit for CSV2 to follow |
|
Table
Feedback report messages (TVAL35)
CS mets eval is invalid for the corresponding CS schema, based on the recommended version of the AJCC CS Algorithm (using CSV1). |
CS error |
Edit for CSV2 to follow |
|
Table
Revision (TVAL35)
Referenced Fields: Name and acronym of CS version 1st (TCSFVER) changed to CS version input original (TCSVERINORIG). Name and acronym of CS reg nodes eval (TCSRNEVAL) changed to CS lymph node eval (TCSLNEVAL). Length of CS Extension and CS lymph nodes has been changed from 2 to 3. CS Version input current has been added. Edit Logic and Feedback report messages: CS Version input current is checked to make sure fields are the correct length according to CS Version 1 or CS Version 2. |
Referenced fields, Business Rules, Edit logic and Feedback report messages updated: Validation is now done using the recommended version of the AJCC CS algorithm |
Edit added: New edit. |
TVAL36
Purpose
This edit validates CS site-specific factor 1.
Table
Referenced fields (TVAL36)
1 |
Tumour record type |
TRECTYPE |
4 |
First 4 digits of T12 (year of date of diagnosis) |
Not applicable |
4 |
ICD-O-2/3 Topography |
TICD_O2T |
4 |
ICD–O–3 Histology |
TICD_O3H |
3 |
CS tumour size |
TCSTSIZE |
3 |
CS extension |
TCSEXTN |
1 |
CS tumour size/ext eval |
TCSEVAL |
3 |
CS lymph nodes |
TCSLNODE |
1 |
CS lymph nodes eval |
TCSLNEVAL |
2 |
Regional nodes examined |
TCSRNEXAM |
2 |
Regional nodes positive |
TCSRNPOS |
2 |
CS mets at dx |
TCSMDIAG |
1 |
CS mets eval |
TCSMEVAL |
3 |
CS site-specific factor 1 |
TCSSSF1 |
3 |
CS site-specific factor 2 |
TCSSSF2 |
3 |
CS site-specific factor 3 |
TCSSSF3 |
3 |
CS site-specific factor 4 |
TCSSSF4 |
3 |
CS site-specific factor 5 |
TCSSSF5 |
3 |
CS site-specific factor 6 |
TCSSSF6 |
6 |
CS version input original |
TCSVERINORIG |
6 |
CS version input current |
TCSVERINCUR |
Business rules
For Add and Update Tumour records within the
CCR collaborative staging scope
28 and with at least one known CS variable
- CS site-specific factor 1 must be valid according to the recommended version of the AJCC CS Algorithm with respect to the CS schema (derived from ICD-O-2/3 Topography and ICD-O-3 Histology).
Table
Edit logic (TVAL36)
T5 IN ['1', '2'] AND T12.YEAR >= '2004' AND T64 = NULL AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T52 <> '999999') AND NOT VALID_CS_SITE-SPECIFIC_FACTOR_1(T15, T21, T36) |
CS data items filled with 'R' at posting. |
Edit for CSV2 to follow |
|
Table
Feedback report messages (TVAL36)
CS site-specific factor 1 is invalid for the corresponding CS schema, based on the recommended version of the AJCC CS Algorithm (using CSV1). |
CS error |
Edit for CSV2 to follow |
|
Table
Revision (TVAL36)
Referenced Fields: Name and acronym of CS version 1st (TCSFVER) changed to CS version input original (TCSVERINORIG). Name and acronym of CS reg nodes eval (TCSRNEVAL) changed to CS lymph node eval (TCSLNEVAL). Length of CS Extension and CS lymph nodes has been changed from 2 to 3. CS Version input current has been added. Edit Logic and Feedback report messages: CS Version input current is checked to make sure fields are the correct length according to CS Version 1 or CS Version 2. |
Referenced fields, Business Rules, Edit logic and Feedback report messages updated: Validation is now done using the recommended version of the AJCC CS algorithm. |
Edit added: New edit. |
TVAL37
Purpose
This edit validates CS site-specific factor 2.
Table
Referenced fields (TVAL37)
1 |
Tumour record type |
TRECTYPE |
4 |
First 4 digits of T12 (year of date of diagnosis) |
Not applicable |
4 |
ICD-O-2/3 Topography |
TICD_O2T |
4 |
ICD–O–3 Histology |
TICD_O3H |
3 |
CS tumour size |
TCSTSIZE |
3 |
CS extension |
TCSEXTN |
1 |
CS tumour size/ext eval |
TCSEVAL |
3 |
CS lymph nodes |
TCSLNODE |
1 |
CS lymph nodes eval |
TCSLNEVAL |
2 |
Regional nodes examined |
TCSRNEXAM |
2 |
Regional nodes positive |
TCSRNPOS |
2 |
CS mets at dx |
TCSMDIAG |
1 |
CS mets eval |
TCSMEVAL |
3 |
CS site-specific factor 1 |
TCSSSF1 |
3 |
CS site-specific factor 2 |
TCSSSF2 |
3 |
CS site-specific factor 3 |
TCSSSF3 |
3 |
CS site-specific factor 4 |
TCSSSF4 |
3 |
CS site-specific factor 5 |
TCSSSF5 |
3 |
CS site-specific factor 6 |
TCSSSF6 |
6 |
CS version input original |
TCSVERINORIG |
6 |
CS version input current |
TCSVERINCUR |
Business rules
For Add and Update Tumour records within the
CCR collaborative staging scope
28 and with at least one known CS variable
- CS site-specific factor 2 must be valid according to the recommended version of the AJCC CS Algorithm with respect to the CS schema (derived from ICD-O-2/3 Topography and ICD-O-3 Histology).
Table
Edit logic (TVAL37)
T5 IN ['1', '2'] AND T12.YEAR >= '2004' AND T64 = NULL AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T52 <> '999999') AND NOT VALID_CS_SITE-SPECIFIC_FACTOR_2(T15, T21, T37) |
CS data items filled with 'R' at posting. |
Edit for CSV2 to follow |
|
Table
Feedback report messages (TVAL37)
CS site-specific factor 2 is invalid for the corresponding CS schema, based on the recommended version of the AJCC CS Algorithm (using CSV1). |
CS error |
Edit for CSV2 to follow |
|
Table
Revision (TVAL37)
Referenced Fields: Name and acronym of CS version 1st (TCSFVER) changed to CS version input original (TCSVERINORIG). Name and acronym of CS reg nodes eval (TCSRNEVAL) changed to CS lymph node eval (TCSLNEVAL). Length of CS Extension and CS lymph nodes has been changed from 2 to 3. CS Version input current has been added. Edit Logic and Feedback report messages: CS Version input current is checked to make sure fields are the correct length according to CS Version 1 or CS Version 2. |
Referenced fields, Business Rules, Edit logic and Feedback report messages updated: Validation is now done using the recommended version of the AJCC CS algorithm. |
Edit added: New edit. |
TVAL38
Purpose
This edit validates CS site-specific factor 3.
Table
Referenced fields (TVAL38)
1 |
Tumour record type |
TRECTYPE |
4 |
First 4 digits of T12 (year of date of diagnosis) |
Not applicable |
4 |
ICD-O-2/3 Topography |
TICD_O2T |
4 |
ICD–O–3 Histology |
TICD_O3H |
3 |
CS tumour size |
TCSTSIZE |
3 |
CS extension |
TCSEXTN |
1 |
CS tumour size/ext eval |
TCSEVAL |
3 |
CS lymph nodes |
TCSLNODE |
1 |
CS lymph nodes eval |
TCSLNEVAL |
2 |
Regional nodes examined |
TCSRNEXAM |
2 |
Regional nodes positive |
TCSRNPOS |
2 |
CS mets at dx |
TCSMDIAG |
1 |
CS mets eval |
TCSMEVAL |
3 |
CS site-specific factor 1 |
TCSSSF1 |
3 |
CS site-specific factor 2 |
TCSSSF2 |
3 |
CS site-specific factor 3 |
TCSSSF3 |
3 |
CS site-specific factor 4 |
TCSSSF4 |
3 |
CS site-specific factor 5 |
TCSSSF5 |
3 |
CS site-specific factor 6 |
TCSSSF6 |
6 |
CS version input original |
TCSVERINORIG |
6 |
CS version input current |
TCSVERINCUR |
Business rules
For Add and Update Tumour records within the
CCR collaborative staging scope
28 and with at least one known CS variable
- CS site-specific factor 3 must be valid according to the recommended version of the AJCC CS Algorithm with respect to the CS schema (derived from ICD-O-2/3 Topography and ICD-O-3 Histology).
Table
Edit logic (TVAL38)
T5 IN ['1', '2'] AND T12.YEAR >= '2004' AND T64 = NULL AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T52 <> '999999') AND NOT VALID_CS_SITE-SPECIFIC_FACTOR_3(T15, T21, T38) |
CS data items filled with 'R' at posting. |
Edit for CSV2 to follow |
|
Table
Feedback report messages (TVAL38)
CS site-specific factor 3 is invalid for the corresponding CS schema, based on the recommended version of the AJCC CS Algorithm (using CSV1). |
CS error |
Edit for CSV2 to follow |
|
Table
Revision (TVAL38)
Referenced Fields: Name and acronym of CS version 1st (TCSFVER) changed to CS version input original (TCSVERINORIG). Name and acronym of CS reg nodes eval (TCSRNEVAL) changed to CS lymph node eval (TCSLNEVAL). Length of CS Extension and CS lymph nodes has been changed from 2 to 3. CS Version input current has been added. Edit Logic and Feedback report messages: CS Version input current is checked to make sure fields are the correct length according to CS Version 1 or CS Version 2. |
Referenced fields, Business Rules, Edit logic and Feedback report messages updated: Validation is now done using the recommended version of the AJCC CS algorithm. |
Edit added: New edit. |
TVAL39
Purpose
This edit validates CS site-specific factor 4.
Table
Referenced fields (TVAL39)
1 |
Tumour record type |
TRECTYPE |
4 |
First 4 digits of T12 (year of date of diagnosis) |
Not applicable |
4 |
ICD-O-2/3 Topography |
TICD_O2T |
4 |
ICD–O–3 Histology |
TICD_O3H |
3 |
CS tumour size |
TCSTSIZE |
3 |
CS extension |
TCSEXTN |
1 |
CS tumour size/ext eval |
TCSEVAL |
3 |
CS lymph nodes |
TCSLNODE |
1 |
CS lymph nodes eval |
TCSLNEVAL |
2 |
Regional nodes examined |
TCSRNEXAM |
2 |
Regional nodes positive |
TCSRNPOS |
2 |
CS mets at dx |
TCSMDIAG |
1 |
CS mets eval |
TCSMEVAL |
3 |
CS site-specific factor 1 |
TCSSSF1 |
3 |
CS site-specific factor 2 |
TCSSSF2 |
3 |
CS site-specific factor 3 |
TCSSSF3 |
3 |
CS site-specific factor 4 |
TCSSSF4 |
3 |
CS site-specific factor 5 |
TCSSSF5 |
3 |
CS site-specific factor 6 |
TCSSSF6 |
6 |
CS version input original |
TCSVERINORIG |
6 |
CS version input current |
TCSVERINCUR |
|
Business rules
For Add and Update Tumour records within the
CCR collaborative staging scope
28 and with at least one known CS variable
- CS site-specific factor 4 must be valid according to the recommended version of the AJCC CS Algorithm with respect to the CS schema (derived from ICD-O-2/3 Topography and ICD-O-3 Histology).
Table
Edit logic (TVAL39)
T5 IN ['1', '2'] AND T12.YEAR >= '2004' AND T64 = NULL AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T52 <> '999999') AND NOT VALID_CS_SITE-SPECIFIC_FACTOR_4(T15, T21, T39) |
CS data items filled with 'R' at posting. |
Edit for CSV2 to follow |
|
Table
Feedback report messages (TVAL39)
CS site-specific factor 4 is invalid for the corresponding CS schema, based on the recommended version of the AJCC CS Algorithm (using CSV1). |
CS error |
Edit for CSV2 to follow |
|
Table
Revision (TVAL39)
Referenced Fields: Name and acronym of CS version 1st (TCSFVER) changed to CS version input original (TCSVERINORIG). Name and acronym of CS reg nodes eval (TCSRNEVAL) changed to CS lymph node eval (TCSLNEVAL). Length of CS Extension and CS lymph nodes has been changed from 2 to 3. CS Version input current has been added. Edit Logic and Feedback report messages: CS Version input current is checked to make sure fields are the correct length according to CS Version 1 or CS Version 2. |
Referenced fields, Business Rules, Edit logic and Feedback report messages updated: Validation is now done using the recommended version of the AJCC CS algorithm. |
Edit added: New edit. |
TVAL40
Purpose
This edit validates CS site-specific factor 5.
Table
Referenced fields (TVAL40)
1 |
Tumour record type |
TRECTYPE |
4 |
First 4 digits of T12 (year of date of diagnosis) |
Not applicable |
4 |
ICD-O-2/3 Topography |
TICD_O2T |
4 |
ICD–O–3 Histology |
TICD_O3H |
3 |
CS tumour size |
TCSTSIZE |
3 |
CS extension |
TCSEXTN |
1 |
CS tumour size/ext eval |
TCSEVAL |
3 |
CS lymph nodes |
TCSLNODE |
1 |
CS lymph nodes eval |
TCSLNEVAL |
2 |
Regional nodes examined |
TCSRNEXAM |
2 |
Regional nodes positive |
TCSRNPOS |
2 |
CS mets at dx |
TCSMDIAG |
1 |
CS mets eval |
TCSMEVAL |
3 |
CS site-specific factor 1 |
TCSSSF1 |
3 |
CS site-specific factor 2 |
TCSSSF2 |
3 |
CS site-specific factor 3 |
TCSSSF3 |
3 |
CS site-specific factor 4 |
TCSSSF4 |
3 |
CS site-specific factor 5 |
TCSSSF5 |
3 |
CS site-specific factor 6 |
TCSSSF6 |
6 |
CS version input original |
TCSVERINORIG |
6 |
CS version input current |
TCSVERINCUR |
|
Business rules
For Add and Update Tumour records within the
CCR collaborative staging scope
28and with at least one known CS variable
- CS site-specific factor 5 must be valid according to the recommended version of the AJCC CS Algorithm with respect to the CS schema (derived from ICD-O-2/3 Topography and ICD-O-3 Histology).
Table
Edit logic (TVAL40)
T5 IN ['1', '2'] AND T12.YEAR >= '2004' AND T64 = NULL AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T52 <> '999999') AND NOT VALID_CS_SITE-SPECIFIC_FACTOR_5(T15, T21, T40) |
CS data items filled with 'R' at posting. |
Edit for CSV2 to follow |
|
Table
Feedback report messages (TVAL40)
CS site-specific factor 5 is invalid for the corresponding CS schema, based on the recommended version of the AJCC CS Algorithm (using CSV1). |
CS error |
Edit for CSV2 to follow |
|
Table
Revision (TVAL40)
Referenced Fields: Name and acronym of CS version 1st (TCSFVER) changed to CS version input original (TCSVERINORIG). Name and acronym of CS reg nodes eval (TCSRNEVAL) changed to CS lymph node eval (TCSLNEVAL). Length of CS Extension and CS lymph nodes has been changed from 2 to 3. CS Version input current has been added. Edit Logic and Feedback report messages: CS Version input current is checked to make sure fields are the correct length according to CS Version 1 or CS Version 2. |
2004 |
Edit added: New edit. |
TVAL41
Purpose
This edit validates CS site-specific factor 6.
Table
Referenced fields (TVAL41)
1 |
Tumour record type |
TRECTYPE |
4 |
First 4 digits of T12 (year of date of diagnosis) |
Not applicable |
4 |
ICD–O–2/3 Topography |
TICD_O2T |
4 |
ICD–O–3 Histology |
TICD_O3H |
3 |
CS tumour size |
TCSTSIZE |
3 |
CS extension |
TCSEXTN |
1 |
CS tumour size/ext eval |
TCSEVAL |
3 |
CS lymph nodes |
TCSLNODE |
1 |
CS lymph nodes eval |
TCSLNEVAL |
2 |
Regional nodes examined |
TCSRNEXAM |
2 |
Regional nodes positive |
TCSRNPOS |
2 |
CS mets at dx |
TCSMDIAG |
1 |
CS mets eval |
TCSMEVAL |
3 |
CS site-specific factor 1 |
TCSSSF1 |
3 |
CS site-specific factor 2 |
TCSSSF2 |
3 |
CS site-specific factor 3 |
TCSSSF3 |
3 |
CS site-specific factor 4 |
TCSSSF4 |
3 |
CS site-specific factor 5 |
TCSSSF5 |
3 |
CS site-specific factor 6 |
TCSSSF6 |
6 |
CS version input original |
TCSVERINORIG |
6 |
CS version input current |
TCSVERINCUR |
Business rules
For Add and Update Tumour records within the
CCR collaborative staging scope
28 and with at least one known CS variable
- CS site-specific factor 6 must be valid according to the recommended version of the AJCC CS Algorithm with respect to the CS schema (derived from ICD-O-2/3 Topography and ICD-O-3 Histology).
Table
Edit logic (TVAL41)
T5 IN ['1', '2'] AND T12.YEAR >= '2004' AND T64 = NULL AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T52 <> '999999') AND NOT VALID_CS_SITE-SPECIFIC_FACTOR_6(T15, T21, T41) |
CS data items filled with 'R' at posting. |
Edit for CSV2 to follow |
|
Table
Feedback report messages (TVAL41)
CS site-specific factor 6 is invalid for the corresponding CS schema, based on the recommended version of the AJCC CS Algorithm (using CSV1). |
CS error |
Edit for CSV2 to follow |
|
Table
Revision (TVAL41)
Referenced Fields: Name and acronym of CS version 1st (TCSFVER) changed to CS version input original (TCSVERINORIG). Name and acronym of CS reg nodes eval (TCSRNEVAL) changed to CS lymph node eval (TCSLNEVAL). Length of CS Extension and CS lymph nodes has been changed from 2 to 3. CS Version input current has been added. Edit Logic and Feedback report messages: CS Version input current is checked to make sure fields are the correct length according to CS Version 1 or CS Version 2. |
Referenced fields, Business Rules, Edit logic and Feedback report messages updated: Validation is now done using the recommended version of the AJCC CS algorithm |
Edit added: New edit. |
TVAL42
Purpose
This edit validates AJCC clinical T
Table
Referenced fields (TVAL42)
1 |
Tumour record type |
TRECTYPE |
4 |
First 4 digits of T12 (year of date of diagnosis) |
Not applicable |
4 |
ICD-O-2/3 Topography |
TICD_O2T |
4 |
ICD-O-3 Histology |
TICD_O3H |
1 |
ICD-O-3 Behaviour |
TICD_O3B |
9 |
AJCC clinical T |
TAJCCCLINT |
Business rules
For Add and Update Tumour records within the
CCR AJCC TNM staging scope
29 and Date of Diagnosis is between 2003 and 2007,
- AJCC clinical T must be one of the Eligible AJCC clinical T values for the corresponding site30.
Edit Logic
To simplify the edit logic, let Site X be a given site within the CCR AJCC TNM staging scope. Example: Colorectal, breast or prostate.
Table
Edit logic (TVAL42)
T5 IN ['1', '2'] AND (T12.YEAR >= 2003 AND T12.YEAR <= 2007) AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T42 NOT IN [Eligible AJCC clinical T for Site X] |
AJCC TNM data items filled with 'R' at posting. |
Table
Feedback report messages (TVAL42)
AJCC clinical T is invalid for reported site. |
AJCC TNM error |
Table
Revision (TVAL42)
Edit no longer applicable: Variable T42 no longer reported. |
Edit added: New edit. |
TVAL43
Purpose
This edit validates AJCC clinical N.
Table
Referenced fields (TVAL43)
1 |
Tumour record type |
TRECTYPE |
4 |
First 4 digits of T12 (year of date of diagnosis) |
Not applicable |
4 |
ICD-O-2/3 Topography |
TICD_O2T |
4 |
ICD-O-3 Histology |
TICD_O3H |
1 |
ICD-O-3 Behaviour |
TICD_O3B |
3 |
AJCC clinical N |
TAJCCCLINN |
Business rules
For Add and Update Tumour records within the
CCR AJCC TNM staging scope
29 and Date of Diagnosis is between 2003 and 2007,
- AJCC clinical N must be one of the Eligible AJCC clinical N values for the corresponding site31.
Edit Logic
To simplify the edit logic, let Site X be a given site within the CCR AJCC TNM staging scope. Example : Colorectal, breast or prostate.
Table
Edit logic (TVAL43)
T5 IN ['1', '2'] AND ( T12.YEAR >= 2003 AND T12.YEAR <= 2007) AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T43 NOT IN [Eligible AJCC clinical N for Site X] |
AJCC TNM data items filled with 'R' at posting. |
Table
Feedback report messages (TVAL43)
AJCC clinical N is invalid for reported site. |
AJCC TNM error |
Table
Revision (TVAL43)
Edit no longer applicable: Variable T43 no longer reported. |
Edit added: New edit. |
TVAL44
Purpose
This edit validates AJCC clinical M.
Table
Referenced fields (TVAL44)
1 |
Tumour record type |
TRECTYPE |
4 |
First 4 digits of T12 (year of date of diagnosis) |
Not applicable |
4 |
ICD-O-2/3 Topography |
TICD_O2T |
4 |
ICD-O-3 Histology |
TICD_O3H |
1 |
ICD-O-3 Behaviour |
TICD_O3B |
3 |
AJCC clinical M |
TAJCCCLINM |
Business rules
For Add and Update Tumour records within the
CCR AJCC TNM staging scope
29 and Date of Diagnosis is between 2003 and 2007,
- AJCC clinical M must be one of the Eligible AJCC clinical M values for the corresponding site32.
Edit Logic
To simplify the edit logic, let Site X be a given site within the CCR AJCC TNM staging scope. Ex: Colorectal, breast or prostate.
Table
Edit logic (TVAL44)
T5 IN ['1', '2'] AND (T12.YEAR >= 2003 AND T12.YEAR <=2007) AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T44 NOT IN [Eligible AJCC clinical M for Site X] |
AJCC TNM data items filled with 'R' at posting. |
Table
Feedback report messages (TVAL44)
AJCC clinical M is invalid for reported site. |
AJCC TNM error |
Table
Revision (TVAL44)
Edit no longer applicable: Variable T44 no longer reported. |
Edit added: New edit. |
TVAL45
Purpose
This edit validates AJCC pathologic T.
Table
Referenced fields (TVAL45)
1 |
Tumour record type |
TRECTYPE |
4 |
First 4 digits of T12 (year of date of diagnosis) |
Not applicable |
4 |
ICD-O-2/3 Topography |
TICD_O2T |
4 |
ICD-O-3 Histology |
TICD_O3H |
1 |
ICD-O-3 Behaviour |
TICD_O3B |
9 |
AJCC pathologic T |
TAJCCPATHT |
Business rules
For Add and Update Tumour records within the
CCR AJCC TNM staging scope
29 and Date of Diagnosis is between 2003 and 2007,
- AJCC pathologic T must be one of the Eligible AJCC pathologic T values for the corresponding site33.
Edit Logic
To simplify the edit logic, let Site X be a given site within the CCR AJCC TNM staging scope. Example: Colorectal, breast or prostate.
Table
Edit logic (TVAL45)
T5 IN ['1', '2'] AND (T12.YEAR >= 2003 AND T12.YEAR <=2007) AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T45 NOT IN [Eligible AJCC pathologic T for Site X] |
AJCC TNM data items filled with 'R' at posting. |
Table
Feedback report messages (TVAL45)
AJCC pathologic T is invalid for reported site. |
AJCC TNM error |
Table
Revision (TVAL45)
Edit no longer applicable: Variable T45 no longer reported. |
Edit added: New edit. |
TVAL46
Purpose
This edit validates AJCC pathologic N.
Table
Referenced fields (TVAL46)
1 |
Tumour record type |
TRECTYPE |
4 |
First 4 digits of T12 (year of date of diagnosis) |
Not applicable |
4 |
ICD-O-2/3 Topography |
TICD_O2T |
4 |
ICD-O-3 Histology |
TICD_O3H |
1 |
ICD-O-3 Behaviour |
TICD_O3B |
3 |
AJCC pathologic N |
TAJCCPATHN |
Business rules
For Add and Update Tumour records within the
CCR AJCC TNM staging scope
29 and Date of Diagnosis is between 2003 and 2007,
- AJCC pathologic N must be one of the Eligible AJCC pathologic N values for the corresponding site34.
Edit Logic
To simplify the edit logic, let Site X be a given site within the CCR AJCC TNM staging scope. Example: Colorectal, breast or prostate.
Table
Edit logic (TVAL46)
T5 IN ['1', '2'] AND (T12.YEAR >= 2003 AND T12.YEAR <= 2007) AND T15 IN [Eligible ICD-O-3 Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T46 NOT IN [Eligible AJCC pathologic N for Site X] |
AJCC TNM data items filled with 'R' at posting. |
Table
Feedback report messages (TVAL46)
AJCC pathologic N is invalid for reported site. |
AJCC TNM error |
Table
Revision (TVAL46)
Edit no longer applicable: Variable T46 no longer reported. |
Edit added: New edit. |
TVAL47
Purpose
This edit validates AJCC pathologic M.
Table
Referenced fields (TVAL47)
1 |
Tumour record type |
TRECTYPE |
4 |
First 4 digits of T12 (year of date of diagnosis) |
Not applicable |
4 |
ICD-O-2/3 Topography |
TICD_O2T |
4 |
ICD-O-3 Histology |
TICD_O3H |
1 |
ICD-O-3 Behaviour |
TICD_O3B |
3 |
AJCC pathologic M |
TAJCCPATHM |
Business rules
For Add and Update Tumour records within the
CCR AJCC TNM staging scope
29 and Date of Diagnosis is between 2003 and 2007,
- AJCC pathologic M must be one of the Eligible pathologic M values for the corresponding site35.
Edit Logic
To simplify the edit logic, let Site X be a given site within the CCR AJCC TNM staging scope. Example: Colorectal, breast or prostate.
Table
Edit logic (TVAL47)
T5 IN ['1', '2'] AND (T12.YEAR >= 2003 AND T12.YEAR <= 2007) AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T47 NOT IN [Eligible AJCC pathologic M for Site X] |
AJCC TNM data items filled with 'R' at posting. |
Table
Feedback report messages (TVAL47)
AJCC pathologic M is invalid for reported site. |
AJCC TNM error |
Table
Revision (TVAL47)
Edit no longer applicable: Variable T47 no longer reported. |
Edit added: New edit. |
TVAL48
Purpose
This edit validates AJCC clinical TNM stage group.
Table
Referenced fields (TVAL48)
1 |
Tumour record type |
TRECTYPE |
4 |
First 4 digits of T12 (year of date of diagnosis) |
Not applicable |
4 |
ICD-O-2/3 Topography |
TICD_O2T |
4 |
ICD-O-3 Histology |
TICD_O3H |
1 |
ICD-O-3 Behaviour |
TICD_O3B |
4 |
AJCC clinical TNM stage group |
TAJCCCLINSG |
Business rules
For Add and Update Tumour records within the
CCR AJCC TNM staging scope
29 and Date of Diagnosis is between 2003 and 2007,
- AJCC clinical TNM stage group must be one of the Eligible AJCC clinical TNM stage group values for the corresponding site38.
Edit Logic
To simplify the edit logic, let Site X be a given site within the CCR AJCC TNM staging scope. Example: Colorectal, breast or prostate.
Table
Edit logic (TVAL48)
T5 IN ['1', '2'] AND (T12.YEAR >= 2003 AND T12.YEAR <= 2007) AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T48 NOT IN [Eligible AJCC clinical TNM stage group for Site X] |
AJCC TNM data items filled with 'R' at posting. |
Table
Feedback report messages (TVAL48)
AJCC clinical TNM stage group is invalid for reported site. |
AJCC TNM error |
Table
Revision (TVAL48)
Edit no longer applicable: Variable T48 no longer reported. |
Edit added: New edit. |
TVAL49
Purpose
This edit validates AJCC pathologic TNM stage group.
Table
Referenced fields (TVAL49)
1 |
Tumour record type |
TRECTYPE |
4 |
First 4 digits of T12 (year of date of diagnosis) |
Not applicable |
4 |
ICD-O-2/3 Topography |
TICD_O2T |
4 |
ICD-O-3 Histology |
TICD_O3H |
1 |
ICD-O-3 Behaviour |
TICD_O3B |
4 |
AJCC pathologic TNM stage group |
TAJCCPATHSG |
Business rules
For Add and Update Tumour records within the
CCR AJCC TNM staging scope
29 and Date of Diagnosis is between 2003 and 2007,
- AJCC pathologic TNM stage group must be one of the Eligible AJCC pathologic TNM stage group values for the corresponding site37.
Edit Logic
To simplify the edit logic, let Site X be a given site within the CCR AJCC TNM staging scope. Example: Colorectal, breast or prostate.
Table
Edit logic (TVAL49)
T5 IN ['1', '2'] AND (T12.YEAR >= 2003 AND T12.YEAR <= 2007) AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T49 NOT IN [Eligible AJCC pathologic TNM stage group for Site X] |
AJCC TNM data items filled with 'R' at posting. |
Table
Feedback report messages (TVAL49)
AJCC pathologic TNM stage group is invalid for reported site. |
AJCC TNM error |
Table
Revision (TVAL49)
Edit no longer applicable: Variable T49 no longer reported. |
Edit added: New edit. |
TVAL50
Purpose
This edit validates AJCC TNM stage group.
Table
Referenced fields (TVAL50)
1 |
Tumour record type |
TRECTYPE |
4 |
First 4 digits of T12 (year of date of diagnosis) |
Not applicable |
4 |
ICD-O-2/3 Topography |
TICD_O2T |
4 |
ICD-O-3 Histology |
TICD_O3H |
1 |
ICD-O-3 Behaviour |
TICD_O3B |
4 |
AJCC TNM stage group |
TAJCCSG |
Business rules
For Add and Update Tumour records within the
CCR AJCC TNM staging scope
29 and Date of Diagnosis is between 2003 and 2007,
- AJCC TNM stage group must be one of the Eligible AJCC TNM stage group values for the corresponding site37.
Edit Logic
To simplify the edit logic, let Site X be a given site within the CCR AJCC TNM staging scope. Example: Colorectal, breast or prostate.
Table
Edit logic (TVAL50)
T5 IN ['1', '2'] AND (T12.YEAR >= 2003 AND T12.YEAR <= 2007) AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T50 NOT IN [Eligible AJCC TNM stage group for Site X] |
AJCC TNM data items filled with 'R' at posting. |
Table
Feedback report messages (TVAL50)
AJCC TNM stage group is invalid for reported site. |
AJCC TNM error |
Table
Revision (TVAL50)
Edit no longer applicable: Variable T50 no longer reported. |
Edit added: New edit. |
TVAL51
Purpose
This edit validates AJCC edition number code.
Table
Referenced fields (TVAL51)
1 |
Tumour record type |
TRECTYPE |
4 |
First 4 digits of T12 (year of date of diagnosis) |
Not applicable |
4 |
ICD-O-2/3 Topography |
TICD_O2T |
4 |
ICD-O-3 Histology |
TICD_O3H |
1 |
ICD-O-3 Behaviour |
TICD_O3B |
2 |
AJCC edition number |
TAJCCEDNUM |
Business rules
For Add and Update Tumour records within the
CCR AJCC TNM staging scope
29 and Date of Diagnosis is between 2003 and 2007,
- AJCC edition number must be one of the Eligible AJCC edition number codes38.
Edit Logic
To simplify the edit logic, let Site X be a given site within the CCR AJCC TNM staging scope. Example: Colorectal, breast or prostate.
Table
Edit logic (TVAL51)
T5 IN ['1', '2'] AND (T12.YEAR >= 2003 AND T12.YEAR <= 2007) AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T51 NOT IN [Eligible AJCC edition number codes] |
AJCC TNM data items filled with 'R' at posting. |
Table
Feedback report messages (TVAL51)
AJCC edition number code is either invalid or not eligible for the CCR system. |
AJCC TNM error |
Table
Revision (TVAL51)
Edit no longer applicable: Variable T51 no longer reported. |
Edit added: New edit. |
TVAL52
Purpose
This edit validates CS version input original.
Table
Referenced fields (TVAL52)
1 |
Tumour record type |
TRECTYPE |
4 |
First 4 digits of T12 (year of date of diagnosis) |
Not applicable |
3 |
CS tumour size |
TCSTSIZE |
3 |
CS extension |
TCSEXTN |
1 |
CS tumour size/ext eval |
TCSEVAL |
3 |
CS lymph nodes |
TCSLNODE |
1 |
CS lymph nodes eval |
TCSLNEVAL |
2 |
Regional nodes examined |
TCSRNEXAM |
2 |
Regional nodes positive |
TCSRNPOS |
2 |
CS mets at dx |
TCSMDIAG |
1 |
CS mets eval |
TCSMEVAL |
3 |
CS site-specific factor 1 |
TCSSSF1 |
3 |
CS site-specific factor 2 |
TCSSSF2 |
3 |
CS site-specific factor 3 |
TCSSSF3 |
3 |
CS site-specific factor 4 |
TCSSSF4 |
3 |
CS site-specific factor 5 |
TCSSSF5 |
3 |
CS site-specific factor 6 |
TCSSSF6 |
3 |
CS site-specific factor 7 |
TCSSSF7 |
3 |
CS site-specific factor 8 |
TCSSSF8 |
3 |
CS site-specific factor 9 |
TCSSSF9 |
3 |
CS site-specific factor 10 |
TCSSSF10 |
3 |
CS site-specific factor 11 |
TCSSSF11 |
3 |
CS site-specific factor 12 |
TCSSSF12 |
3 |
CS site-specific factor 13 |
TCSSSF13 |
3 |
CS site-specific factor 14 |
TCSSSF14 |
3 |
CS site-specific factor 15 |
TCSSSF15 |
3 |
CS site-specific factor 16 |
TCSSSF16 |
3 |
CS site-specific factor 17 |
TCSSSF17 |
3 |
CS site-specific factor 18 |
TCSSSF18 |
3 |
CS site-specific factor 19 |
TCSSSF19 |
3 |
CS site-specific factor 20 |
TCSSSF20 |
3 |
CS site-specific factor 21 |
TCSSSF21 |
3 |
CS site-specific factor 22 |
TCSSSF22 |
3 |
CS site-specific factor 23 |
TCSSSF23 |
3 |
CS site-specific factor 24 |
TCSSSF24 |
3 |
CS site-specific factor 25 |
TCSSSF25 |
6 |
CS version input original |
TCSVERINORIG |
1 |
Lymph-vascular invasion |
TLYMPHVASINV |
6 |
CS version input current |
TCSVERINCUR |
Business rules
For Add and Update Tumour records within the
CCR collaborative staging scope and with at least one known CS variable
- CS version input original must be one of the Eligible CS version input original codes.
Table
Edit logic (TVAL52)
T5 IN ['1', '2'] AND T12.YEAR >= '2004' AND T64 = NULL AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' or T52 <> '999999') AND T52 NOT IN [Eligible CS version input original codes] |
CS data items filled with 'R' at posting. |
T5 IN ['1', '2'] AND T12.YEAR >= '2004' AND (T64 >= '020200' AND T64 <> '999999') AND (T27<>'999' OR T28<>'999' OR T29<>'9' OR T30<>'999' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T63 <> '9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T63 <> '9" OR T65 <> '999' OR T66 <> '999' OR T67 <> '999' OR T68 <> '999' OR T69 <> '999' OR T70 <> '999' OR T71 <> '999' OR T72 <> '999' OR T73 <> '999' OR T74 <> '999' OR T75 <> '999' OR T76 <> '999' OR T77 <> '999' OR T78 <> '999' OR T79 <> '999' OR T80 <> '999' OR T81 <> '999' OR T82 <> '999' OR T83 <> '999' OR T52 <> '999999') AND T52 NOT IN [Eligible CS version input original codes] |
CS data items filled with 'R' at posting. |
Table
Feedback report messages (TVAL52)
CS version input original is not a valid version number. |
CS error |
CS Version input original is not a valid version number (for CSV2). |
CS error |
Table
Revision (TVAL52)
Referenced fields, Business rules, edit logic, and Feedback report messages: Variable Names changed - CS version 1st to CS version input original (acronym changed from TCSFVER to TCSVERINORIG), CS reg nodes eval to CS lymph nodes eval (acronym changed from TCSRNEVAL to TCSLNEVAL). Length of CS Extension and CS Lymph nodes has been changed from 2 to 3. CS Version input current has been added. Lymph-vascular invasion has been added. Edit Logic and Feedback report messages: CS Version input current is checked to make sure fields checked are the correct length according to CS Version 1 or CS Version 2. New fields added for verifications after implementation of CSV2. |
Edit added: New edit. |
TVAL53
Purpose
This edit validates the Ambiguous terminology diagnosis code.
Table
Referenced fields (TVAL53)
1 |
Tumour record type |
TRECTYPE |
1 |
Ambiguous Terminology Diagnosis |
TAMBIGTERM |
Business rules
For Add and Update Tumour records
- Ambiguous terminology diagnosis must be one of the Eligible Ambiguous terminology diagnosis codes.
Table
Edit logic (TVAL53)
T5 IN ['1', '2'] AND T53 IS NOT NULL AND NOT IN [Eligible Ambiguous terminology diagnosis codes] |
Record rejected |
Table
Feedback report messages (TVAL53)
Ambiguous terminology diagnosis code is invalid. |
Core error |
Table
Revision (TVAL53)
Edit added: New edit. |
TVAL54
Purpose
This edit validates the Date of conclusive diagnosis.
Table
Referenced fields (TVAL54)
1 |
Tumour record type |
TRECTYPE |
8 |
Date of conclusive diagnosis |
TDATCONCLUSDIAG |
4 |
First 4 digits of T54 (year of date of conclusive diagnosis) |
Not applicable |
2 |
5th and 6th digits of T54 (month of date of conclusive diagnosis) |
Not applicable |
2 |
7th and 8th digits of T56 (day of date of conclusive diagnosis) |
Not applicable |
Business rules
For Add and Update Tumour records,
Date of conclusive diagnosis
- Must be exclusively composed of numbers: 0 to 9.
- Must be 8 digits long.
- If Year or Month or Day is accessioned then the Date of conclusive diagnosis must be accessioned.
- If Year or Month or Day is not applicable then the Date of conclusive diagnosis must be not applicable.
- If Year is unknown then Month and Day must be unknown.
- If Month is unknown then Day must be unknown.
- If Year and Month are known and Day is unknown then Month must be a valid month.
- If Year, Month and Day are known then it must be a valid calendar date.
- Must be between January 1st, 2008 and December 31st of Reference year inclusively.
Table
Edit logic (TVAL54)
T5 IN ['1', '2'] AND LENGTH (T54) <> 8 OR NOT IS_COMPOSED_OF (T54, '0123456789') |
Record Rejected |
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 |
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 |
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 |
T5 IN ['1', '2'] AND LENGTH (T54) = 8 AND IS_COMPOSED_OF (T54, '0123456789') AND T54.MONTH = '99' AND T54.DAY <> '99' |
Record Rejected |
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 |
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 |
T5 IN ['1', '2'] AND T54 NOT IN ['00000000', '88888888', '99999999'] AND (T54.YEAR < 2008 OR T54.YEAR > CYCLE_YEAR) |
Record Rejected |
Table
Feedback report messages (TVAL54)
Date of conclusive diagnosis is not composed of 8 numbers. |
Core Error |
Year, month and day must be 'accessioned'. |
Core Error |
Year, month and day must be 'not applicable'. |
Core Error |
Year, month and day must be 'unknown'. |
Core Error |
Date of conclusive diagnosis: month and day must be 'unknown'. |
Core Error |
Date of conclusive diagnosis is not a valid partial date: month is invalid. |
Core Error |
Date of conclusive diagnosis is not a valid calendar date. |
Core Error |
Date of conclusive diagnosis is out of scope. |
Core Error |
Table
Revision (TVAL54)
Edit added: New edit. |
TVAL55
Purpose
This edit validates the Type of multiple tumours reported as one primary code.
Table
Referenced fields (TVAL55)
1 |
Tumour record type |
TRECTYPE |
2 |
Type of multiple tumours reported as one primary |
TMULTTUMONEPRIM |
Business rules
For Add and Update Tumour records,
Type of multiple tumours reported as one primary code
- Must contain a valid code.
Table
Edit logic (TVAL55)
T5 IN ['1', '2'] AND T55 IS NOT NULL AND T55 NOT IN [Eligible Type of multiple tumours reported as one primary codes] |
Record rejected |
Table
Feedback report messages (TVAL55)
Type of multiple tumours reported as one primary code is invalid. |
Core error |
Table
Revision (TVAL55)
Edit added: New edit. |
TVAL56
Purpose
This edit validates the Date of multiple tumours.
Table
Referenced fields (TVAL56)
1 |
Tumour record type |
TRECTYPE |
8 |
Date of multiple tumours |
TDATMULT |
4 |
First 4 digits of T56 (year of date of multiple tumours) |
Not applicable |
2 |
5th and 6th digits of T56 (month of date of multiple tumours) |
Not applicable |
2 |
7th and 8th digits of T56 (day of date of multiple tumours) |
Not applicable |
Business rules
For Add and Update Tumour records,
Date of multiple tumours
- Must be exclusively composed of numbers: 0 to 9.
- Must be 8 digits long.
- If Year or Month or Day relates to a single tumour then the Date of multiple tumours must contain all zeros.
- If Year or Month or Day is not applicable then the Date of multiple tumours must be not applicable.
- If Year is unknown then Month and Day must be unknown.
- If Month is unknown then Day must be unknown.
- If Year and Month are known and Day is unknown then Month must be a valid month.
- If Year, Month and Day are known then it must be a valid calendar date.
- Must be between January 1st, 2008 and December 31st of Reference year inclusively.
Table
Edit logic (TVAL56)
T5 IN ['1', '2'] AND LENGTH (T56) <> 8 OR NOT IS_COMPOSED_OF (T56, '0123456789') |
Record Rejected |
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 |
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 |
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 |
T5 IN ['1', '2'] AND LENGTH (T56) = 8 AND IS_COMPOSED_OF (T56, '0123456789') AND T56.MONTH = '99' AND T56.DAY <> '99' |
Record Rejected |
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 |
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 |
T5 IN ['1', '2'] AND T56 NOT IN ['00000000', '88888888', '99999999'] AND (T56.YEAR < 2008 OR T56.YEAR > CYCLE_YEAR) |
Record Rejected |
Table
Feedback report messages (TVAL56)
Date of multiple tumours is not composed of 8 numbers. |
Core Error |
Year, month and day must relate to a single tumour (all zeros). |
Core Error |
Year, month and day must be 'not applicable'. |
Core Error |
Year, month and day must be 'unknown'. |
Core Error |
Date of multiple tumours: month and day must be 'unknown'. |
Core Error |
Date of multiple tumours is not a valid partial date: month is invalid. |
Core Error |
Date of multiple tumours is not a valid calendar date. |
Core Error |
Date of multiple tumours is out of scope. |
Core Error |
Table
Revision (TVAL56)
Edit added: New edit. |
TVAL57
Purpose
This edit validates the Multiplicity counter.
Table
Referenced fields (TVAL57)
1 |
Tumour record type |
TRECTYPE |
2 |
Multiplicity counter |
TMULTCOUNT |
Business rules
For Add and Update Tumour records,
Multiplicity counter
- Must be a numeric value between '01' and '87', or '88' or '99'
Table
Edit logic (TVAL57)
T5 IN ['1', '2'] AND T57 IS NOT NULL AND T57 NOT IN [Eligible Multiplicity counter codes] |
Record Rejected |
Table
Feedback report messages (TVAL57)
Multiplicity counter is invalid |
Core error |
Table
Revision (TVAL57)
Edit added: New edit. |
TVAL58
Purpose
This edit validates the date of diagnosis flag.
Table
Referenced fields (TVAL58)
1 |
Tumour record type |
TRECTYPE |
1 |
Date of diagnosis flag |
TDATDIAGFLAG |
Business rules
For Add and Update Tumour records
- Date of diagnosis flag must be one of the Eligible date of diagnosis flag codes.
Table
Edit logic (TVAL58)
T5 IN ['1', '2'] AND T58 NOT IN [Eligible date of diagnosis flag codes] |
Record Rejected |
Table
Feedback report messages (TVAL58)
Date of diagnosis flag code is invalid. |
Core fatal error |
Table
Revision (TVAL58)
New edit added. |
TVAL59
Purpose
This edit validates the date of conclusive diagnosis flag.
Table
Referenced fields (TVAL59)
1 |
Tumour record type |
TRECTYPE |
1 |
Date of conclusive diagnosis flag
|
TDATCONCLUSDIAGFLAG
|
Business rules
For Add and Update Tumour records
- Date of conclusive diagnosis flag must be one of the Eligible date of conclusive diagnosis flag codes.
Table
Edit logic (TVAL59)
T5 IN ['1', '2'] AND T59 NOT IN [Eligible date of conclusive diagnosis flag codes] |
Record Rejected |
Table
Feedback report messages (TVAL59)
Date of conclusive diagnosis flag code is invalid. |
Core fatal error |
Table
Revision (TVAL59)
New edit added |
TVAL60
Purpose
This edit validates the date of multiple tumours flag.
Table
Referenced fields (TVAL60)
1 |
Tumour record type |
TRECTYPE |
1 |
Date of multiple tumours flag |
TDATMULTFLAG |
Business rules
For Add and Update Tumour records
- Date of multiple tumours flag must be one of the Eligible date of multiple tumours flag codes.
Table
Edit logic (TVAL60)
T5 IN ['1', '2'] AND T59 NOT IN [Eligible date of multiple tumours flag codes] |
Record Rejected |
Table
Feedback report messages (TVAL60)
Date of multiple tumours flag code is invalid. |
Core fatal error |
Table
Revision (TVAL60)
New edit added. |
TVAL61
Purpose
This edit validates Grade path value.
Table
Referenced fields (TVAL61)
1 |
Tumour record type |
TRECTYPE |
1 |
Grade path value |
TGRADEPATHVAL |
Business rules
For Add and Update Tumour records
- Grade path value must be one of the Eligible Grade path value codes.
Table
Edit logic (TVAL61)
T5 IN ['1', '2'] AND T61 IS NOT NULL AND NOT IN [Eligible Grade path value codes] |
Record rejected |
Table
Feedback report messages (TVAL61)
Grade path value code is invalid. |
Core error |
Table
Revision (TVAL61)
Edit added: New edit |
TVAL62
Purpose
This edit validates Grade path system.
Table
Referenced fields (TVAL62)
1 |
Tumour record type |
TRECTYPE |
1 |
Grade path system |
TGRADEPATHSYS |
Business rules
For Add and Update Tumour records
- Grade path system must be one of the Eligible Grade path system codes.
Table
Edit logic (TVAL62)
T5 IN ['1', '2'] AND T62 IS NOT NULL AND NOT IN [Eligible Grade path system codes] |
|
Table
Feedback report messages (TVAL62)
Grade path system code is invalid. |
Core error |
Table
Revision (TVAL62)
Edit added: New edit |
TVAL63
Purpose
This edit validates Lymph-vascular invasion.
Table
Referenced fields (TVAL62)
1 |
Tumour record type |
TRECTYPE |
6 |
CS version input current
|
TCSVERINCUR
|
1 |
Lymph-vascular invasion
|
TLYMPHVASINV
|
Business rules
For Add and Update Tumour records
- If CS version input current is blank (CSV2 not yet implemented) then Lymph-vascular invasion must be left blank.
- If CS version input current indicates CSV2 has been implemented then Lymph-vascular invasion must be one of the Eligible Lymph-vascular invasion codes.
Table
Edit logic (TVAL63)
T5 IN ['1', '2'] AND T64 = NULL AND T63 <> NULL |
Record rejected |
T5 IN ['1', '2'] AND (T64>= '020200' and T64 <> '999999') and T63 NOT IN [Eligible Lymph-vascular invasion codes]
|
Record rejected
|
Table
Feedback report messages (TVAL63)
Lymph-vascular invasion code must be blank if CSV2 is not implemented. |
Core error |
Lymph-vascular invasion code is invalid. |
Core error |
Table
Revision (TVAL63)
Edit added: New edit |
TVAL64
Purpose
This edit validates CS Version input current.
Table
Referenced fields (TVAL64)
1 |
Tumour record type |
TRECTYPE |
4 |
First 4 digits of T12 (year of date of diagnosis) |
Not applicable |
3 |
CS tumour size |
TCSTSIZE |
3 |
CS extension |
TCSEXTN |
1 |
CS tumour size/ext eval |
TCSEVAL |
3 |
CS lymph nodes |
TCSLNODE |
1 |
CS lymph nodes eval |
TCSLNEVAL |
2 |
Regional nodes examined |
TCSRNEXAM |
2 |
Regional nodes positive |
TCSRNPOS |
2 |
CS mets at dx |
TCSMDIAG |
1 |
CS mets eval |
TCSMEVAL |
1 |
Lymph-vascular invasion |
TLYMPHVASINV |
6 |
CS version input current |
TCSVERINCUR |
3 |
CS site-specific factor 1 |
TCSSSF1 |
3 |
CS site-specific factor 2 |
TCSSSF2 |
3 |
CS site-specific factor 3 |
TCSSSF3 |
3 |
CS site-specific factor 4 |
TCSSSF4 |
3 |
CS site-specific factor 5 |
TCSSSF5 |
3 |
CS site-specific factor 6 |
TCSSSF6 |
3 |
CS site-specific factor 7 |
TCSSSF7 |
3 |
CS site-specific factor 8 |
TCSSSF8 |
3 |
CS site-specific factor 9 |
TCSSSF9 |
3 |
CS site-specific factor 10 |
TCSSSF10 |
3 |
CS site-specific factor 11 |
TCSSSF11 |
3 |
CS site-specific factor 12 |
TCSSSF12 |
3 |
CS site-specific factor 13 |
TCSSSF13 |
3 |
CS site-specific factor 14 |
TCSSSF14 |
3 |
CS site-specific factor 15 |
TCSSSF15 |
3 |
CS site-specific factor 16 |
TCSSSF16 |
3 |
CS site-specific factor 17 |
TCSSSF17 |
3 |
CS site-specific factor 18 |
TCSSSF18 |
3 |
CS site-specific factor 19 |
TCSSSF19 |
3 |
CS site-specific factor 20 |
TCSSSF20 |
3 |
CS site-specific factor 21 |
TCSSSF21 |
3 |
CS site-specific factor 22 |
TCSSSF22 |
3 |
CS site-specific factor 23 |
TCSSSF23 |
3 |
CS site-specific factor 24 |
TCSSSF24 |
3 |
CS site-specific factor 25 |
TCSSSF25 |
Business rules
For Add and Update Tumour records within the
CCR collaborative staging scope and with at least one known CS variable
- CS version input current must be one of the Eligible CS version input current codes.
Table
Edit logic (TVAL64)
(T5 IN ['1', '2'] AND T12.YEAR >= '2004' AND (T27<>'999' OR 'T28<>'999' OR T29<>'9' OR T30<>'999' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T63 <> '9' OR T65 <> '999' OR T66 <> '999' OR T67 <> '999' OR T68 <> '999' OR T69 <> '999' OR T70 <> '999' OR T71 <> '999' OR T72 <> '999' OR T73 <> '999' OR T74 <> '999' OR T75 <> '999' OR T76 <> '999' OR T77 <> '999' OR T78 <> '999' OR T79 <> '999' OR T80 <> '999' OR T81 <> '999' OR T82 <> '999' OR T83 <> '999' OR T52 <> '999999') AND T64 NOT IN [Eligible CS version input current codes] |
CS data items filled with 'R' at posting. |
Table
Feedback report messages (TVAL64)
CS version input current is not a valid version number. |
CS error |
Table
Revision (TVAL64)
Edit added: New edit. |
TVAL65 - TVAL83
Purpose
These edits validate the CS site-specific factors 7 - 25.
Table
Referenced fields (TVAL65-TVAL83)
1 |
Tumour record type |
TRECTYPE |
6 |
CS version input current |
TCSVERINCUR |
3 |
CS site-specific factors 7 -25 |
N/A |
Business rules
For Add and Update Tumour records
CS site specific factors 7 – 25
- must be either blank or composed of numbers 0 to 9
- must be 3 digits long
Table
Edit logic (TVAL65 - TVAL83)
T5 IN ['1', '2'] AND (T64 >= '020200' AND T64 <> '999999') AND T(65, T66, T67 …T83 NOT NULL) and (LENGTH (T66, T67 …T83) <> 3 OR NOT IS_COMPOSED_OF ((T66, T67 …T83), '0123456789')) |
CS data items filled with 'R' at posting. |
Table
Feedback report messages (TVAL65-TVAL83)
CS Site specific factor XX code is invalid. |
CS error |
Table
Revision (TVAL65- TVAL83)
New edit added. |
TVAL84
Purpose
This edit validates CS mets at dx bone.
Table
Referenced fields (TVAL84)
1 |
Tumour record type |
TRECTYPE |
1 |
CS mets at dx bone |
TCSMDXBONE |
Business rules
For Add and Update Tumour records
- CS mets at dx bone must be one of the Eligible CS mets at dx bone codes.
Table
Edit logic (TVAL84)
T5 IN ['1', '2'] AND T84 IS NOT NULL AND NOT IN [Eligible CS mets at dx bone codes] |
Record rejected |
Table
Feedback report messages (TVAL84)
CS mets at dx bone code is invalid. |
Core error |
Table
Revision (TVAL84)
Edit added: New edit |
TVAL85
Purpose
This edit validates CS mets at dx brain.
Table
Referenced fields (TVAL85)
1 |
Tumour record type |
TRECTYPE |
1 |
CS mets at dx brain |
TCSMDXBRAIN |
Business rules
For Add and Update Tumour records
- CS mets at dx brain must be one of the Eligible CS mets at dx brain codes.
Table
Edit logic (TVAL85)
T5 IN ['1', '2'] AND T85 IS NOT NULL AND NOT IN [Eligible CS mets at dx brain codes] |
Record rejected |
Table
Feedback report messages (TVAL85)
CS mets at dx brain code is invalid. |
Core error |
Table
Revision (TVAL85)
Edit added: New edit |
TVAL86
Purpose
This edit validates CS mets at dx liver.
Table
Referenced fields (TVAL86)
1 |
Tumour record type |
TRECTYPE |
1 |
CS mets at dx liver |
TCSMDXLIVER |
Business rules
For Add and Update Tumour records
- CS mets at dx liver must be one of the Eligible CS mets at dx liver codes.
Table
Edit logic (TVAL86)
T5 IN ['1', '2'] AND T86 IS NOT NULL AND NOT IN [Eligible CS mets at dx liver codes] |
Record rejected |
Table
Feedback report messages (TVAL86)
CS mets at dx liver code is invalid. |
Core error |
Table
Revision (TVAL86)
Edit added: New edit |
TVAL87
Purpose
This edit validates CS mets at dx lung.
Table
Referenced fields (TVAL87)
1 |
Tumour record type |
TRECTYPE |
1 |
CS mets at dx lung |
TCSMDXLUNG |
Business rules
For Add and Update Tumour records
- CS mets at dx lung must be one of the Eligible CS mets at dx lung codes.
Table
Edit logic (TVAL87)
T5 IN [*'1', '2'] AND T87 IS NOT NULL AND NOT IN [Eligible CS mets at dx lung codes] |
Record rejected |
Table
Feedback report messages (TVAL87)
CS mets at dx lung code is invalid. |
Core error |
Table
Revision (TVAL87)
Edit added: New edit |
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
Ensures that the content of the patient record is consistent with the action described in the Patient record type. |
Verifies the likelihood of given names and gender. |
Ensures that first given name, second given name and third given name are used coherently. |
Ensures that type of current surname code accurately reflects the content of the current surname field. |
Ensures that birth surname and current surname are consistent with type of current surname. |
Ensures that at least one surname is reported, either the current surname or the birth surname. |
Ensures that date of birth and date of death respect a chronological sequence and time frame. |
Ensures that death-related variables present a consistent reporting of the patient's vital status. |
Ensures that Death registration number and province/territory or country of death are consistent. |
Ensures Death registration number and date of death are consistent. |
Ensures Death registration number and Underlying cause of death are consistent. |
PCOR1
Purpose
This edit ensures that the content of the patient record is consistent with the action described in the patient record type.
Table
Referenced fields (PCOR1)
2 |
Patient reporting province/territory |
PREPPROV |
12 |
Patient identification number |
PPIN |
9 |
CCR identification number |
CCR_ID |
1 |
Patient record type |
PRECTYPE |
1 |
Type of current surname |
PTYP_CUR |
25 |
Current surname |
PCURSNAM |
15 |
First given name |
PGNAME_1 |
15 |
Second given name |
PGNAME_2 |
7 |
Third given name |
PGNAME_3 |
1 |
Sex |
PSEX |
8 |
Date of birth |
PDATBIR |
3 |
Province/territory or country of birth |
PPROVBIR |
25 |
Birth surname |
PBIRNAM |
8 |
Date of death |
PDATDEA |
3 |
Province/territory or country of death |
PPROVDEA |
6 |
Death registration number |
PDEAREG |
4 |
Underlying cause of death |
PCAUSDEA |
1 |
Autopsy confirming cause of death |
PAUTOPSY |
1 |
Date of birth flag |
PAUTOPSY |
1 |
Date of death flag |
PAUTOPSY |
Business rules
For Add Patient records
- Patient reporting province/territory, Patient identification number, Type of Current surname, Sex, Date of birth,Province/territory or country of birth, Date of death, Province/territory or country of death, Death registration number, Underlying cause of death and Autopsy confirming cause of death must be provided.
- CCR identification number must be blank.
For Update Patient records
- Patient reporting province/territory, Patient identification number, CCR identification number, Type of Current surname, Sex, Date of birth, Province/territory or country of birth, Date of death, Province/territory or country of death, Death registration number, Underlying cause of death and Autopsy confirming cause of death must be provided.
For Delete Patient records
- Patient reporting Province/territory, Patient identification number, CCR identification number must be provided.
- Type of Current surname, Current surname, First given name, Second given name, Third given name, Sex, Date of birth, Province/territory or country of birth, Birth surname, Date of death, Province/territory or country of death, Death registration number, Underlying cause of death, Autopsy confirming cause of death, Date of birth and Date of death flag must be blank.
Table
Edit logic (PCOR1)
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 |
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 |
P4 = '3' AND (P1 IS NULL OR P2 IS NULL OR P3 IS NULL OR P5 IS NOT NULL OR P6 IS NOT NULL OR P7 IS NOT NULL OR P8 IS NOT NULL OR P9 IS NOT NULL OR P10 IS NOT NULL OR P11 IS NOT NULL OR P12 IS NOT NULL OR P13 IS NOT NULL OR P14 IS NOT NULL OR P15 IS NOT NULL OR P16 IS NOT NULL OR P17 IS NOT NULL OR P18 IS NOT NULL OR P20 IS NOT NULL OR P21 IS NOT NULL ) |
Record rejected |
Table
Feedback report messages (PCOR1)
Input record does not respect the Add Patient record format. There are missing or extra values. |
Core fatal error |
Input record does not respect the Update Patient record format. There are missing values. |
Core fatal error |
Input record does not respect the Delete Patient record format. There are missing or extra values. |
Core fatal error |
Table
Revision (PCOR1)
Referenced Fields, Business rules and Edit logic: P20 – Date of birth flag and P21 – Date of death flag added. |
Edit renamed: Current edit was formerly known as Correlation Edit No.1. |
PCOR2
Purpose
This edit verifies the likelihood of given names and sex.
Table
Referenced fields (PCOR2)
1 |
Patient record type |
PRECTYPE |
15 |
First given name |
PGNAME_1 |
15 |
Second given name |
PGNAME_2 |
7 |
Third given name |
PGNAME_3 |
1 |
Sex |
PSEX |
Table
Other parameters (PCOR2)
3 |
Tolerated average likelihood of First given name, Second given name and Third given name to be associated to the opposite gender according to given name and Sex registry2. Value must be between 0 and 100. Default value is 95. |
Business rules
For Add and Update Patient records
- If the average likelihood of First given name, Second given name and Third given name to be associated to the opposite gender according to given name and Sex registry is greater than NAME_SEX_THRESHOLD, then a warning must be sent.
Table
Edit logic (PCOR2)
P4 IN ['1', '2'] AND P10 IN ['1', '2'] AND AVERAGE ([Probability of P7 to be associated to opposite gender], [Probability of P8 to be associated to opposite gender], [Probability of P9 to be associated to opposite gender]) > NAME_SEX_THRESHOLD |
Warning |
Table
Feedback report messages (PCOR2)
Reported given names are not likely for reported Sex. |
Warning |
Table
Revision (PCOR2)
Edit removed: Edit formerly known as Correlation Edit No.2 has been removed. Edit added: Current edit was not documented before. |
PCOR3
Purpose
This edit ensures that first given name, second given name and third given name are used coherently.
Table
Referenced fields (PCOR3)
1 |
Patient record type |
PRECTYPE |
15 |
First given name |
PGNAME_1 |
15 |
Second given name |
PGNAME_2 |
7 |
Third given name |
PGNAME_3 |
Business rules
For Add and Update Patient records
- If First given name is blank then Second given name and Third given name must be blank.
- If Second given name is blank then Third given name must be blank.
Table
Edit logic (PCOR3)
P4 IN ['1', '2'] AND P7 IS NULL AND (P8 IS NOT NULL OR P9 IS NOT NULL) |
Record rejected |
P4 IN ['1', '2'] AND P8 IS NULL AND P9 IS NOT NULL |
Record rejected |
Table
Feedback report messages (PCOR3)
First given name is missing. |
Core error |
Second given name is missing. |
Core error |
Table
Revision (PCOR3)
Edit renamed: Current edit was formerly known as Correlation Edit No.3. |
PCOR4
Purpose
This edit ensures that type of current surname code accurately reflects the content of the current surname field.
Table
Referenced fields (PCOR4)
1 |
Patient record type |
PRECTYPE |
1 |
Type of current surname |
PTYP_CUR |
25 |
Current surname |
PCURSNAM |
Business rules
For Add and Update Patient records
- If Type of Current surname is 'Current Surname unknown' (0) then Current surname must be blank.
- If Current surname is blank then Type of Current surname must be 'Current surname unknown' (0).
Table
Edit logic (PCOR4)
P4 IN ['1', '2'] AND ((P5 = '0' AND P6 IS NOT NULL) OR (P6 IS NULL AND P5 <> '0')) |
Record rejected |
Table
Feedback report messages (PCOR4)
Type of current surname and Current surname do not agree. |
Core error |
Table
Revision (PCOR4)
Edit renamed: Current edit was formerly known as Correlation Edit No.4. |
PCOR5
Purpose
This edit ensures that birth surname and current surname are consistent with type of current surname.
Table
Referenced fields (PCOR5)
1 |
Patient record type |
PRECTYPE |
1 |
Type of Current surname |
PTYP_CUR |
25 |
Current surname |
PCURSNAM |
25 |
Birth surname |
PBIRNAM |
Business rules
For Add and Update Patient records
- If Type of Current surname is 'Birth surname' then Current surname and Birth surname must be the same.
Table
Edit logic (PCOR5)
P4 IN ['1', '2'] AND P5 = '1' AND P6 <> P13 |
Record rejected |
Table
Feedback report messages (PCOR5)
Current surname and Birth surname are different while Type of current surname indicates that they should be the same. |
Core error |
Table
Revision (PCOR5)
Edit renamed: Current edit was formerly known as Correlation Edit No.5. |
PCOR6
Purpose
This edit ensures that at least one surname is reported, either the current surname or the birth surname.
Table
Referenced fields (PCOR6)
1 |
Patient record type |
PRECTYPE |
25 |
Current surname |
PCURSNAM |
25 |
Birth surname |
PBIRNAM |
Business rules
For Add and Update Patient records
- Current surname and Birth surname cannot both be blank.
Table
Edit logic (PCOR6)
P4 IN ['1', '2'] AND P6 IS NULL AND P13 IS NULL |
Record rejected |
Table
Feedback report messages (PCOR6)
Current surname and Birth surname cannot both be blank. |
Core error |
Table
Revision (PCOR6)
Edit renamed: Current edit was formerly known as Correlation Edit No.6. |
PCOR7
Purpose
This edit ensures that date of birth and date of death respect a chronological sequence and time frame.
Table
Referenced fields (PCOR7)
1 |
Patient record type |
PRECTYPE |
8 |
Date of birth |
PDATBIR |
4 |
First 4 characters of P11 (year of date of birth) |
Not applicable |
2 |
5th and 6th characters of P11 (month of date of birth) |
Not applicable |
2 |
7th and 8th characters of P11 (day of date of birth) |
Not applicable |
8 |
Date of death |
PDATDEA |
4 |
First 4 characters of P14 (year of date of death) |
Not applicable |
2 |
5th and 6th characters of P14 (month of date of death) |
Not applicable |
2 |
7th and 8th characters of P14 (day of date of death) |
Not applicable |
8 |
Date of transmission |
PDATTRAN |
Business rules
For Add and Update Patient records
- If Date of birth and Date of death are at least partially known then
- Date of death must be on or after Date of birth;
- Year of Date of death and year of Date of birth should not be more than 110 years apart.
- If Date of birth is at least partially known and the patient is not known to have died then
- Year of Date of birth and year of Date of transmission should not be more than 110 years apart.
Table
Edit logic (PCOR7)
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 |
P4 IN ['1', '2'] AND P11 <> '99999999' AND ((P14 NOT IN ['00000000', '99999999'] AND P14.YEAR – P11.YEAR > 110) OR (P14 = '00000000' AND P19.YEAR – P11.YEAR > 110)) |
Warning |
Table
Feedback report messages (PCOR7)
Date of death is before Date of birth. |
Core error |
The patient is more than 110 years old. |
Warning |
Table
Revision (PCOR7)
Edit renamed: Current edit was formerly known as Correlation Edit No.7. Business rules added: Special handling for patients over 110 years old. |
PCOR8
Purpose
This edit ensures that death-related variables present a consistent reporting of the patient's vital status.
Table
Referenced fields (PCOR8)
1 |
Patient record type |
PRECTYPE |
8 |
Date of death |
PDATDEA |
3 |
Province/territory or country of death |
PPROVDEA |
6 |
Death registration number |
PDEAREG |
4 |
Underlying cause of death |
PCAUSDEA |
1 |
Autopsy confirming cause of death |
PAUTOPSY |
Business rules
For Add and Update Patient records
- If any of the death-related variables (Date of death, Province/territory or country of death, Death registration number, Underlying cause of death and Autopsy confirming cause of death) indicate that the patient is deceased then no variables should indicate that the patient is not known to have died.
Table
Edit logic (PCOR8)
P4 IN ['1', '2'] AND (P14 <> '00000000' OR P15 <> '000' OR P16 <> '000000' OR P17 <> '0000' OR P18 <> '0') AND (P14 = '00000000' OR P15 = '000' OR P16 = '000000' OR P17 = '0000' OR P18 = '0') |
Record rejected |
Table
Feedback report messages (PCOR8)
Some death-related variables indicate that the patient is deceased whereas at least another indicates that the patient is not known to have died. |
Core error |
Table
Revision (PCOR8)
Edit removed: Edit formerly known as Correlation Edit No.8 was redundant with PVAL11. Edit renamed: Current edit was formerly known as Correlation Edit No.10. |
PCOR9
Purpose
This edit ensures that death registration number and province/territory or country of death are consistent.
Table
Referenced fields (PCOR9)
1 |
Patient record type |
PRECTYPE |
3 |
Province/territory or country of death |
PPROVDEA |
6 |
Death registration number |
PDEAREG |
Business rules
For Add and Update Patient records
- If Death registration number is known then Province/territory or country of death must indicate a specific location in Canada or United States of America.
- If Death registration number indicated that the Patient died outside Canada then Province/territory or country of death must indicate a foreign country or unknown place.
- If Death registration number is unknown then Province/territory or country of death must be either a location in Canada or an unknown place.
Table
Edit logic (PCOR9)
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 |
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 |
P4 IN ['1', '2'] AND P16 = '999999' AND P15 NOT IN [909, 910, 911, 912, 913, 924, 935, 946, 947, 948, 959, 960, 961, 962, 999] |
Record rejected |
Table
Feedback report messages (PCOR9)
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 |
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 |
If Death registration number is unknown then province/territory or country of death must be either a location in Canada or an unknown place. |
Core error |
Table
Revision (PCOR9)
Edit reorganized: Edit formerly known as Correlation Edit No.9 merged with PVAL14. Edit renamed: Current edit was formerly known as Correlation Edit No.11. Business rules changed: If Death registration number is known then province/territory or country of death must indicate a specific location in Canada or United States of America; If Death registration number is unknown then province/territory or country of death must be either a location in Canada or an unknown place. Business rules added: If Death registration number indicated that the patient died outside Canada then province/territory or country of death must indicate a foreign country or unknown place. |
PCOR10
Purpose
This edit ensures death registration number and date of death are consistent.
Table
Referenced fields (PCOR10)
1 |
Patient record type |
PRECTYPE |
8 |
Date of death |
PDATDEA |
6 |
Death registration number |
PDEAREG |
Business rules
For Add and Update Patient records
- If Death registration number is known then Date of death must be at least partially known.
Table
Edit logic (PCOR10)
P4 IN ['1', '2'] AND P16 IN [000001-999997] AND P14.YEAR = '9999' |
Record rejected |
Table
Feedback report messages (PCOR10)
Date of death cannot be unknown if Death registration number is known. |
Core error |
Table
Revision (PCOR10)
Edit reorganized: Edit formerly known as Correlation Edit No.10 moved to PCOR8. Edit added: New edit. |
PCOR11
Purpose
This edit ensures death registration number and underlying cause of death are consistent.
Table
Referenced fields (PCOR11)
1 |
Patient record type |
PRECTYPE |
6 |
Death registration number |
PDEAREG |
3 |
Underlying cause of death |
PCAUSDEA |
Business rules
For Add and Update Patient records
- If Death registration number is unknown then Underlying cause of death cannot be 'Officially unknown'.
Table
Edit logic (PCOR11)
P4 IN ['1', '2'] AND P16 = '999999' AND P17 IN = ['R99', '7999'] |
Record rejected |
Table
Feedback report messages (PCOR11)
Underlying cause of death cannot be 'Officially unknown' when Death registration is unknown. |
Core error |
Table
Revision (PCOR11)
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
Ensures that the content of the core tumour fields is consistent with the operation described in the Tumour record type. |
Ensures that Postal code and Standard geographic code are coherent. |
Ensures that Census tract and Standard geographic code are coherent. |
Rejects tumour data for patients living outside the reporting province/territory at time of diagnosis. |
Ensures that expected topography, histology and behaviour values are reported based on the Source classification flag. |
Ensures the consistency between ICD-9 Cancer code and related ICD-O-2 values. |
Ensures the consistency between related ICD-O-2 and ICD-O-3 values. |
Not applicable. (Placeholder for future requirement implementation.) |
Rejects tumour records that are outside the CCR core scope. |
Ensures that invalid combinations of topography and histology are rejected. |
Ensures that invalid combinations of histology and behaviour codes are rejected. |
Ensures the consistency between the topography and the laterality. |
Ensures that invalid combinations of Method used to establish the date of diagnosis and Diagnostic confirmation codes are rejected. |
Ensures that Method of diagnosis is only reported for tumours diagnosed prior to 2004. |
Ensures that Method used to establish the date of diagnosis is only reported for tumours diagnosed in 2004 and onwards. |
Ensures that Diagnostic confirmation is only reported for tumours diagnosed in 2004 and onwards. |
Ensures that Grade, differentiation or cell indicator is only reported for tumours diagnosed in 2004 and onwards. |
This edit ensures that Collaborative Staging variables are reported for tumours within the CCR collaborative staging scope. |
This edit ensures that AJCC TNM staging variables are reported for tumours within the CCR AJCC TNM staging scope. |
Ensures that TNM stage group is reported only when clinical and pathologic TNM stage group are not reported. |
Ensures that the combination of AJCC clinical TNM stage group and individual clinical T, N, M values is acceptable. |
Ensures that the combination of AJCC pathologic TNM stage group and the individual pathologic T, N, M values is acceptable. |
Ensures that the combination of AJCC TNM stage group and the individual clinical/pathologic T, N, M values is acceptable. |
Ensures that AJCC edition number is coherent with all remaining AJCC TNM staging variables. |
Ensures the consistency between Ambiguous terminology diagnosis and Date of conclusive diagnosis. |
Ensures the consistency between Type of multiple tumours reported as one primary, Date of multiple tumours and Multiplicity counter. |
Ensures the consistency between Ambiguous terminology diagnosis and Date of Conclusive Diagnosis. |
Ensures that date of diagnosis and date of conclusive diagnosis respect a chronological sequence and time frame. |
Ensures the consistency between ICD-O-2/3 Topography and Type of multiple tumours reported as one primary. |
Ensures the consistency between ICD-O-3 Behaviour and Multiple tumours reported as one primary. |
Ensures the consistency between Type of Multiple Tumours Reported as One Primary, ICD-O-2/3 Topography and ICD-O-3 Histology. |
Ensures the consistency between Date of multiple tumours and Type of multiple tumours reported as one primary. |
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. |
Ensures the consistency between Date of diagnosis and Grade path value and Grade path system. |
Ensures the consistency between Grade path value and Grade path system. |
Ensures the consistency between CS mets at dx and CS mets at dx - bone, CS mets at dx and CS mets at dx - brain, CS mets at dx and CS mets at dx - liver, CS mets at dx and CS mets at dx - lung. |
TCOR1
Purpose
This edit ensures that the content of the core tumour fields is consistent with the operation described in the tumour record type.
Table
Referenced fields (TCOR1)
2 |
Tumour reporting province/territory |
TREPPROV |
12 |
Tumour patient identification number |
TPIN |
9 |
Tumour reference number |
TTRN |
9 |
CCR identification number |
CCR_ID |
1 |
Tumour record type |
TRECTYPE |
25 |
Name of place of residence |
TPLACRES |
6 |
Postal code |
TPOSTCOD |
7 |
Standard geographic code |
TCODPLAC |
9 |
Census tract |
TCENTRAC |
15 |
Health insurance number |
THIN |
1 |
Method of diagnosis |
TMETHDIAG |
8 |
Date of diagnosis |
TDATDIAG |
4 |
First 4 digist of T12 (year of date of diagnosis |
Not applicable |
4 |
ICD–9 Cancer code |
TICD_9 |
1 |
Source classification flag |
TSCF |
4 |
ICD–O–2/3 Topography |
TICD_O2T |
4 |
ICD–O–2 Histology |
TICD_O2H |
1 |
ICD–O–2 Behaviour |
TICD_O2B |
1 |
Laterality |
TLATERAL |
4 |
ICD–O–3 Histology |
TICD_O3H |
1 |
ICD–O–3 Behaviour |
TICD_03B |
1 |
Grade, differentiation or cell indicator |
TGRADE |
2 |
Method used to establish the date of diagnosis |
TMETHUSED |
2 |
Diagnostic confirmation |
TMETHCONF |
3 |
CS tumour size |
TCSTSIZE |
3 |
CS extension |
TCSEXTN |
1 |
CS tumour size/ext eval |
TCSEVAL |
3 |
CS lymph nodes |
TCSLNODE |
1 |
CS lymph nodes eval |
TCSLNEVAL |
2 |
Regional nodes examined |
TCSRNEXAM |
2 |
Regional nodes positive |
TCSRNPOS |
2 |
CS mets at diagnosis |
TCSMDIAG |
1 |
CS mets evaluation |
TCSMEVAL |
3 |
CS site–specific factor 1 |
TCSSSF1 |
3 |
CS site–specific factor 2 |
TCSSSF2 |
3 |
CS site–specific factor 3 |
TCSSSF3 |
3 |
CS site–specific factor 4 |
TCSSSF4 |
3 |
CS site–specific factor 5 |
TCSSSF5 |
3 |
CS site–specific factor 6 |
TCSSSF6 |
9 |
AJCCclinical T |
TAJCCCLINT |
3 |
AJCC clinical N |
TAJCCCLINN |
3 |
AJCC clinical M |
TAJCCCLINM |
9 |
AJCC pathologic T |
TAJCCPATHT |
6 |
AJCC pathologic N |
TAJCCPATHN |
3 |
AJCC pathologic M |
TAJCCPATHM |
4 |
AJCC clinical TNM stage group |
TAJCCCLINSG |
4 |
AJCC pathologic TNM stage group |
TAJCCPATHSG |
4 |
AJCC TNM stage group |
TAJCCSG |
2 |
AJCC TNM edition number |
TAJCCEDNUM |
6 |
CS version input original |
TCSVERINORIG |
1 |
Ambiguous terminology diagnosis |
TAMBIGTERM |
8 |
Date of conclusive diagnosis |
TDATCONCLUSDIAG |
2 |
Type of multiple tumours reported as one primary |
TMULTTUMONEPRIM |
8 |
Date of multiple tumours |
TDATMULT |
2 |
Multiplicity counter |
TMULTCOUNT |
2 |
Date of diagnosis flag |
TDATDIAGFLAG |
2 |
Date of conclusive diagnosis flag |
TDATCONCLUSDIAGFLAG |
2 |
Date of multiple tumours flag |
TDATMULTFLAG |
1 |
Grade path value |
TGRADEPATHVAL |
1 |
Grade path system |
TGRADEPATHSYS |
1 |
Lymph-vascular invasion |
TLYMPHVASINV |
6 |
CS version input current |
TCSVERINCUR |
3 |
CS site-specific factor 7 |
TCSSSF7 |
3 |
CS site-specific factor 8 |
TCSSSF8 |
3 |
CS site-specific factor 9 |
TCSSSF9 |
3 |
CS site-specific factor 10 |
TCSSSF10 |
3 |
CS site-specific factor 11 |
TCSSSF11 |
3 |
CS site-specific factor 12 |
TCSSSF12 |
3 |
CS site-specific factor 13 |
TCSSSF13 |
3 |
CS site-specific factor 14 |
TCSSSF14 |
3 |
CS site-specific factor 15 |
TCSSSF15 |
3 |
CS site-specific factor 16 |
TCSSSF16 |
3 |
CS site-specific factor 17 |
TCSSSF17 |
3 |
CS site-specific factor 18 |
TCSSSF18 |
3 |
CS site-specific factor 19 |
TCSSSF19 |
3 |
CS site-specific factor 20 |
TCSSSF20 |
3 |
CS site-specific factor 21 |
TCSSSF21 |
3 |
CS site-specific factor 22 |
TCSSSF22 |
3 |
CS site-specific factor 23 |
TCSSSF23 |
3 |
CS site-specific factor 24 |
TCSSSF24 |
3 |
CS site-specific factor 25 |
TCSSSF25 |
1 |
CS Mets at Dx - Bone |
TCSMDXBONE |
1 |
CS Mets at Dx - Brain |
TCSMDXBRAIN |
1 |
CS Mets at Dx - Liver |
TCSMDXLIVER |
1 |
CS Mets at Dx - Lung |
TCSMDXLUNG |
Business rules
For Add Tumour records
- Tumour reporting province/territory, Tumour patient identification number, Tumour reference number, Postal code, Standard geographic code, Method of diagnosis, Date of diagnosis, ICD-9 cancer code, Source classification flag, ICD-O-2/3 Topography, ICD-O-2 Histology, ICD-O-2 Behaviour, Laterality, ICD-O-3 Histology, ICD-O-3 Behaviour, Grade, differentiation or cell indicator, Method used to establish the date of diagnosis, Diagnostic confirmation must be provided39.
- Fillers (T18 and T20) are ignored.
For Update Tumour records
- Tumour reporting province/territory, Tumour patient identification number, Tumour reference number, CCR identification number, Postal code, Standard geographic code, Method of diagnosis, Date of diagnosis, ICD-9 cancer code, Source classification flag, ICD-O-2/3 Topography, ICD-O-2 Histology, ICD-O-2 Behaviour, Laterality, ICD-O-3 Histology, ICD-O-3 Behaviour, Grade, differentiation or cell indicator, Method used to establish the date of diagnosis, Diagnostic confirmation must be provided39.
- Fillers (T18 and T20) are ignored.
For Delete Tumour records
- Tumour reporting province/territory, Tumour patient identification number, Tumour reference number and CCR identification number must be provided.
- Name of place of residence, Postal code, Standard geographic code, Census tract, Health insurance number, Method of diagnosis, Date of diagnosis, ICD-9 cancer code, Source classification flag, ICD-O-2/3 Topography, ICD-O-2 Histology, ICD-O-2 Behaviour, Laterality, ICD-O-3 Histology, ICD-O-3 Behaviour, Grade, differentiation or cell indicator, Method used to establish the date of diagnosis, Diagnostic confirmation, CS tumour size, CS extension, CS tumour size/ext eval, CS lymph nodes, CS lymph nodes eval, Regional nodes examined, Regional nodes positive, CS mets at dx, CS mets eval, CS site-specific factor 1, CS site-specific factor 2, CS site-specific factor 3, CS site-specific factor 4, CS site-specific factor 5, CS site-specific factor 6, AJCC clinical T, AJCC clinical N, AJCC clinical M, AJCC pathologic T, AJCC pathologic N, AJCC pathologic M, AJCC clinical TNM stage group, AJCC pathologic TNM stage group, AJCC TNM stage group, AJCC edition number, CS version input original, Ambiguous Terminology Diagnosis, Date of conclusive diagnosis, Type of multiple tumours reported as one primary, Date of multiple tumours, and Multiplicity Counter, Date of diagnosis flag, Date of conclusive diagnosis flag, Date of multiple tumours flag, Grade path value, Grade path system, Lymph-vascular invasion, CS site-specific factors 7 – 25, CS Mets at Dx – Bone, CS Mets at Dx – Brain, CS Mets at Dx – Liver, CS Mets at Dx – Lung must be blank.
- Fillers (T18 and T20) are ignored.
Table
Edit logic (TCOR1)
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 |
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 |
T5 = '3' AND (T1 IS NULL OR T2 IS NULL OR T3 IS NULL OR T4 IS NULL OR T6 IS NOT NULL OR T7 IS NOT NULL OR T8 IS NOT NULL OR T9 IS NOT NULL OR T10 IS NOT NULL OR T11 IS NOT NULL OR T12 IS NOT NULL OR T13 IS NOT NULL OR T14 IS NOT NULL OR T15 IS NOT NULL OR T16 IS NOT NULL OR T17 IS NOT NULL OR T19 IS NOT NULL OR T21 IS NOT NULL OR T22 IS NOT NULL OR T23 IS NOT NULL OR T24 IS NOT NULL OR T25 IS NOT NULL OR T27 IS NOT NULL OR T28 IS NOT NULL OR T29 IS NOT NULL OR T30 IS NOT NULL OR T31 IS NOT NULL OR T32 IS NOT NULL OR T33 IS NOT NULL OR T34 IS NOT NULL OR T35 IS NOT NULL OR T36 IS NOT NULL OR T37 IS NOT NULL OR T38 IS NOT NULL OR T39 IS NOT NULL OR T40 IS NOT NULL OR T41 IS NOT NULL OR T42 IS NOT NULL OR T43 IS NOT NULL OR T44 IS NOT NULL OR T45 IS NOT NULL OR T46 IS NOT NULL OR T47 IS NOT NULL OR T48 IS NOT NULL OR T49 IS NOT NULL OR T50 IS NOT NULL OR T51 IS NOT NULL OR T52 IS NOT NULL OR T53 IS NOT NULL OR T54 IS NOT NULL OR T55 IS NOT NULL OR T56 IS NOT NULL OR T57 IS NOT NULLOR T58 IS NOT NULL OR T59 IS NOT NULL OR T60 IS NOT NULL OR T61 IS NOT NULL OR T62 IS NOT NULL OR T63 IS NOT NULL OR T64 IS NOT NULL OR T65 IS NOT NULL OR T66 IS NOT NULL OR T67 IS NOT NULL OR T68 IS NOT NULL OR T69 IS NOT NULL OR T70 IS NOT NULL OR T71 IS NOT NULL OR T72 IS NOT NULL OR T73 IS NOT NULL OR T74 IS NOT NULL OR T75 IS NOT NULL OR T76 IS NOT NULL OR T77 IS NOT NULL OR T78 IS NOT NULL OR T79 IS NOT NULL OR T80 IS NOT NULL OR T81 IS NOT NULL OR T82 IS NOT NULL OR T83 IS NOT NULL OR T84 IS NOT NULL OR T85 IS NOT NULL OR T86 IS NOT NULL OR T87 IS NOT NULL) |
Record rejected |
Table
Feedback report messages (TCOR1)
Input record does not respect the Add Tumour record format. There are missing values. |
Core fatal error |
Input record does not respect the Update Tumour record format. There are missing values. |
Core fatal error |
Input record does not respect the Delete Tumour record format. There are missing or extra values. |
Core fatal error |
Table
Revision (TCOR1)
Business rules and Edit logic changed: Fields T58 to T87 added. Variable name changes T31 - CS lymph nodes eval (CS reg nodes eval), and T52 - CS version input original (CS version 1st). The length of variables T24, T25, T28 and T30 has changed. The length of variables Method used to establish date of diagnosis, Diagnostic confirmation, CS extension and CS lymph nodes has changed. |
Business rules and Edit logic changed: Fields T53 to T57 have been added. |
Business rules and Edit logic changed: Field T52 has been added. |
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. |
Edit renamed: Edit formerly known as Correlation Edit No.12. Business rules changed: Handle new fields related to Collaborative staging and TNM data. |
TCOR2
Purpose
This edit ensures that postal code and standard geographic code are coherent.
Table
Referenced fields (TCOR2)
1 |
Tumour record type |
TRECTYPE |
6 |
Postal code |
TPOSTCOD |
1 |
First digit of Postal code |
Not applicable |
2 |
First 2 digits of T8 (province code of Standard geographic code) |
Not applicable |
Business rules
For Add and Update Tumour records, if Postal code is known then
- it must start with 'A' if in Newfoundland or Labrador;
- it must start with 'B' if in Nova Scotia;
- it must start with 'C' if in Prince Edward Island;
- it must start with 'E' if in New Brunswick;
- it must start with 'G', 'H', 'J' or 'K' if in Quebec;
- it must start with 'K', 'L', 'M', 'N' or 'P' if in Ontario;
- it must start with 'R' if in Manitoba;
- it must start with 'R' or 'S' if in Saskatchewan;
- it must start with 'S' or 'T' if in Alberta;
- it must start with 'V' if in British Columbia;
- it must start with 'Y' if in Yukon;
- it must start with 'X' if in Northwest Territories;
- it must start with 'X' if in Nunavut.
Table
Edit logic (TCOR2)
T5 IN ['1', '2'] AND T7 <> '999999' AND ((T8.PROV = '10' AND T7.FIRST <> 'A') OR (T8.PROV = '11' AND T7.FIRST <> 'C') OR (T8.PROV = '12' AND T7.FIRST <> 'B') OR (T8.PROV = '13' AND T7.FIRST <> 'E') OR (T8.PROV = '24' AND T7.FIRST NOT IN ['G', 'H', 'J', 'K']) OR (T8.PROV = '35' AND T7.FIRST NOT IN ['K', 'L', 'M', 'N', 'P']) OR (T8.PROV = '46' AND T7.FIRST <> 'R') OR (T8.PROV = '47' AND T7.FIRST NOT IN ['R', 'S']) OR (T8.PROV = '48' AND T7.FIRST NOT IN ['S', 'T']) OR (T8.PROV = '59' AND T7.FIRST <> 'V') OR (T8.PROV = '60' AND T7.FIRST <> 'Y') OR (T8.PROV = '61' AND T7.FIRST <> 'X') OR (T8.PROV = '62' AND T7.FIRST <> 'X')) |
Record rejected |
Table
Feedback report messages (TCOR2)
Postal code and Standard geographic code indicate 2 different provinces/territories. |
Core error |
Table
Revision (TCOR2)
Edit renamed: Edit formerly known as Correlation Edit No.14. |
TCOR3
Purpose
This edit ensures that census tract and standard geographic code are coherent.
Table
Referenced fields (TCOR3)
1 |
Tumour record type |
TRECTYPE |
7 |
Standard geographic code |
TCODPLAC |
9 |
Census tract |
TCENTRAC |
4 |
First 4 characters of T12 (year of the Date of diagnosis) |
Not applicable |
Business rules
For Add and Update Tumour records
- If Date of diagnosis is between year 1992 and 1995 inclusively, and both Census tract and Standard geographic code are fully known, then the reported Standard geographic code must match the Standard geographic code associated with the Census tract in Eligible Census tracts from 1992 to 199512 .
- If Date of diagnosis is between year 1996 and 2000 inclusively, and both Census tract and Standard geographic code are fully known, then the reported Standard geographic code must match the Standard geographic code associated with the Census tract in Eligible Census tracts from 1996 to 200012.
- If Date of diagnosis is between year 2001 and 2005 inclusively, and both Census tract and Standard geographic code are fully known, then the reported Standard geographic code must match the Standard geographic code associated with the Census tract in Eligible Census tracts from 2001 to 200512.
Table
Edit logic (TCOR3)
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 |
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 |
T5 IN ['1', '2'] AND T8 NOT LIKE '_ _ _ _ 999' AND T9 NOT LIKE '___999.99' AND T12.YEAR >= 2001 AND T12.YEAR < 2005 AND T8 NOT IN [SGC from Eligible Census tracts from 2001 to 2005 where Census tract = T9] |
Record rejected |
Table
Feedback report messages (TCOR3)
Census tract and Standard geographic code combination not found in Census tract Data dictionary – 1991. |
Core error |
Census tract and Standard geographic code combination not found in Census tract Data dictionary – 1996. |
Core error |
Census tract and Standard geographic code combination not found in Census tract Data dictionary – 2001. |
Core error |
Table
Revision (TCOR3)
Business rules and Edit logic changed: Edit modified to include combinations where Census tract indicate an area outside a Census Metropolitan Area. |
Edit renamed: Edit formerly known as Correlation Edit No.15 |
TCOR4
Purpose
This edit rejects tumour data for patients living outside the reporting province/territory at time of diagnosis.
Table
Referenced fields (TCOR4)
2 |
Tumour reporting province/territory |
TREPPROV |
1 |
Tumour record type |
TRECTYPE |
2 |
First 2 characters from T8 (province code of Standard geographic code) |
Not applicable |
Business rules
For Add and Update Tumour records
- Tumour reporting province/territory must be equal to province code found in Standard geographic code.
Table
Edit logic (TCOR4)
T5 IN ['1', '2'] AND T1 <> T8.PROV |
Record rejected |
Table
Feedback report messages (TCOR4)
Reporting province/territory and Standard geographic code must indicate the same province/territory. |
Core error |
Table
Revision (TCOR4)
Edit renamed: Edit formerly known as Correlation Edit No.16. |
TCOR5
Purpose
This edit ensures that expected topography, histology and behaviour values are reported based on the Source classification flag.
Table
Referenced fields (TCOR5)
1 |
Tumour record type |
TRECTYPE |
4 |
ICD-9 cancer code |
TICD_9 |
1 |
Source classification flag |
TSCF |
4 |
ICD-O-2 Histology |
TICD_O2H |
1 |
ICD-O-2 Behaviour |
TICD_O2B |
Business rules
For Add and Update Tumour records
- If Source classification Flag indicates that ICD-9 is the Source classification then ICD-9 cancer code, ICD-O-2/3 Topography40, ICD-O-2 Histology, ICD-O-2 Behaviour41, ICD-O-3 Histology42 and ICD-O-3 Behaviour41 must be reported.
- If Source classification flag indicates that ICD-O-2 is the Source classification then ICD-O-2/3 Topography40, ICD–O–2 Histology, ICD-O-2 Behaviour41, ICD-O-3 Histology42 and ICD-O-3 Behaviour41 must be reported and ICD-9 Cancer code must not be reported.
- If Source classification flag indicates that ICD-O-3 is the Source classification then ICD-O-2/3 Topography42, ICD-O-3 Histology40 and ICD-O-3 Behaviour41 must be reported and ICD-9 cancer code, ICD-O-2 Histology and ICD-O-2 Behaviour must not be reported.
Table
Edit logic (TCOR5)
T5 IN ['1', '2'] AND T14 = '1' AND (T13 = '0000' OR T16 = '0000') |
Record rejected |
T5 IN ['1', '2'] AND T14 = '2' AND T16 = '0000' |
Record rejected |
T5 IN ['1', '2'] AND T14 = '2' AND T13 <> '0000' |
Record rejected |
T5 IN ['1', '2'] AND T14 = '4' AND (T13 <> '0000' OR T16 <> '0000' OR T17 <> '0') |
Record rejected |
Table
Feedback report messages (TCOR5)
Based on the Source classification flag, ICD-9 Cancer code and ICD-O-2 Histology must be reported. |
Core Error |
Based on the Source classification flag, ICD-O-2 Histology must be reported. |
Core Error |
Based on the Source classification flag, ICD-9 Cancer code must not be reported. |
Core Error |
Based on the Source classification flag, ICD-9 cancer code, ICD-O-2 Histology and ICD-O-2 Behaviour must not be reported. |
Core Error |
Table
Revision (TCOR5)
Edit renamed: Edit formerly known as Correlation Edit No.18. Business rules deleted: ICD-10 related rules dropped. Business rules changed: Ensure that topography and histology are reported in accordance with the Source classification flag. Business rules added: Prevent the reporting of data using a classification older than the one indicated by the Source classification flag. |
TCOR6
Purpose
This edit ensures the consistency between ICD-9 Cancer code and related ICD-O-2 values.
Table
Referenced fields (TCOR6)
1 |
Tumour record type |
TRECTYPE |
4 |
ICD-9 cancer code |
TICD_9 |
1 |
Source classification flag |
TSCF |
4 |
ICD-O-2/3 Topography |
TICD_O2T |
4 |
ICD-O-2 Histology |
TICD_O2H |
1 |
ICD-O-2 Behaviour |
TICD_O2B |
Business rules
For Add and Update Tumour records where the source classification is ICD-9
- ICD-9 Cancer code and ICD-O-2/3 Topography must match based on ICD-9 to ICD-O-2 conversion table43.
- If ICD-9 Cancer code is related to a specific histology code (different than 8000) based on ICD-9 to ICD-O-2 conversion table then reported ICD-O-2 Histology should not be generic (equal to 8000).
- ICD-9 Cancer code and ICD-O-2 Behaviour must be coherent based on ICD-9 to ICD-O-2 conversion table.
Table
Edit logic (TCOR6)
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 |
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 |
T5 IN ['1', '2'] AND T14 = '1' AND T13 <> '0000' AND (T13 and T17 NOT IN [ICD-9 to ICD-O-2 conversion table]) |
Record Rejected |
Table
Feedback report messages (TCOR6)
ICD-9 Cancer code and ICD-O-2/3 Topography are not coherent. |
Core Error |
ICD-O-2 Histology could have been more precise based on ICD-9 cancer code. |
Warning |
ICD-9 Cancer code and ICD-O-2 Behaviour are not coherent. |
Core Error |
Table
Revision (TCOR6)
Edit renamed: Edit formerly known as Correlation Edit No.20 Business rules deleted: ICD-10 related rules dropped. Business rules added:
Coherence check between ICD-9 Cancer code and ICD-O2/3 Topography added.
Coherence check between ICD-9 Cancer code and ICD-O-2 Histology added. |
TCOR7
Purpose
This edit ensures the consistency between related ICD-O-2 and ICD-O-3 values.
Table
Referenced fields (TCOR7)
1 |
Tumour record type |
TRECTYPE |
1 |
Source classification flag |
TSCF |
4 |
ICD-O-2/3 Topography |
TICD_O2T |
4 |
ICD-O-2 Histology |
TICD_O2H |
1 |
ICD-O-2 Behaviour |
TICD_O2B |
4 |
ICD-O-3 Histology |
TICD_O3H |
1 |
ICD-O-3 Behaviour |
TICD_O3B |
Business rules
For Add and Update Tumour records where the source classification is either ICD-9 or ICD-O-2
- ICD-O-3 Histology and ICD-O-3 Behaviour combination must be consistent with ICD-O-2/3 Topography, ICD-O-2 Histology and ICD-O-2 Behaviour combination based on ICD-O-2 to ICD-O-3 conversion table44.
Table
Edit logic (TCOR7)
T5 IN ['1', '2'] AND T14 IN ['1', '2'] AND T16 <> '0000' AND (T21 and T22 combination NOT IN [ICD-O-2 to ICD-O-3 conversion table for T15, T16 and T17 combination]) |
Record rejected |
Table
Feedback report messages (TCOR7)
ICD-O-3 Histology and ICD-O-3 Behaviour combination is not coherent with ICD-O-2/3 Topography, ICD-O-2 Histology and ICD-O-2 Behaviour combination. |
Core Error |
Table
Revision (TCOR7)
Edit added: New edit. |
TCOR8
Purpose
Not applicable. (This empty correlation is kept as a placeholder for future requirement implementation.)
Table
Referenced fields (TCOR8)
Not applicable |
Not applicable |
Not applicable |
Business rules
Not applicable
Table
Edit logic (TCOR8)
Not applicable |
Not applicable |
Table
Feedback report messages (TCOR8)
Not applicable |
Not applicable |
Table
Revision (TCOR8)
Not applicable |
TCOR9
Purpose
This edit rejects tumour records that are outside the CCR core scope.
Table
Referenced fields (TCOR9)
1 |
Tumour record type |
TRECTYPE |
4 |
First 4 digits of T12 (year of Date of diagnosis) |
Not applicable |
4 |
ICD-O-2/3 Topography |
TICD_O2T |
4 |
ICD-O-3 Histology |
TICD_O3H |
1 |
ICD-O-3 Behaviour |
TICD_O3B |
Business rules
For Add and Update Tumour records
- ICD-O-2/3 Topography, ICD-O-3 Histology, ICD-O-3 Behaviour and year of Date of diagnosis combination must be within the CCR core scope45.
Table
Edit logic (TCOR9)
T5 IN ['1', '2'] AND (T12.YEAR, T15, T21 and T22 NOT IN [CCR core scope]) |
Record rejected |
Table
Feedback report messages (TCOR9)
Based on ICD-O-2/3 Topography, ICD-O-3 Histology and Behaviour and Date of diagnosis, the tumour is outside the CCR core scope. |
Core Error |
Table
Revision (TCOR9)
Edit consolidated: Edits formerly known as Correlation edit No.13 and Correlation edit No.21. Business rules changed: Verification is now performed on ICD-O-3 values only, regardless of the source classification used. |
TCOR10
Purpose
This edit ensures that invalid combinations of topography and histology are rejected.
Table
Referenced fields (TCOR10)
1 |
Tumour record type |
TRECTYPE |
4 |
First 4 digits of Date of diagnosis (year of date of diagnosis) |
Not applicable |
4 |
ICD-O-2/3 Topography |
TICD_O2T |
4 |
ICD-O-3 Histology |
TICD_O3H |
Business rules
For Add and Update Tumour records
- ICD-O-2/3 Topography and ICD-O-3 Histology and year of date of diagnosis combination must not be invalid based on Invalid site and Histology combinations table46.
Table
Edit logic (TCOR10)
T5 IN ['1', '2'] AND (T12.Year, T15 and T21 IN [Invalid site and Histology combinations]) |
Record rejected |
Table
Feedback report messages (TCOR10)
ICD-O-2/3 Topography, ICD-O-3 Histology and Date of diagnosis combination is either invalid or not eligible for CCR. |
Core error |
Table
Revision (TCOR10)
Referenced fields, Business rules, Edit logic and Feedback report messages changed: Verification now includes Date of diagnosis. |
Edit renamed: Edit formerly known as Correlation Edit No.23. Business rules changed: Verification is now performed on ICD-O-3 values only, regardless of the source classification used. |
TCOR11
Purpose
This edit ensures that invalid combinations of histology and behaviour codes are rejected.
Note: Invalid combinations are combinations that are invalid from a subject matter point of view. These are different from matrix combinations which are combinations not explicitly listed in ICD-O but possible from a subject matter point of view and allowed based on rules or coding guidelines for morphology, ICD-O-3, as outlined in the International Classification of Diseases for Oncology, third edition..
Table
Referenced fields (TCOR11)
1 |
Tumour record type |
TRECTYPE |
4 |
First 4 digits of Date of diagnosis (year of date of diagnosis) |
Not applicable |
4 |
ICD-O-3 Histology |
TICD_O3H |
1 |
ICD-O-3 Behaviour |
TICD_O3B |
Business rules
For Add and Update Tumour records
- ICD-O-3 Histology, ICD-O-3 Behaviour and year of date of diagnosis combination must not be invalid based on Invalid Histology and Behaviour combination table47.
Table
Edit logic (TCOR11)
T5 IN ['1', '2'] AND (T12.YEAR, T21 and T22 IN [Invalid Histology and Behaviour combination]) |
Record rejected |
Table
Feedback report messages (TCOR11)
ICD-O-3 Histology, ICD-O-3 Behaviour and Date of diagnosis combination is invalid. |
Core error |
Table
Revision (TCOR11)
Referenced fields, Business rules, Edit logic and Feedback report messages changed: Verification now includes Date of diagnosis. |
Edit renamed: Edit formerly known as Correlation Edit No.24. Business rules changed: Verification is now performed on ICD-O-3 values only, regardless of the source classification used. |
TCOR12
Purpose
This edit ensures the consistency between the topography and the laterality.
Table
Referenced fields (TCOR12)
1 |
Tumour record type |
TRECTYPE |
4 |
First 4 digits of Date of diagnosis (year of date of diagnosis) |
Not applicable |
4 |
ICD-O-2/3 Topography |
TICD_O2T |
1 |
Laterality |
TLATERAL |
Business rules
For Add and Update Tumour records
- ICD-O-2/3 Topography, Laterality and year of date of diagnosis combination must be valid based on Valid site and Laterality combinations table48.
Table
Edit logic (TCOR12)
T5 IN ['1', '2'] AND (T12.Year, T15 and T19 NOT IN [Valid site and Laterality combinations table]) |
Record rejected |
Table
Feedback report messages (TCOR12)
ICD-O-2/3 Topography, Laterality and Date of diagnosis combination is invalid. |
Core error |
Table
Revision (TCOR12)
Edit renamed: Edit formerly known as Correlation Edit No.22. Business rules changed: Verification is now performed on ICD-O-3 values only, regardless of the source classification used. |
TCOR13
Purpose
This edit ensures that invalid combinations of Method used to establish the date of diagnosis and Diagnostic confirmation codes are rejected.
Table
Referenced fields (TCOR13)
1 |
Tumour record type |
TRECTYPE |
4 |
First 4 digits of Date of Diagnosis (year of Date of Diagnosis) |
N/A |
1 |
Method used to establish the date of diagnosis |
TMETHUSED |
1 |
Diagnostic confirmation |
TMETHCONF |
1 |
Ambiguous Terminology Diagnosis |
TAMBIGTERM |
Business rules
For Add and Update Tumour records where the Date of Diagnosis is in 2004 or after
- Diagnostic confirmation cannot be less definitive than Method used to establish the date of diagnosis. Example: Diagnostic confirmation cannot be "positive cytology" if the Method used to establish the Date of Diagnosis is "positive histology".
- Method used to establish the date of diagnosis and Diagnostic confirmation must indicate the same value when either is "Autopsy Only" or "Death Certificate Only (DCO)" and the other one is reported.
For Add and Update Tumour records where the Date of Diagnosis is in 2008 or after
- If Ambiguous Terminology Diagnosis is Ambiguous terminology only (1) then
- Diagnostic Confirmation must be more definitive than Method used to establish date of diagnosis.
Table
Edit logic (TCOR13)
T5 IN ['1', '2'] AND (T12.YEAR>= '2008' AND T12.YEAR <= '2009') AND T53 = '1' AND T24 IN ['1','2','4','5','6','7', '9'] AND T25 IN ['1','2','4','5','6','7', '9'] AND ((T24='2' AND T25='2') OR (T24<T25))
|
Record rejected |
T5 IN ['1', '2'] AND (T12.YEAR>= '2004' AND T12.YEAR <= '2009') AND T24 IN ['1','2','4','5','6','7', '9'] AND T25 IN ['1','2','4','5','6','7', '9'] AND ((T24='2' AND T25='2') OR (T24<T25 AND NOT (T24='1' and T25='2')))
|
Record rejected |
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 |
T5 IN ['1', '2'] AND (T12.YEAR>= '2010') AND T53 = '1' AND T24 IN ['1','2','4','5','6','7','9','10'] AND T25 IN ['1','2','4','5','6','7','9','10'] AND ((T24='2' AND T25='2') OR (T24 < '10' and T25 < '10' ANDT24<=T25) OR (T24 = '10' AND T25 > '1' AND T24 > T25))
|
Record rejected |
T5 IN ['1', '2'] AND (T12.YEAR>= '2010' ) AND T24 IN ['1','2','4','5','6','7', '9','10'] AND T25 IN ['1','2','4','5','6','7', '9','10'] AND ((T24='2' AND T25='2') OR ((T24 < '10' AND T25 < '10') AND (T24 < T25) AND NOT (T24='1' and T25='2')) OR (T24= '10' AND T24 > T25 AND NOT (T24='10' and T25='1')))
|
Record rejected |
Table
Feedback report messasges (TCOR13)
Diagnostic confirmation must be more definitive than Method used to establish the date of diagnosis when Ambiguous terminology is equal to 1 (Date of diagnosis 2008 to 2009).
|
Core error |
Diagnostic confirmation cannot be less definitive than Method used to establish the date of diagnosis (Date of diagnosis 2004 to 2009).
|
Core error |
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 |
Diagnostic confirmation must be more definitive than Method used to establish the date of diagnosis when Ambiguous terminology is equal to 1 (Date of diagnosis 2010 and onwards).
|
Core error |
Diagnostic confirmation cannot be less definitive than Method used to establish the date of diagnosis (Date of diagnosis 2010 and onwards).
|
Core error |
Table
Revision (TCOR13)
Edit Logic and Feedback report messages: New sub-edits added and existing edits modified to account for new code 10 - Positive histology plus added to Method used to establish date of diagnosis and Diagnostic confirmation. |
New Sub-edit added: To make Diagnostic confirmation more definitive than Method used to establish the date of diagnosis. |
New edit added. |
TCOR14
Purpose
This edit ensures that method of diagnosis is only reported for tumours diagnosed prior to 2004.
Table
Referenced fields (TCOR14)
1 |
Tumour record type |
TRECTYPE |
1 |
Method of diagnosis |
TMETHDIAG |
4 |
First 4 digits of Date of diagnosis (year of date of diagnosis) |
Not applicable |
Business rules
For Add and Update Tumour records
- Method of diagnosis must only be reported when Date of diagnosis is prior 2004.
Table
Edit logic (TCOR14)
T5 IN ['1', '2'] AND T12.YEAR < 2004 AND T11 = '0' |
Record rejected |
T5 IN ['1', '2'] AND T12.YEAR >= 2004 AND T11 <> '0' |
Record rejected |
Table
Feedback report messages (TCOR14)
Method of diagnosis must be reported for tumours diagnosed before 2004. |
Core error |
Method of diagnosis must be coded 'Not reported' for tumours diagnosed in 2004 and onwards. |
Core error |
Table
Revision (TCOR14)
Edit Added: New edit. |
TCOR15
Purpose
This edit ensures that method used to establish the date of diagnosis is only reported for tumours diagnosed in 2004 and onwards.
Table
Referenced fields (TCOR15)
1 |
Tumour record type |
TRECTYPE |
4 |
First 4 digits of Date of diagnosis (year of date of diagnosis) |
Not applicable |
1 |
Method used to establish the date of diagnosis |
TMETHUSED |
Business rules
For Add and Update Tumour records
- Method used to establish the date of diagnosis must only be reported when Date of diagnosis is in 2004 or after.
Table
Edit logic (TCOR15)
T5 IN ['1', '2'] AND T12.YEAR < 2004 AND T24<> '0' |
Record rejected |
T5 IN ['1', '2'] AND T12.YEAR >= 2004 AND T24 = '0' |
Record rejected |
Table
Feedback report messages (TCOR15)
Method used to establish the date of diagnosis must be coded 'Not reported' for tumours diagnosed before 2004. |
Core error |
Method used to establish the date of diagnosis must be reported for tumours diagnosed in 2004 and onwards. |
Core error |
Table
Revision (TCOR15)
Edit Added: New edit. |
TCOR16
Purpose
This edit ensures that diagnostic confirmation is only reported for tumours diagnosed in 2004 and onwards.
Table
Referenced fields (TCOR16)
1 |
Tumour record type |
TRECTYPE |
4 |
First 4 digits of Date of diagnosis (year of date of diagnosis) |
Not applicable |
1 |
Diagnostic confirmation |
TMETHCONF |
Business rules
For Add and Update Tumour records
- Diagnostic confirmation must only be reported when Date of diagnosis is in 2004 or after.
Table
Edit logic (TCOR16)
T5 IN ['1', '2'] AND T12.YEAR < 2004 AND T25<> '0' |
Record rejected |
T5 IN ['1', '2'] AND T12.YEAR >= 2004 AND T25 = '0' |
Record rejected |
Table
Feddback report messages (TCOR16)
Diagnostic confirmation must be coded 'Not reported' for tumours diagnosed before 2004. |
Core error |
Diagnostic confirmation must be reported for tumours diagnosed in 2004 and onwards. |
Core error |
Table
Revision (TCOR16)
Edit Added: New edit. |
TCOR17
Purpose
This edit ensures that grade, differentiation or cell indicator is only reported for tumours diagnosed in 2004 and onwards.
Table
Referenced fields (TCOR17)
1 |
Tumour record type |
TRECTYPE |
4 |
First 4 digits of Date of diagnosis (year of date of diagnosis) |
Not applicable |
1 |
Grade, differentiation or cell indicator |
TGRADE |
Business rules
For Add and Update Tumour records
- Grade, differentiation or cell indicator must only be reported when Date of diagnosis is in 2004 or after.
Table
Edit logic (TCOR17)
T5 IN ['1', '2'] AND T12.YEAR < 2004 AND T23 <> '0' |
Record rejected |
T5 IN ['1', '2'] AND T12.YEAR >= 2004 AND T23 = '0' |
Record rejected |
Table
Feedback report messages (TCOR17)
Grade, differentiation or cell indicator must be coded 'Not reported' for tumours diagnosed before 2004. |
Core error |
Grade, differentiation or cell indicator must be reported for tumours diagnosed in 2004 and onwards. |
Core error |
Table
Revision (TCOR17)
Edit Added: New edit. |
TCOR18
Purpose
This edit ensures that collaborative staging variables are reported for tumours within the CCR collaborative staging scope.
Table
Referenced fields (TCOR18)
1 |
Tumour record type |
TRECTYPE |
4 |
First 4 digits of T12 (year of date of diagnosis) |
Not applicable |
3 |
CS tumour size |
TCSTSIZE |
3 |
CS extension |
TCSEXTN |
1 |
CS tumour size/ext eval |
TCSEVAL |
2 |
CS lymph nodes |
TCSLNODE |
1 |
CS lymph nodes eval |
TCSRNEVL |
2 |
Regional nodes examined |
TCSRNEXAM |
2 |
Regional nodes positive |
TCSRNPOS |
2 |
CS mets at dx |
TCSMDIAG |
1 |
CS mets eval |
TCSMEVAL |
3 |
CS site-specific factor 1 |
TCSSSF1 |
3 |
CS site-specific factor 2 |
TCSSSF2 |
3 |
CS site-specific factor 3 |
TCSSSF3 |
3 |
CS site-specific factor 4 |
TCSSSF4 |
3 |
CS site-specific factor 5 |
TCSSSF5 |
3 |
CS site-specific factor 6 |
TCSSSF6 |
6 |
CS Version input original |
TCSVERINORIG |
1 |
Lymph-vascular invasion |
TLYMPHVASINV |
6 |
CS version input current |
TCSVERINCUR |
3 |
CS site-specific factors 7 - 25 |
TCSSSF7 – TCSSSF25 |
Business rules
For Add and Update Tumour records outside the
CCR collaborative staging scope
48,
- All Collaborative staging variables must be blank.
For Add and Update Tumour records within the
CCR collaborative staging scope,
- All Collaborative staging variables must be reported.
Table
Edit logic (TCOR18)
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.
|
T5 IN ['1', '2'] AND T12.YEAR >= 2004 AND T64 IS NULL AND (T27 IS NULL OR T28 IS NULL OR T29 IS NULL OR T30 IS NULL OR T31 IS NULL OR T32 IS NULL OR T33 IS NULL OR T34 IS NULL OR T35 IS NULL OR T36 IS NULL OR T37 IS NULL OR T38 IS NULL OR T39 IS NULL OR T40 IS NULL OR T41 IS NULL OR T52 IS NULL)
|
CS data items filled with 'R' at posting.
|
T5 IN ['1', '2'] AND T12.YEAR >= 2004 AND T64 IS NOT NULL AND (T27 IS NULL OR T28 IS NULL OR T29 IS NULL OR T30 IS NULL OR T31 IS NULL OR T32 IS NULL OR T33 IS NULL OR T34 IS NULL OR T35 IS NULL OR T36 IS NULL OR T37 IS NULL OR T38 IS NULL OR T39 IS NULL OR T40 IS NULL OR T41 IS NULL OR T52 IS NULL OR T63 IS NULL OR T65 IS NULL OR T66 IS NULL OR T67 IS NULL OR T68 IS NULL OR T69 IS NULL OR T70 IS NULL OR T71 IS NULL OR T72 IS NULL OR T73 IS NULL OR T74 IS NULL OR T75 IS NULL OR T76 IS NULL OR T77 IS NULL OR T78 ISNULL OR T79 IS NULL OR T80 IS NULL OR T81 IS NULL OR T82 IS NULL OR T83 IS NULL)
|
CS data items filled with 'R' at posting.
|
Table
Feedback report messages (TCOR18)
Collaborative staging data must be left blank for tumours diagnosed prior to 2004. Reported data will not be loaded into CCR. |
CS fatal error |
Eligible Collaborative staging site: all Collaborative staging variables must be reported (using CSV1).
|
CS fatal error |
Eligible Collaborative staging site: all Collaborative staging variables must be reported (using CSV2) |
CS fatal error |
Table
Revision (TCOR18)
Referenced Fields: Name and acronym of CS version 1st (TCSFVER) changed to CS version input original (TCSVERINORIG). Name and acronym of CS reg nodes eval (TCSRNEVAL) changed to CS lymph node eval (TCSLNEVAL). Length of CS Extension and CS Lymph nodes has changed from 2 to 3. TCOR18-2 revised to reflect use of CSV1. TCOR18-3 added to reflect use of CSV2. |
Referenced fields and Edit logic updated: T52 added as a new CS variable |
Edit Added: New edit. |
TCOR19
Purpose
This edit ensures that AJCC TNM staging variables are reported for tumours within the CCR AJCC TNM staging scope.
Table
Referenced fields (TCOR19)
1 |
Tumour record type |
TRECTYPE |
4 |
First 4 digits of T12 (year of date of diagnosis) |
Not applicable |
4 |
ICD-O-2/3 Topography |
TICD_O2T |
4 |
ICD-O-3 Histology |
TICD_O3H |
1 |
ICD-O-3 Behaviour |
TICD_O3B |
9 |
AJCC clinical T |
TAJCCCLINT |
3 |
AJCC clinical N |
TAJCCCLINN |
3 |
AJCC clinical M |
TAJCCCLINM |
9 |
AJCC pathologic T |
TAJCCPATHT |
3 |
AJCC pathologic N |
TAJCCPATHN |
3 |
AJCC pathologic M |
TAJCCPATHM |
4 |
AJCC clinical TNM stage group |
TAJCCCLINSG |
4 |
AJCC pathologic TNM stage group |
TAJCCPATHSG |
4 |
AJCC TNM stage group |
TAJCCSG |
2 |
AJCC edition number |
TAJCCEDNUM |
Business rules
For Add and Update Tumour records within the
CCR AJCC TNM staging scope
29,
- All AJCC TNM staging variables must be reported.
For Add and Update Tumour records outside the
CCR AJCC TNM staging scope
- All AJCC TNM staging variables must be blank.
Edit logic
To simplify the edit logic, let Site X be a given site within the CCR AJCC TNM staging scope. Example: Colorectal, breast or prostate.
Table
Edit logic (TCOR19)
T5 IN ['1', '2'] AND (T12.YEAR < 2003 OR T12.YEAR > 2007) AND NOT (T42 IS NULL AND T43 IS NULL AND T44 IS NULL AND T45 IS NULL AND T46 IS NULL AND T47 IS NULL AND T48 IS NULL AND T49 IS NULL AND T50 IS NULL AND T51 IS NULL) |
AJCC TNM data items are not posted. |
T5 IN ['1', '2'] AND (T12.YEAR >= 2003 OR T12.YEAR > 2007) AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND (T42 IS NULL OR T43 IS NULL OR T44 IS NULL OR T45 IS NULL OR T46 IS NULL OR T47 IS NULL OR T48 IS NULL OR T49 IS NULL OR T50 IS NULL OR T51 IS NULL) |
AJCC TNM data items filled with 'R' at posting. |
T5 IN ['1', '2'] AND (T12.YEAR >= 2003 OR T12.YEAR > 2007) AND NOT (T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X]) AND NOT (T42 IS NULL AND T43 IS NULL AND T44 IS NULL AND T45 IS NULL AND T46 IS NULL AND T47 IS NULL AND T48 IS NULL AND T49 IS NULL AND T50 IS NULL AND T51 IS NULL) |
AJCC TNM data items are not posted. |
Table
Feedback report messages (TCOR19)
All AJCC TNM staging data must be blank for tumours diagnosed prior to 2003 or after 2007. Reported data will not be loaded into CCR. |
AJCC TNM fatal error |
Eligible AJCC TNM staging site: all AJCC TNM staging variables must be reported. |
AJCC TNM fatal error |
Non-eligible AJCC TNM staging site: all AJCC TNM staging variables must be blank. Reported data will not be loaded into CCR |
AJCC TNM fatal error |
Table
Revision (TCOR19)
Edit logic and Feedback report messages updated: AJCC variables T42 to T51 no longer reported after 2007. |
Edit Added: New edit. |
TCOR20
Purpose
This edit ensures that TNM stage group is reported only when clinical and pathologic TNM stage group are not reported.
Table
Referenced fields (TCOR20)
1 |
Tumour record type |
TRECTYPE |
4 |
First 4 digits of T12 (year of date of diagnosis) |
Not applicable |
4 |
ICD-O-2/3 Topography |
TICD_O2T |
4 |
ICD-O-3 Histology |
TICD_O3H |
1 |
ICD-O-3 Behaviour |
TICD_O3B |
4 |
AJCC clinical TNM stage group |
TAJCCCLINSG |
4 |
AJCC pathologic TNM stage group |
TAJCCPATHSG |
4 |
AJCC TNM stage group |
TAJCCSG |
Business rules
For Add and Update Tumour records within the
CCR AJCC TNM staging scope
29,
- AJCC TNM stage group can only be reported when both AJCC clinical TNM stage group and AJCC pathologic TNM stage group are either unknown or not assessed.
Edit logic
To simplify the edit logic, let Site X be a given site within the AJCC TNM Staging. Ex:Colorectal, breast or prostate.
Table
Edit logic (TCOR20)
T5 IN ['1', '2'] AND (T12.YEAR >= 2003 AND T12.YEAR <= 2007) AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T50 <> '99' AND (T48 NOT IN ['99', 'X'] OR T49 NOT IN ['99', 'X']) |
AJCC TNM data items filled with 'R' at posting. |
Table
Feedback report messasges (TCOR20)
TNM stage group cannot be reported when clinical and/or pathologic TNM stage group is reported |
AJCC TNM error |
Table
Revision (TCOR20)
Edit logic and Feedback report messages changed: AJCC variables T48, T49 and T50 no longer reported after 2007. |
Edit Added: New edit. |
TCOR21
Purpose
This edit ensures that the combination of AJCC Clinical TNM stage group and the individual clinical T, N, M values combination is acceptable.
Table
Referenced fields (TCOR21)
1 |
Tumour record type |
TRECTYPE |
4 |
First 4 digits of T12 (year of date of diagnosis) |
Not applicable |
4 |
ICD-O-2/3 Topography |
TICD_O2T |
4 |
ICD-O-3 Histology |
TICD_O3H |
1 |
ICD-O-3 Behaviour |
TICD_O3B |
9 |
AJCC clinical T |
TAJCCCLINT |
3 |
AJCC clinical N |
TAJCCCLINN |
3 |
AJCC clinical M |
TAJCCCLINM |
4 |
AJCC clinical TNM stage group |
TAJCCCLINSG |
Business rules
For Add and Update Tumour records within the
CCR AJCC TNM staging scope
29,
- If AJCC clinical TNM stage group is known and assessed then AJCC clinical T, N, M and AJCC clinical TNM stage group combination must be valid for the site49.
- If AJCC clinical TNM stage group is not assessed then AJCC clinical T, N and M combination must not lead to a stage group for the site
- If AJCC clinical TNM stage group is unknown then all AJCC clinical T, N and M values must also be unknown and conversely.
Edit logic
To simplify the edit logic, let Site X be a given site within the CCR AJCC TNM staging scope. Example: Colorectal, breast or prostate.
Table
Edit logic (TCOR21)
T5 IN ['1', '2'] AND (T12.YEAR >= 2003 AND T12.YEAR <= 2007) AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND NOT (T42 = '99' AND T43 = '99' AND T44 = '99') AND T48 NOT IN ['99', 'X'] AND T42, T43, T44, T48 NOT IN [valid AJCC TNM and stage group combination for Site X] |
AJCC TNM data items filled with 'R' at posting. |
T5 IN ['1', '2'] AND (T12.YEAR >= 2003 AND T12.YEAR <= 2007) AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T48 = 'X' AND T42, T43, T44 IN [valid AJCC TNM and stage group combination for Site X] |
AJCC TNM data items filled with 'R' at posting. |
T5 IN ['1', '2'] AND (T12.YEAR >= 2003 AND T12.YEAR <= 2007) AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T48 = '99' AND (T42 <> '99' OR T43 <> '99' OR T44 <> '99') |
AJCC TNM data items filled with 'R' at posting. |
T5 IN ['1', '2'] AND (T12.YEAR >= 2003 AND T12.YEAR <= 2007) AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T48 <> '99' AND T42 = '99' AND T43 = '99' AND T44 = '99' |
AJCC TNM data items filled with 'R' at posting. |
Table
Feedback report messages (TCOR21)
AJCC clinical TNM stage group is invalid for reported AJCC clinical T, N and M values and site. |
AJCC TNM error |
AJCC clinical TNM stage group must be assessed for reported clinical T, N and M values and site. |
AJCC TNM error |
All AJCC clinical T, N and M values must be set to 'Unknown' when AJCC clinical TNM stage group is 'Unknown'. |
AJCC TNM error |
AJCC clinical TNM stage group must be set to 'Unknown' when All AJCC clinical T, N and M values are set to 'Unknown'. |
AJCC TNM error |
Table
Revision (TCOR21)
Edit logic and Feedback report messages changed: AJCC variables T42, T43, T44 and T48 no longer reported after 2007. |
Edit Added: New edit. |
TCOR22
Purpose
This edit ensures that the combination of AJCC pathologic TNM stage group and the individualpathologic T, N, M values is acceptable.
Table
Referenced fields (TCOR22)
1 |
Tumour record type |
TRECTYPE |
4 |
First 4 digits of T12 (year of date of diagnosis) |
Not applicable |
4 |
ICD-O-2/3 Topography |
TICD_O2T |
4 |
ICD-O-3 Histology |
TICD_O3H |
1 |
ICD-O-3 Behaviour |
TICD_O3B |
9 |
AJCC pathologic T |
TAJCCPATHT |
3 |
AJCC pathologic N |
TAJCCPATHN |
3 |
AJCC pathologic M |
TAJCCPATHM |
4 |
AJCC pathologic TNM stage group |
TAJCCPATHSG |
Business rules
For Add and Update Tumour records within the
CCR AJCC TNM staging scope
29.
- If AJCC pathologic TNM stage group is known and assessed then AJCC pathologic T, N, M and AJCC pathologic TNM stage group combination must be valid for the site49.
- If AJCC pathologic TNM stage group is not assessed then AJCC pathologic T, N and M combination must not imply a stage group for the site49.
- If AJCC pathologic TNM stage group is unknown then all AJCC pathologic T, N and M values must also be unknown and conversely.
Edit logic
To simplify the edit logic, let Site X be a given site within the CCR AJCC TNM staging scope. Example: Colorectal, breast or prostate.
Table
Edit logic (TCOR22)
T5 IN ['1', '2'] AND (T12.YEAR >= 2003 AND T12.YEAR <= 2007) AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND NOT (T45 = '99' AND T46 = '99' AND T47 = '99') AND T49 NOT IN ['99', 'X'] AND T45, T46, T47, T49 NOT IN [valid AJCC TNM and stage group combination for Site X] |
AJCC TNM data items filled with 'R' at posting. |
T5 IN ['1', '2'] AND (T12.YEAR >= 2003 AND T12.YEAR <= 2007) AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T49 = 'X' AND T45, T46, T47 IN [valid AJCC TNM and stage group combination for Site X] |
AJCC TNM data items filled with 'R' at posting. |
T5 IN ['1', '2'] AND (T12.YEAR >= 2003 AND T12.YEAR <= 2007) AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T49 = '99' AND (T45 <> '99' OR T46 <> '99' OR T47 <> '99') |
AJCC TNM data items filled with 'R' at posting. |
T5 IN ['1', '2'] AND T12.YEAR >= 2003 AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T49 <> '99' AND T45 = '99' AND T46 = '99' AND T47 = '99' |
AJCC TNM data items filled with 'R' at posting. |
Table
Feedback report messages (TCOR22)
AJCC pathologic TNM stage group is invalid for reported AJCC pathologic T, N and M values and site. |
AJCC TNM error |
AJCC pathologic TNM stage group must be assessed for reported pathologic T, N and M values and site. |
AJCC TNM error |
All AJCC pathologic T, N and M values must be set to 'Unknown' when AJCC pathologic TNM stage group is 'Unknown'. |
AJCC TNM error |
AJCC pathologic TNM stage group must be set to 'Unknown' when All AJCC pathologic T, N and M values are set to 'Unknown'. |
AJCC TNM error |
Table
Revision (TCOR22)
Edit logic and Feedback report messages changed: AJCC variables T45, T46, T47 and T49 no longer reported after 2007. |
Edit Added: New edit. |
TCOR23
Purpose
This edit ensures that the combination of AJCC TNM stage group and the individual clinical/pathologic T, N, M values is acceptable.
Table
Referenced fields(TCOR23)
1 |
Tumour record type |
TRECTYPE |
4 |
First 4 digits of T12 (year of date of diagnosis) |
Not applicable |
4 |
ICD-O-2/3 Topography |
TICD_O2T |
4 |
ICD-O-3 Histology |
TICD_O3H |
1 |
ICD-O-3 Behaviour |
TICD_O3B |
9 |
AJCC clinical T |
TAJCCCLINT |
3 |
AJCC clinical N |
TAJCCCLINN |
3 |
AJCC clinical M |
TAJCCCLINM |
9 |
AJCC pathologic T |
TAJCCPATHT |
3 |
AJCC pathologic N |
TAJCCPATHN |
3 |
AJCC pathologic M |
TAJCCPATHM |
4 |
AJCC TNM stage group |
TAJCCSG |
Business rules
For Add and Update Tumour records within the
CCR AJCC TNM staging scope
29,
- If AJCC TNM stage group is known then the most "accurate" combination of known and assessed AJCC clinical/pathologic T, N, M values and AJCC TNM stage group must be valid49,50. For any staging element (T, N, M), pathologic values are always considered more "accurate" when both clinical and pathologic values are known and assessed.
- Example If cT = 'T2' and pT = 'T1', the most accurate tumour stage is 'T1' (pathologic data take precedence over clinical).
- Example If cM = 'M1' and pM = 'MX', the most accurate metastases stage is 'M1' (pathologic M is not assessed).
Edit logic
To simplify the edit logic, let:
- BestT (clin, path), BestN (clin, path) and BestM (clin, path) be functions that return the most "accurate" tumour, node and metastases staging value based on the rules stated above. When both clinical and pathologic values are '99', 'TX', 'NX' or 'MX', these functions always return the pathologic value.
- Site X be a given site within the CCR AJCC TNM staging scope. Example: Colorectal, breast or prostate.
Table
Edit logic (TCOR23)
T5 IN ['1', '2'] AND (T12.YEAR >= 2003 AND T12.YEAR <= 2007) AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T50 <> '99' AND ((BestT (T42, T45) NOT IN ['99', 'X'] AND BestN (T43, T46) IN ['99', 'X'] AND BestM (T44, T47) IN ['99', 'X'] AND BestT(T42, T45), T50 NOT IN [valid AJCC TNM and stage group combination for Site X]) OR (BestT (T42, T45) IN ['99', 'X'] AND BestN (T43, T46) NOT IN ['99', 'X'] AND BestM (T44, T47) IN ['99', 'X'] AND BestN (T43, T46), T50 NOT IN [valid AJCC TNM and stage group combination for Site X]) OR (BestT (T42, T45) IN ['99', 'X'] AND BestN (T43, T46) IN ['99', 'X'] AND BestM (T44, T47) NOT IN ['99', 'X'] AND BestM (T44, T47), T50 NOT IN [valid AJCC TNM and stage group combination for Site X]) OR (BestT (T42, T45) NOT IN ['99', 'X'] AND BestN (T43, T46) NOT IN ['99', 'X'] AND BestM (T44, T47) IN ['99', 'X'] AND BestT (T42, T45), BestN (T43, T46), T50 NOT IN [valid AJCC TNM and stage group combination for Site X]) OR (BestT (T42, T45) IN ['99', 'X'] AND BestN (T43, T46) NOT IN ['99', 'X'] AND BestM (T44, T47) NOT IN ['99', 'X'] AND BestN (T43, T46), BestM (T44, T47), T50 NOT IN [valid AJCC TNM and stage group combination for Site X]) OR ((BestT (T42, T45) NOT IN ['99', 'X'] AND BestN (T43, T46) IN ['99', 'X'] AND BestM (T44, T47) NOT IN ['99', 'X'] AND BestT(T42, T45), BestM (T44, T47), T50 NOT IN [valid AJCC TNM and stage group combination for Site X]) OR (BestT (T42, T45) NOT IN ['99', 'X'] AND BestN (T43, T46) NOT IN ['99', 'X'] AND BestM (T44, T47) NOT IN ['99', 'X'] AND BestT(T42, T45), BestN (T43, T46), BestM (T44, T47), T50 NOT IN [valid AJCC TNM and stage group combination for Site X])) |
AJCC TNM data items filled with 'R' at posting. |
Table
Feedback report messages (TCOR23)
AJCC TNM stage group is invalid for reported clinical/pathologic T, N and M values and site. |
AJCC TNM error |
Table
Revision (TCOR23)
Edit logic and Feedback report messages changed: AJCC variables T42, T43, T44, T45, T46, T47 and T50 no longer reported after 2007. |
Edit Added: New edit. |
TCOR24
Purpose
This edit ensures that AJCC edition number is coherent with all remaining AJCC TNM staging variables.
Table
Referenced fields (TCOR24)
1 |
Tumour record type |
TRECTYPE |
4 |
First 4 digits of T12 (year of date of diagnosis) |
Not applicable |
4 |
ICD-O-2/3 Topography |
TICD_O2T |
4 |
ICD-O-3 Histology |
TICD_O3H |
1 |
ICD-O-3 Behaviour |
TICD_O3B |
9 |
AJCC clinical T |
TAJCCCLINT |
3 |
AJCC clinical N |
TAJCCCLINN |
3 |
AJCC clinical M |
TAJCCCLINM |
9 |
AJCC pathologic T |
TAJCCPATHT |
3 |
AJCC pathologic N |
TAJCCPATHN |
3 |
AJCC pathologic M |
TAJCCPATHM |
4 |
AJCC clinical TNM stage group |
TAJCCCLINSG |
4 |
AJCC pathologic TNM stage group |
TAJCCPATHSG |
4 |
AJCC TNM stage group |
TAJCCSG |
2 |
AJCC edition number |
TAJCCEDNUM |
Business rules
For Add and Update Tumour records with the
CCR AJCC TNM staging scope
29.
- If AJCC edition number is set to 'Not staged' then all other AJCC TNM staging variables must be set to 'Unknown' and conversely.
Table
Edit logic (TCOR24)
T5 IN ['1', '2'] AND (T12.YEAR >= 2003 AND T12.YEAR <= 2007) AND ((T15 IN [Eligible ICD-O-3 – Topography codes for AJCC TNM Staging Colorectal sites] AND T21 IN [Eligible ICD-O-3 – Histology codes for AJCC TNM Staging Colorectal sites] AND T22 IN [Eligible ICD-O-3 Behaviour codes for AJCC TNM Staging Colorectal sites]) OR (T15 IN [Eligible ICD-O-3 – Topography codes for AJCC TNM Staging Breast sites] AND T21 IN [Eligible ICD-O-3 – Histology codes for AJCC TNM Staging Breast sites] AND T22 IN [Eligible ICD-O-3 – Behaviour codes for AJCC TNM Staging Breast sites]) OR (T15 IN [Eligible ICD-O-3 – Topography codes for AJCC TNM Staging Prostate sites] AND T21 IN [Eligible ICD-O-3 – Histology codes for AJCC TNM Staging Prostate sites] AND T22 IN [Eligible ICD-O-3 – Behaviour codes for AJCC TNM Staging Prostate sites])) AND T42 = '99' AND T43 = '99' AND T44 = '99' AND T45 = '99' AND T46 = '99' AND T47 = '99' AND T48 = '99' AND T49 = '99' AND T50 = '99' AND T51 <> '00' |
AJCC TNM data items filled with 'R' at posting. |
T5 IN ['1', '2'] AND (T12.YEAR >= 2003 AND T12.YEAR <= 2007) AND ((T15 IN [Eligible ICD-O-3 – Topography codes for AJCC TNM Staging Colorectal sites] AND T21 IN [Eligible ICD-O-3 – Histology codes for AJCC TNM Staging Colorectal sites] AND T22 IN [Eligible ICD-O-3 Behaviour codes for AJCC TNM Staging Colorectal sites]) OR (T15 IN [Eligible ICD-O-3 – Topography codes for AJCC TNM Staging Breast sites] AND T21 IN [Eligible ICD-O-3 – Histology codes for AJCC TNM Staging Breast sites] AND T22 IN [Eligible ICD-O-3 – Behaviour codes for AJCC TNM Staging Breast sites]) OR (T15 IN [Eligible ICD-O-3 – Topography codes for AJCC TNM Staging Prostate sites] AND T21 IN [Eligible ICD-O-3 – Histology codes for AJCC TNM Staging Prostate sites] AND T22 IN [Eligible ICD-O-3 – Behaviour codes for AJCC TNM Staging Prostate sites])) AND T51 = '00' AND (T42 <> '99' OR T43 <> '99' OR T44 <> '99' OR T45 <> '99' OR T46 <> '99' OR T47 <> '99' OR T48 <> '99' OR T49 <> '99' OR T50 <> '99') |
All AJCC TNM data items filled with 'R' at posting. |
Table
Feedback report messages (TCOR24)
TNM edition number must be set to 'Not Staged' when all other AJCC TNM staging variables are 'Unknown'. |
AJCC TNM error |
TNM edition number cannot be set to 'Not Staged' when some AJCC TNM staging variables are reported. |
AJCC TNM error |
Table
Revision (TCOR24)
Edit logic and Feedback report messages changed: AJCC variables T42 - T51 no longer reported after 2007. |
Edit Added: New edit. |
TCOR26
Purpose
This edit ensures the consistency between Ambiguous terminology diagnosis and Date of conclusive diagnosis.
Table
Referenced fields (TCOR26)
1 |
Tumour record type |
TRECTYPE |
4 |
First 4 digits of T12 (year of date of diagnosis) |
Not applicable |
1 |
Ambiguous terminology diagnosis |
TAMBIGTERM |
8 |
Date of conclusive diagnosis |
TDATCONCLUSDIAG |
Business rules
For Add and Update Tumour records
- If Date of Diagnosis is before 2008 then Ambiguous terminology diagnosis and Date of conclusive diagnosis must both be blank.
- If Date of Diagnosis is 2008 and onwards then Ambiguous terminology diagnosis and Date of conclusive diagnosis must be either both blank or both reported.
Table
Edit logic (TCOR26)
T5 IN ['1','2'] AND T12.YEAR < 2008 AND (T53 IS NOT NULL OR T54 IS NOT NULL) |
Record rejected |
T5 IN ['1','2'] AND T12.YEAR >= 2008 AND (T53 IS NOT NULL OR T54 IS NOT NULL) AND (T53 IS NULL OR T54 IS NULL) |
Record rejected |
Table
Feedback report messages (TCOR26)
Ambiguous terminology diagnosis and Date of conclusive diagnosis must both be blank if Date of diagnosis is before 2008. |
Core error |
Ambiguous terminology diagnosis and Date of conclusive diagnosis must either both be reported or both be left blank if Date of diagnosis is 2008 and onwards. |
Core error |
Table
Revision (TCOR26)
Edit added: New edit. |
TCOR27
Purpose
This edit ensures the consistency between Type of multiple tumours reported as one primary, Date of multiple tumours and Multiplicity counter.
Table
Referenced fields (TCOR27)
1 |
Tumour record type |
TRECTYPE |
5 |
First 4 digits of T12 (year of date of diagnosis) |
Not applicable |
2 |
Type of multiple tumours reported as one primary |
TMULTTUMONEPRIM |
8 |
Date of multiple tumours |
DDATMULT |
2 |
Multiplicity counter |
TMULTCOUNT |
Business rules
For Add and Update Tumour records
- If Date of Diagnosis is before 2008 then Type of multiple tumours reported as one primary, Date of multiple tumours and Multiplicity counter must all be blank.
- If Date of Diagnosis is 2008 and onwards then Type of multiple tumours reported as one primary, Date of multiple tumours, and Multiplicity counter must be either all blank or all reported.
Table
Edit logic (TCOR27)
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 |
T5 IN ['1','2'] AND T12.YEAR >= 2008 AND (T55 IS NOT NULL OR T56 IS NOT NULL OR T57 IS NOT NULL) AND (T55 IS NULL OR T56 IS NULL OR T57 IS NULL) |
Record rejected |
Table
Feedback report messages (TCOR27)
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 |
Type of multiple tumours reported as one primary, Date of multiple tumours and Multiplicity counter must either all be blank or all be reported if Date of diagnosis is 2008 and onwards. |
Core error |
Table
Revision (TCOR27)
Edit added: New edit. |
TCOR29
Purpose
This edit ensures the consistency between Ambiguous terminology diagnosis and Date of conclusive diagnosis.
Table
Referenced fields (TCOR29)
1 |
Tumour record type |
TRECTYPE |
1 |
Ambiguous terminology diagnosis |
TAMBIGTERM |
8 |
Date conclusive diagnosis |
TDATCONCLUSDIAG |
Business rules
For Add and Update Tumour records
- If Ambiguous terminology diagnosis is "Conclusive terminology within 60 days of original diagnosis" (0) then Date of conclusive diagnosis must be "Not applicable" (88888888).
- If Ambiguous terminology diagnosis is "Ambiguous terminology only" (1) then Date of conclusive diagnosis must be "Accessioned based on ambiguous terminology diagnosis only" (00000000).
- If Ambiguous terminology diagnosis is "Ambiguous terminology followed by conclusive terminology" (2) then Date of conclusive diagnosis must NOT be "Not applicable" (88888888) or "Accessioned based on ambiguous terminology diagnosis only" (00000000).
- If Ambiguous terminology diagnosis is "Unknown terminology" (9) then Date of conclusive diagnosis must indicate that date is unknown (99999999).
- If Ambiguous terminology diagnosis is "Ambiguous terminology followed by conclusive terminology" (2) then Date of conclusive diagnosis should NOT be unknown (99999999).
Table
Edit logic (TCOR29)
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 |
T5 IN ['1', '2'] AND T53 IN ['2'] AND T54 IN ['99999999'] |
Warning |
Table
Feedback report messages (TCOR29)
Ambiguous terminology diagnosis and Date of conclusive diagnosis are inconsistent. |
Core error |
Date of conclusive diagnosis should be a valid calendar date when case is identified as "Ambiguous terminology followed by conclusive terminology". |
Warning |
Table
Revision (TCOR29)
Edit added: New edit. |
TCOR30
Purpose
This edit ensures that date of diagnosis and date of conclusive diagnosis respect a chronological sequence and time frame.
Table
Referenced fields (TCOR30)
1 |
Tumour record type |
TRECTYPE |
8 |
Date of diagnosis |
TDATDIAG |
4 |
First 4 digits of T12 (year of date of diagnosis) |
Not applicable |
2 |
5th and 6th digits of T12 (month of date of diagnosis) |
Not applicable |
2 |
Last 2 digits of T12 (day of date of diagnosis) |
Not applicable |
8 |
Date of Conclusive Diagnosis |
TDATCONCLUSDIAG |
4 |
First 4 digits of T54 (year of date of conclusive diagnosis) |
Not applicable |
2 |
5th and 6th digits of T54 (month of date of conclusive diagnosis) |
Not applicable |
2 |
7th and 8th of T54 (day of date of conclusive diagnosis) |
Not applicable |
Business rules
For Add and Update Tumour records
- Date of conclusive diagnosis must be greater than two months (60 days) after the Date of diagnosis.
Table
Edit logic (TCOR30)
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 |
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 |
T5 IN ['1', '2'] AND T12.YEAR = T54.YEAR AND T12.MONTH = '99' AND T54.MONTH = '99' |
Record rejected |
Table
Feedback report messages (TCOR30)
Date of conclusive diagnosis is before date of diagnosis. |
Core error |
Date of conclusive diagnosis must be greater than 60 days after the date of diagnosis. |
Core error |
If the year of Date of diagnosis is equal to the year of Date of conclusive diagnosis and both months are unknown, the Date of conclusive diagnosis must be unknown. |
Core error |
Table
Revision (TCOR30)
Edit added: New edit. |
TCOR31
Purpose
This edit ensures the consistency between ICD-O-2/3 Topography and Type of multiple tumours reported as one primary.
Table
Referenced fields (TCOR31)
1 |
Tumour record type |
TRECTYPE |
5 |
ICD-O-2/3 Topography |
TICD_02T |
2 |
Type of multiple tumours reported as one primary |
TMULTTUMONEPRIM |
Business rules
For Add and Update Tumour records
- If Type of multiple tumours reported as one primary is coded as "polyp and adenocarcinoma" (31) or "Familial Adenomatous Polyposis (FAP) with carcinoma" (32) Then ICD-O-2/3 Topography must be coded as "Colon" (C180-C189), "Rectosigmoid Junction" (C199) or "Rectum" (C209).
Table
Edit logic (TCOR31)
T5 IN ['1', '2'] AND T55 IN [31,32] and T15 NOT IN [C180-C189, C199 or C209] |
Record rejected |
Table
Feedback report messages (TCOR31)
Type of multiple tumours reported as one primary and ICD-O-2/3 combination is invalid. |
Core error |
Table
Revision (TCOR31)
Edit added: New edit. |
TCOR32
Purpose
This edit ensures the consistency between ICD-O-3 Behaviour and Type of multiple tumours reported as one primary.
Table
Referenced fields (TCOR32)
1 |
Tumour record type |
TRECTYPE |
1 |
ICD-O-3 Behaviour |
TICD_03B |
2 |
Type of multiple tumours reported as one primary |
TMULTTUMONEPRIM |
Business rules
For Add and Update Tumour records
- If Type of multiple tumours reported as one primary is coded as either "Multiple benign (intracranial and CNS sites only)" (10), "Multiple borderline" (11), or "Benign (intracranial and CNS sites only) and borderline" (12), then ICD-O-3 Behaviour must be coded as either "benign" (0) or "borderline" (1).
Table
Edit logic (TCOR32)
T5 IN ['1', '2'] AND T55 IN ['10', '11', '12'] AND T22 NOT IN ['0','1'] |
Record rejected |
Table
Feedback report messages (TCOR32)
Type of multiple tumours reported as one primary and ICD-O-3 behaviour combination is invalid. |
Core error |
Table
Revision (TCOR32)
Edit added: New edit. |
TCOR33
Purpose
This edit ensures the consistency between Type of multiple tumours reported as one primary, Date of multiple tumours, Multiplicity counter, ICD-O-2/3 Topography and ICD-O-3 Histology.
Table
Referenced fields (TCOR33)
1 |
Tumour record type |
TRECTYPE |
4 |
ICD–O–2/3 Topography |
TICD_O2T |
4 |
ICD–O–3 Histology |
TICD_O3H |
1 |
Method used to establish the date of diagnosis |
TMETHUSED |
2 |
Type of multiple tumours reported as one primary |
TMULTTUMONEPRIM |
8 |
Date of multiple tumours |
TDATMULT |
2 |
Multiplicity counter |
TMULTCOUNT |
Business rules
For Add and Update Tumour records where method used to establish the date of diagnosis is not 'death certificate only"
- If ICD–O–2/3 topography is 'unknown primary' (C809) or ICD–O– 3 Histology refers to lymphoma, leukemia or immunoproliferative disease62 [9590-9989 except 9731, 9734, 9740, 9750, 9755, 9756, 9757, 9758, 9930] then Type of multiple tumours reported as one primary, Date of multiple tumours and Multiplicity counter must be 'Information on multiple tumours not applicable for this site'.
- If ICD-O-2/3 topography is known (not C809) and ICD–O–3 Histology does NOT refer to lymphoma, leukemia or immunoproliferative disease [9590-9989 except 9731, 9734, 9740, 9750, 9755, 9756, 9757, 9758, 9930] then Type of multiple tumours reported as one primary, Date of multiple tumours and Multiplicity counter must not be 'Information on multiple tumours not applicable for this site'.
Table
Edit logic (TCOR33)
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 |
T5 IN ['1','2'] AND T24 <> 8 AND (T15 <> 'C809' OR T21 NOT IN [9590-9989]) AND T55 = '88' OR T56 = '88888888' OR T57 = '88' |
Record rejected |
Table
Feedback report messages (TCOR33)
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 |
Type of multiple tumours reported as one primary, Date of multiple tumours and Multiplicity counter must NOT be reported as 'Information on multiple tumours not applicable for this site'. |
Core error |
Table
Revision (TCOR33)
Edit added: New edit. |
TCOR34
Purpose
This edit ensures the consistency between Date of multiple tumours and Type of multiple tumours reported as one primary.
Table
Referenced fields (TCOR34)
1 |
Tumour record type |
TRECTYPE |
2 |
Type of multiple tumours reported as one primary |
TMULTTUMONEPRIM |
8 |
Date of multiple tumours |
DDATMULT |
2 |
Multiplicity counter |
TMULTCOUNT |
Business rules
For Add and Update Tumour records
- If Type of multiple tumours reported as one primary is "single tumour" (00) then Date of multiple tumours must be "single tumour" (00000000) and Multiplicity counter must be '01'.
- If Type of multiple tumours reported as one primary is "not applicable for this site" (88) then Date of multiple tumours must be "information on multiple tumours not applicable for this site" (88888888) and Multiplicity counter must be 'Information on multiple tumours not applicable for this site' (88).
- If Type of multiple tumours reported as one primary indicates multiple tumours (codes 10 through 80) or unknown (99) then Date of multiple tumours must be the date the patient is diagnosed with multiple tumours or unknown (99999999) and Multiplicity counter must be values 02 through 87 or (99).
Table
Edit logic (TCOR34)
T5 IN ['1','2'] AND (T55 = '00' AND T56 <> '00000000' OR T57 <> '01') OR (T55 = '88' AND T56 <> '88888888' OR T57 <> 88' ) OR (T55 IN ['10','11','12','20','30','31','32','40','80' '99'] AND (T56 = '00000000' OR T56 = '88888888') OR (T57 = '01' OR T57 = '88') |
Record rejected |
Table
Feedback report messages (TCOR34)
Type of multiple tumours reported as one primary, date of multiple tumours and multiplicity counter combination is invalid. |
Core error |
Table
Revision (TCOR34)
Business rules and edit logic changed : Modified to accept additional combinations. |
Edit added: New edit. |
TCOR35
Purpose
This edit ensures the consistency between Method used to establish the date of diagnosis, Type of multiple tumours reported as one primary, Date of multiple tumours and Multiplicity counter..
Table
Referenced fields (TCOR35)
1 |
Tumour record type |
TRECTYPE |
1 |
Method used to establish the date of diagnosis |
TMETHUSED |
2 |
Type of multiple tumours reported as one primary |
TMULTTUMONEPRIM |
8 |
Date of multiple tumours |
TDATMULT |
2 |
Multiplicity counter |
TMULTCOUNT |
Business rules
For Add and Update Tumour records
- If Type of multiple tumours reported as one primary is "Unknown" (99) and Method used to establish date of diagnosis is "Death certificate only" (8), then Date of multiple tumours must be "Unknown" (99999999) and Multiplicity counter must be "Multiple tumours present, unknown how many/unknown if single or multiple tumours" (99).
Table
Edit logic (TCOR35)
T5 IN ['1','2'] AND (T55 = '99' AND T24 = '8') AND (T56 <> '99999999' OR T57 <> '99') |
Record rejected |
Table
Feedback report messages (TCOR35)
Method used to establish the date of diagnosis, Type of multiple tumours reported as one primary, Date of multiple tumours and Multiplicity counter combination is invalid. |
Core error |
Table
Revision (TCOR35)
Edit added: New edit. |
TCOR36
Purpose
This edit ensures the consistency between Date of diagnosis and Grade path value and Grade path system.
Table
Referenced fields (TCOR36)
1 |
Tumour record type |
TRECTYPE |
4 |
First 4 digits of T12 (year of date of diagnosis) |
Not applicable |
1 |
Grade path value |
TGRADEPATHVAL |
1 |
Grade path system |
TGRADEPATHSYS |
Business rules
For Add and Update Tumour records
- If Date of Diagnosis is before 2010 then Grade path value and Grade path system must both be blank.
- If Date of Diagnosis is 2010 and onwards then Grade path value and Grade path system must be either both blank or both reported.
Table
Edit logic (TCOR36)
T5 IN ['1','2'] AND T12.YEAR < 2010 AND (T61 IS NOT NULL OR T62 IS NOT NULL) |
Record rejected |
T5 IN ['1','2'] AND T12.YEAR >= 2010 AND (T61 IS NOT NULL OR T62 IS NOT NULL) AND (T61 IS NULL OR T62 IS NULL) |
Record rejected |
Table
Feedback report messages (TCOR36)
Grade path value and Grade path system must both be blank if Date of diagnosis is before 2010. |
Core error |
Grade path value and Grade path system must either both be reported or both be left blank if Date of diagnosis is 2010 and onwards. |
Core error |
Table
Revision (TCOR36)
Edit added: New edit. |
TCOR37
Purpose
This edit ensures the consistency between Grade path value and Grade path system.
Table
Referenced fields (TCOR37)
1 |
Tumour record type |
TRECTYPE |
4 |
First 4 digits of T12 (year of date of diagnosis) |
Not applicable |
1 |
Grade path value |
TGRADEPATHVAL |
1 |
Grade path system |
TGRADEPATHSYS |
Business rules
For Add and Update Tumour records
- If Grade Path System is reported as a two-grade system (2), then Grade Path Value must be reported as Grade 1 or as Grade 2.
- If Grade Path System is reported as a three-grade system (3), then Grade Path Value must be reported as Grade 1, or as Grade 2, or as Grade 3.
- If Grade Path System is reported as a Four-Grade System (4), then Grade Path Value must be reported as Grade 1, or as Grade 2, or as Grade 3, or as Grade 4.
Table
Edit logic (TCOR37)
T5 IN ['1', '2'] AND T12.YEAR >= 2010 AND (T62 = '2' AND (T61 <> '1' OR T61 <> '2')) |
Record rejected |
T5 IN ['1', '2'] AND T12.YEAR >= 2010 AND (T62 = '3' AND (T61 <> '1' OR T61 <> '2' OR T61 <> '3')) |
Record rejected |
T5 IN ['1', '2'] AND T12.YEAR >= 2010 AND (T62 = '4' AND (T61 <> '1' OR T61 <> '2' OR T61 <> '3' OR T61 <> '4')) |
Record rejected |
Table
Feedback report messages (TCOR37)
Grade Path Value must be reported as Grade 1 or Grade 2 when Grade Path System is reported as a two-grade system. |
Core error |
Grade Path Value must be reported as Grade 1, Grade 2 or Grade 3 when Grade Path System is reported as a three-grade system. |
Core error |
Grade Path Value must be reported as Grade 1, Grade 2 or Grade 3, or Grade 4 when Grade Path System is reported as a four-grade system. |
Core error |
Table
Revision (TCOR37)
Edit added: New edit. |
TCOR38
Purpose
This edit ensures consistency between CS mets at dx and CS mets at dx bone, CS mets at dx and CS mets at dx brain, CS mets at dx and CS mets at dx liver, CS mets at dx and CS mets at dx lung.
Table
Referenced fields (TCOR38)
1 |
Tumour record type |
TRECTYPE |
4 |
First 4 digits of T12 (year of date of diagnosis) |
Not applicable |
2 |
CS mets at dx |
TCSMDIAG |
1 |
CS mets at dx bone |
TCSMDXBONE |
1 |
CS mets at dx brain |
TCSMDXBRAIN |
1 |
CS mets at dx liver |
TCSMDXLIVER |
1 |
CS mets at dx lung |
TCSMDXLUNG |
Business rules
For Add and Update Tumour records where Date of diagnosis >= '2010'
- If CS mets at dx bone indicates metastatic involvement, then CS mets at dx must also indicate metastatic involvement.
- If CS mets at dx brain indicates metastatic involvement, then CS mets at dx must also indicate metastatic involvement.
- If CS mets at dx liver indicates metastatic involvement, then CS mets at dx must also indicate metastatic involvement.
- If CS mets at dx lung indicates metastatic involvement, then CS mets at dx must also indicate metastatic involvement.
Table
Edit logic (TCOR38)
T5 IN ['1', '2'] AND T12.YEAR >= 2010 AND (T84 = '1' AND T34 = '00') |
Record rejected |
T5 IN ['1', '2'] AND T12.YEAR >= 2010 AND (T85 = '1' AND T34 = '00') |
Record rejected |
T5 IN ['1', '2'] AND T12.YEAR >= 2010 AND (T86 = '1' AND T34 = '00') |
Record rejected |
T5 IN ['1', '2'] AND T12.YEAR >= 2010 AND (T87 = '1' AND T34 = '00') |
Record rejected |
Table
Feedback report messages (TCOR38)
CS mets dx must indicate metastatic involvement when CS mets at dx bone indicates metastatic involvement. |
Core error |
CS mets dx must indicate metastatic involvement when CS mets at dx brain indicates metastatic involvement. |
Core error |
CS mets dx must indicate metastatic involvement when CS mets at dx liver indicates metastatic involvement. |
Core error |
CS mets dx must indicate metastatic involvement when CS mets at dx lung indicates metastatic involvement. |
Core error |
Table
Revision (TCOR38)
Edit added: New edit. |
The purpose of the match edits is to enforce the business rules between fields on different records. For ease of use, match edits have been divided into four groups:
- Key input match edits: Ensure that input patient and tumour records respect the submission rules in terms of matching keys.
- Key base match edits: Ensure that input patient and tumour records respect the actual state of the CCR in terms of matching keys.
- Data item match edits: Enforce the business rules between data items (other than keys) found on different records.
- Pre-posting match edits: Identify core error-free input records that cannot be posted to the CCR4 because some other related Input records are either missing or have core errors.
3.6.1 Key input match edits
The purpose of the key input match edits is to ensure that input patient and tumour records respect the submission rules in terms of matching keys.
At this level, the following fields are used as key:
- Patient record: Reporting province/territory and patient identification number.
- Tumour record: Reporting province/territory, patient identification number and tumour reference number.
The following table summarizes the purpose of each individual edit of this category:
Table 28
Input match edits summary
Ensures that only one operation affecting a specific patient record is performed (that is, add, delete or update) within a data submission. |
Ensures that only one operation affecting a specific Tumour record is performed (that is, add, delete or update) within a data submission. |
Enforces the submission rules regarding the addition of a patient record. |
Enforces the submission rules regarding the deletion of a patient record. |
Enforces the submission rules regarding the addition of a Tumour record. |
Important note:
When a key input match edit fails, all related Input records (all input patient and tumour records sharing the same reporting province/territory and patient identification number) are rejected. Related records are also called the family of records.
KIM1
Purpose
This edit ensures that only one operation affecting a specific patient record is performed
(add, delete or update) within a data submission.
Table
Referenced fields (KIM1)
2 |
Patient reporting province/territory |
PREPPROV |
12 |
Patient identification number |
PPIN |
Business rules
For Input Patient records
- There cannot be another Input patient record with identical Reporting province/territory and Patient identification number within the same data submission.
Table
Edit logic (KIM1)
Input patient record that matches another Input patient record where P1=P1 AND P2=P2. |
Family rejected51 |
Table
Feedback report messages (KIM1)
Family rejected: more than one Input patient record with the same Patient reporting province/territory and Patient identification number. |
Core error |
Table
Revision (KIM1)
Edit renamed: Formerly known as Input Match Edit No.1. |
KIM2
Purpose
This edit ensures that only one operation affecting a specific tumour record is performed (add, delete or update) within a data submission.
Table
Referenced fields (KIM2)
2 |
Tumour reporting province/territory |
TREPPROV |
12 |
Tumour patient identification number |
TPIN |
9 |
Tumour reference number |
TTRN |
Business rules
For Input Tumour records
- There cannot be another Input Tumour record with identical Reporting province/territory, Patient identification number and Tumour reference number within the same data submission.
Table
Edit logic (KIM2)
Input tumour record that matches another Input tumour record where T1=T1 AND T2=T2 AND T3=T3. |
Family rejected52 |
Table
Feedback report messages (KIM2)
Family rejected: more than one Input tumour record with the same Tumour reporting province/territory, Tumour patient identification number and Tumour reference number. |
Core error |
Table
Revision (KIM2)
Edit renamed: Formerly known as Input Match Edit No.2. |
KIM3
Purpose
This edit enforces the submission rules regarding the addition of a patient record.
Table
Referenced fields (KIM3)
2 |
Patient reporting province/territory |
PREPPROV |
12 |
Patient identification number |
PPIN |
1 |
Patient record type |
PRECTYPE |
2 |
Tumour reporting province/territory |
TREPPROV |
12 |
Tumour patient identification number |
TPIN |
9 |
CCR identification number |
CCR_ID |
1 |
Tumour record type |
TRECTYPE |
Business fields
For Add Patient records
- There must be at least one Add Tumour record with identical Reporting province/territory and Patient identification number and a blank CCR identification number within the same data submission.
- There cannot be any Add Tumour record with identical Reporting province/territory and Patient identification number and a reported CCR identification number within the same data submission.
- There cannot be any Update or Delete Tumour record with identical Reporting province/territory and Patient identification number within the same data submission.
Table
Edit logic KIM3)
Input patient record where P4='1' that matches no Input tumour record where T5='1' AND T1=P1 AND T2=P2. |
Family rejected53 |
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 |
Input patient record where P4='1' that matches an Input tumour record where T5 IN ['2','3'] AND T1=P1 AND T2=P2. |
Family rejected53 |
Table
Feedback report messages (KIM3)
Family rejected: Add Patient record does not match any Add Tumour record. |
Core error |
Family rejected: Add Patient record matches an Add Tumour record with CCR identification number. |
Core error |
Family rejected: Add Patient record matches an Update or Delete Tumour record. |
Core error |
Table
Revision (KIM3)
Edit renamed: Formerly known as Input Match Edit No.3. |
KIM4
Purpose
This edit enforces the submission rules regarding the deletion of a patient record.
Table
referenced fields (KIM4)
2 |
Patient reporting province/territory |
PREPROV |
12 |
Patient identification number |
PPIN |
1 |
Patient record type |
PRECTYPE |
2 |
Tumour reporting province/territory |
TREPPROV |
12 |
Tumour patient identification number |
TPIN |
1 |
Tumour record type |
TRECTYPE |
Business rules
For Delete Patient records
- There must be at least one Delete Tumour record with identical Reporting province/territory and Patient identification number within the same data submission.
- There cannot be any Add or Update Tumour record with identical Reporting province/territory and Patient identification number within the same data submission.
Table
Edit logic (KIM4)
Input patient record where P4='3' that matches no Input tumour record where T5='3' AND P1=T1 AND P2=T2. |
Family rejected53 |
Input patient record where P4='3' that matches Input tumour record where T5 IN ['1','2'] AND P1=T1 AND P2=T2. |
Family rejected53 |
Table
Feedback report messages (KIM4)
Delete Patient record does not match any Delete Tumour record. |
Core error |
Family rejected: Delete Patient record matches an Add or Update Tumour record. |
Core error |
Table
Revision (KIM4)
Edit renamed: Formerly known as Input Match Edit No.4. Business rules changed: CCR identification number has been removed from the edit since it is equivalent to Reporting province/territory – Patient identification number combination. |
KIM5
Purpose
This edit enforces the submission rules regarding the addition of a tumour record.
Table
Referenced fields (KIM5)
2 |
Patient reporting province/territory |
PREPPROV |
12 |
Patient identification number |
PPIN |
1 |
Patient record type |
PRECTYPE |
2 |
Tumour reporting province/territory |
TREPPROV |
12 |
Tumour patient identification number |
TPIN |
9 |
CCR Identification number |
CCR_ID |
1 |
Tumour record type |
TRECTYPE |
Business rules
For Add Tumour records without
CCR identification number
- There must be an Add Patient record with identical Reporting province/territory and Patient identification number within the same data submission.
- There cannot be any Update54 Patient records with identical Reporting province/territory and Patient identification number within the same data submission.
Table
Edit logic (KIM5)
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 |
Input tumour record where T5='1' AND T4 IS NULL that matches Input patient record where P4='2' AND P1=T1 AND P2=T2. |
Family rejected55 |
Table
Feedback report messages (KIM5)
Family rejected: Add Tumour record without CCR_ID does not match an Add Patient record. |
Core error |
Family rejected: Add Tumour record without CCR_ID matches an Update Patient record. |
Core error |
Table
Revision (KIM5)
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
Ensures that no duplicate Patient keys are posted to the CCR. |
Ensures that Update or Delete Patient record keys match a Base Patient record. |
Ensures that no duplicate Tumour keys are posted to the CCR. |
Ensures that an Add Tumour record with CCR identification number matches a Base patient record owned by the Reporting province/territory. |
Ensures that Update or Delete Tumour record keys match a Base tumour record. |
Important note
When a key base match edit fails, the conflicting base record (if any), is included in the detailed feedback report for easier error correction.
Writing conventions throughout the following edit descriptions:
- Expression "base patient/tumour record" means a patient/tumour record already in the CCR.
- Expression "add/update/delete/input patient/tumour record" means a patient/tumour record within the data submission.
- Unless specified otherwise, field numbers prefixed with "I" are input fields and field numbers prefixed with "B" are Base fields.
Example: IT5 is the Tumour record type field on an input tumour record.
Example: IP1 is the Reporting province/territory field on an input patient record
KBM1
Purpose
This edit ensures that no duplicate patient keys are posted to the CCR.
Table
Referenced fields (KBM1)
2 |
Patient reporting province/territory |
PREPPROV |
12 |
Patient identification number |
PPIN |
1 |
Patient record type |
PRECTYPE |
Business rules
For Add Patient records
- There must not be a Base patient record with identical Reporting province/territory and Patient identification number.
Table
Edit logic (KBM1)
Input patient record where IP4='1' that matches a Base patient record where IP1=BP1 AND IP2=BP2. |
Record rejected |
Table
Feedback report messages (KBM1)
A Base patient record with identical reporting province/Territory and Patient identification number already exists. |
Core error |
Table
Revision (KBM1)
Edit renamed: Formerly known as Correlation Edit No.25. |
KBM2
Purpose
This edit ensures that update or delete patient record keys match a base patient record.
Table
Referenced fields (KBM2)
2 |
Patient reporting province/territory |
PREPPROV |
12 |
Patient identification number |
PPIN |
9 |
CCR identification number |
CCR_ID |
1 |
Patient record type |
PRECTYPE |
Business rules
For Update or Delete Patient records
- There must be a Base patient record with identical Reporting province/territory, Patient identification number and CCR identification number.
Table
Edit logic (KBM2)
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 |
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 |
Input patient record where IP4 IN ['2','3'] that matches a Base patient record where IP1<>BP1 AND IP3=BP3. |
Record rejected |
Input patient record where IP4 IN ['2','3'] that match no Base patient record where (IP1=BP1 AND IP2=BP2) OR IP3=BP3. |
Record rejected |
Table
Feedback report messages (KBM2)
Based on the CCR identification number, the Patient identification number is incorrect. |
Core error |
Based on the Reporting province/territory and the Patient identification number, the CCR identification number is incorrect. |
Core error |
Based on the CCR identification number, the Patient is owned by another province/territory. |
Core error |
No matching Patient record found in the CCR. |
Core error |
Table
Revision (KBM2)
Edit renamed: Formerly known as Correlation Edit No.26. |
KBM3
Purpose
This edit ensures that no duplicate tumour keys are posted to the CCR.
Table
Referenced fields (KBM3)
2 |
Tumour reporting province/Territory |
TREPPROV |
12 |
Tumour patient identification number |
TPIN |
9 |
Tumour reference number |
TTRN |
1 |
Tumour record type |
TRECTYPE |
Business rules
For Add Tumour records
- There must not be a Base tumour record with an identical Reporting province/territory, Patient identification number and Tumour reference number.
Table
Edit logic (KBM3)
Input tumour record where IT5='1' that matches a Base tumour record where IT1=BT1 AND IT2=BT2 AND IT3=BT3. |
Record rejected |
Table
Feedback report messages (KBM3)
A Base tumour record with identical Reporting province/territory, Patient identification number and Tumour reference number already exists. |
Core error |
Table
Revision (KBM3)
Edit renamed: Formerly known as Correlation Edit No.32 – Part 1. |
KBM4
Purpose
This edit ensures that an add tumour record with CCR identification number matches a base patient record owned by the reporting province/territory.
Table
Referenced fields (KBM4)
2 |
Tumour reporting province/territory |
TREPPROV |
9 |
Tumour patient identification number |
TPIN |
9 |
CCR identification number |
CCR_ID |
1 |
Tumour record type |
TRECTYPE |
2 |
Patient reporting province/territory |
PREPPROV |
9 |
Patient identification number |
PPIN |
9 |
CCR identification number |
CCR_ID |
Business rules
For Add Tumour records with
CCR identification number
- There must be a Base patient record with the same Reporting province/territory, Patient identification number and CCR identification number.
Table
Edit logic (KBM4)
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 |
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 |
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 |
Input tumour record where IT5='1' AND IT4 IS NOT NULL that matches no Base patient record where (IT1=BP1 AND IT2=BP2) OR IT4=BP3. |
Record rejected |
Table
Feedback report messages (KBM4)
Based on CCR identification number, Patient identification number is incorrect. |
Core error |
Based on Reporting province/territory and Patient identification number, CCR identification number is incorrect. |
Core error |
Based on CCR identification number, the Patient record belongs to another province/territory. |
Core error |
Matching Base patient record not found. |
Core error |
Table
Revision (KBM4)
Edit renamed: Formerly known as Correlation Edit No.32 – Part 2 and Additional rules for updating the CCR #3. Business rules changed: This aggregated edit is now using the Base Patient records. |
KBM5
Purpose
This edit ensures that update or delete tumour record keys match a base tumour record.
Table
Referenced fields (KBM5)
2 |
Tumour reporting province/territory |
TREPPROV |
12 |
Tumour patient identification number |
TPIN |
9 |
Tumour reference number |
TTRN |
9 |
CCR identification number |
CCR_ID |
1 |
Tumour record type |
TRECTYPE |
Business rules
For Update and Delete Tumour records
- There must be a Base tumour record with identical Reporting province/territory, Patient identification number, Tumour reference number and CCR identification number.
Table
Edit logic (KBM5)
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 |
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 |
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 |
Input tumour record where IT5 IN ['2','3'] that matches no Base tumour record where (IT1=BT1 AND IT2=BT2) OR (IT1=BT1 AND IT4=BT4). |
Record rejected |
Table
Feedback report messages (KBM5)
Based on Reporting province/territory, Patient identification number and Tumour reference number, CCR identification number is incorrect. |
Core error |
Based on CCR identification number and Reporting province/territory, Patient identification number is incorrect. |
Core error |
Matching Base tumour record not found. Tumour reference number may be incorrect. |
Core error |
Matching Base tumour record not found. |
Core error |
Table
Revision (KBM5)
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
Ensures that Date of diagnosis and Date of birth are coherent and within time frame. |
Ensures that Date of diagnosis and Date of death are coherent. |
Ensures that Method of diagnosis accurately reflects the relationship between Date of diagnosis and Date of death. |
Ensures that Method used to establish the date of diagnosis accurately reflects the relationship between Date of diagnosis and Date of death. |
Ensures that patient Sex and tumour Topography are coherent. |
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
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 |
x |
|
|
x |
|
|
x |
|
|
x |
|
|
x |
|
|
x |
|
|
x |
|
|
x |
|
|
x |
|
|
x |
|
|
|
x |
|
|
x |
|
|
x |
|
|
x |
|
|
x |
|
|
x |
|
|
x |
|
|
x |
|
|
- |
|
|
- |
|
|
|
x |
|
|
x |
|
|
x |
|
|
x |
|
|
x |
|
|
x |
|
|
x |
|
|
x |
|
|
x |
|
|
x |
DIM1
Purpose
This edit ensures that date of diagnosis and date of birth are coherent and within time frame.
Table
Referenced fields (DIM1)
2 |
Patient reporting province/territory |
PREPPROV |
12 |
Patient identification number |
PPIN |
9 |
CCR identification number |
CCR_ID |
1 |
Patient record type |
PRECTYPE |
8 |
Date of birth |
PDATBIR |
2 |
Tumour reporting province/territory |
TREPPROV |
12 |
Patient identification number |
TPIN |
9 |
Tumour reference number |
TTRN |
9 |
CCR identification number |
CCR_ID |
1 |
Tumour record type |
TRECTYPE |
8 |
Date of diagnosis |
TDATDIAG |
Business rules
Date of diagnosis must be on or after the
Date of birth.
- Year of Date of diagnosis and year of the Date of birth must not be more than 117 years apart.
Edit logic
Important notes:
- These sub-edits must be processed in a specific order. See Section - 3.6.3.1 Special order of execution for more details.
- Partially known dates must be compared using the highest common level of precision.
Example: If Date1 = YYYYMMDD and Date2 = YYYYMM99 then dates must be compared using the year and month only. Thus, for the purpose of the following sub-edits, '20031002' and '20031099' are equal.
Table
Edit logic (DIM1)
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 |
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 |
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 |
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 |
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 |
Core error-free Input patient record where IP4='2' that matches a Base tumour record where IP3=BT4 AND IP11<>'99999999' AND BT12.YEAR>(IP11.YEAR+117) that matches no Core error-free Input Tumour record where IT5 IN ['2','3'] AND IT1=BT1 AND IT2=BT2 AND IT3=BT3. |
Patient record rejected |
Table
Feedback report messages (DIM1)
Date of diagnosis is before Date of birth on matching Input patient record. |
Core error |
Date of diagnosis is before Date of birth on matching Base patient record. |
Core error |
Date of birth is after Date of diagnosis on matching Base tumour record. |
Core error |
Date of diagnosis is more than 117 years after Date of birth on matching Input patient record. |
Core error |
Date of diagnosis is more than 117 years after Date of birth on matching Base patient record. |
Core error |
Date of birth is more than 117 years before Date of diagnosis on matching Base tumour record. |
Core error |
Table
Revision (DIM1)
Edit renamed: Formerly known as Correlation Edit No.28. |
DIM2
Purpose
This edit ensures that date of diagnosis and date of death are coherent.
Table
Referenced fields (DIM2)
2 |
Patient reporting province/territory |
PREPPROV |
12 |
Patient identification number |
PPIN |
9 |
CCR identification number |
CCR_ID |
1 |
Patient record type |
PRECTYPE |
8 |
Date of death |
PDATDEA |
2 |
Tumour reporting province/territory |
TREPPROV |
12 |
Patient identification number |
TPIN |
9 |
Tumour reference number |
TTRN |
9 |
CCR identification number |
CCR_ID |
1 |
Tumour record type |
TRECTYPE |
8 |
Date of diagnosis |
TDATDIAG |
Business rules
Tumour Date of diagnosis cannot be after the patient Date of death.
Edit logic
Important notes:
- These sub-edits must be processed in a specific order. See Section 3.6.3.1 Special order of execution for more details.
- Partially known dates must be compared using the highest common level of precision.
Example: If Date1 = YYYYMMDD and Date2 = YYYYMM99 then dates must be compared using the year and month only. Thus, for the purpose of the following sub-edits, '20031002' and '20031099' are equal.
Table
Edit logic (DIM2)
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 |
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 |
Core error-free Input patient record where IP4='2' AND IP14 NOT IN ['99999999','00000000'] that matches a Base tumour record where IP3=BT4 AND BT12>IP14 (see note above) that matches no Core error-free Input tumour record where IT5 IN ['2','3'] AND IT1=BT1 AND IT2=BT2 AND IT3=BT3. |
Patient record rejected |
Table
Feedback report messages (DIM2)
Date of diagnosis is after Date of death on matching Input patient record. |
Core error |
Date of diagnosis is after Date of death on matching Base patient record. |
Core error |
Date of death is before Date of diagnosis on matching Base tumour record. |
Core error |
Table
Revision (DIM2)
Edit renamed: Formerly known as Correlation Edit No.29. |
DIM3
Purpose
This edit ensures that the method of diagnosis accurately reflects the relationship between the date of diagnosis and the date of death.
Table
Referenced fields (DIM3)
2 |
Patient reporting province/territory |
PREPPROV |
12 |
Patient identification number |
PPIN |
9 |
CCR identification number |
CCR_ID |
1 |
Patient record type |
PRECTYPE |
8 |
Date of death |
PDATDEA |
2 |
Tumour reporting province/territory |
TREPPROV |
12 |
Tumour patient identification number |
TPIN |
9 |
Tumour reference number |
TTRN |
9 |
CCR identification number |
CCR_ID |
1 |
Tumour record type |
TRECTYPE |
1 |
Method of diagnosis |
TMETDIAG |
8 |
Date of diagnosis |
TDATDIAG |
4 |
First 4 digits of T12 (year of date of diagnosis) |
Not applicable |
Business rules
For tumours diagnosed between 1992 and 2003
- Method of diagnosis cannot be 'Death certificate only (DCO)' or 'Autopsy' when the Date of death indicates that the 'Patient is not known to have died'.
- Method of diagnosis can be anything when Date of death is unknown or equal to Date of diagnosis.
- Method of diagnosis cannot be 'Death certificate only (DCO)' when Date of diagnosis is before Date of death.57
Edit logic
Important notes:
- These sub-edits must be processed in a specific order. See Section 3.6.3.1 Special order of execution for more details.
- Partially known dates must be compared using the highest common level of precision.
Example: If Date1 = YYYYMMDD and Date2 = YYYYMM99 then dates must be compared using the year and month only. Thus, for the purpose of the following sub-edits, '20031002' and '20031099' are equal.
Table
Edit logic (DIM3)
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 |
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 |
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 |
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 |
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 |
Core error-free Input patient record where IP4='2' AND IP14 NOT IN ['00000000', '99999999'] that matches a Base tumour record where IP3=BT4 AND BT11='6' AND BT12.YEAR>=1992 AND BT12.YEAR<=2003 AND BT12<IP14 (see note above) that matches no Core error-free Input tumour record where IT5 IN ['2','3'] AND IT1=BT1 AND IT2=BT2 AND IT3=BT3. |
Patient record Rejected |
Table
Feedback report messages (DIM3)
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 |
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 |
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 |
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 |
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 |
Date of death cannot be after Date of diagnosis on a matching Base tumour record where Method of diagnosis is 'Death certificate only (DCO)'. |
Core error |
Table
Revision (DIM3)
Edit renamed: Formerly known as Correlation Edit No.30 – Part 1. |
DIM4
Purpose
This edit ensures that the method used to establish the date of diagnosis accurately reflects the relationship between date of diagnosis and date of death.
Table
Referenced fields (DIM4)
2 |
Patient reporting province/territory |
PREPPROV |
12 |
Patient identification number |
PPIN |
9 |
CCR identification number |
CCR_ID |
1 |
Patient record type |
PRECTYPE |
8 |
Date of death |
PDATDEA |
2 |
Tumour reporting province/territory |
TREPPROV |
12 |
Tumour patient identification number |
TPIN |
9 |
Tumour reference number |
TTRN |
9 |
CCR identification number |
CCR_ID |
1 |
Tumour record type |
TRECTYPE |
1 |
Method of diagnosis |
TMETDIAG |
8 |
Date of diagnosis |
TDATDIAG |
4 |
First 4 digits of T12 (year of date of diagnosis) |
Not applicable |
1 |
Method used to establish the date of diagnosis |
TMETHUSED |
Business rules
For tumours diagnosed in 2004 and onwards
- Method used to establish the date of diagnosis cannot be 'Autopsy only' or 'Death certificate only (DCO)' when Date of death indicates that the 'Patient is not known to have died' or when Date of diagnosis is before Date of death.
- Method used to establish the date of diagnosis can be anything when Date of death is unknown or equal to Date of diagnosis.
Edit logic
Important notes:
- These sub-edits must be processed in a specific order. See Section 3.6.3.1 Special order of execution for more details.
- Partially known dates must be compared using the highest common level of precision.
Example: If Date1 = YYYYMMDD and Date2 = YYYYMM99 then dates must be compared using the year and month only. Thus, for the purpose of the following sub-edits, '20031002' and '20031099' are equal.
Table
Edit logic (DIM4)
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 |
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 |
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 |
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 |
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 |
Core error-free Input patient record where IP4='2' AND IP14 NOT IN ['00000000', '99999999'] that matches a Base tumour record where IP3=BT4 AND BT12.YEAR>=2004 AND BT12<IP14 (see note above) AND BT24 IN ['3','8'] that matches no Core error-free Input tumour record where IT5 IN ['2','3'] AND IT1=BT1 AND IT2=BT2 AND IT3=BT3. |
Patient record rejected |
Table
Feedback report messages (DIM4)
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 |
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 |
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 |
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 |
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 |
Date of death cannot be after Date of Diagnosis on matching Base tumour record where Method used to establish the date of diagnosis is 'Autopsy Only' or 'Death certificate only (DCO)' |
Core error |
Table
Revision (DIM4)
Edit renamed: Formerly known as Correlation Edit No.30 – Part 2. |
DIM5
Purpose
This edit ensures that patient sex and tumour topography are coherent.
Table
Referenced fields (DIM5)
2 |
Patient reporting province/territory |
PREPPROV |
12 |
Patient identification number |
PPIN |
9 |
CCR identification number |
CCR_ID |
1 |
Patient record type |
PRECTYPE |
1 |
Sex |
PSEX |
2 |
Tumour reporting province/territory |
TREPPROV |
12 |
Tumour patient identification number |
TPIN |
9 |
Tumour reference number |
TTRN |
9 |
CCR identification number |
CCR_ID |
1 |
Tumour record type |
TRECTYPE |
4 |
ICD-O-2/3 Topography |
TICD_O2T |
Business rules
- Tumours diagnosed in female organ must be associated with female patient. Female organs are: ICD-O-2/3 Topography: C510-C589.
- Tumours diagnosed in male organ must be associated with male patient. Male organs are: ICD-O-2/3 Topography: C600-C639.
Edit logic
Important notes
These sub-edits must be processed in a specific order. See Section – 3.6.3.1 Special order of execution.
DIM5
Table
Edit logic (DIM5)
(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 |
(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 |
(Core error-free Input patient record where IP4='2' AND IP10 IN ['1','9'] that matches a Base tumour record where IP3=BT4 AND BT15 IN [ICD-O-2/3 Topography codes associated to female organ] that matches no Core error-free Input tumour record where IT5 IN ['2','3'] AND IT1=BT1 AND IT2=BT2 AND IT3=BT3)
OR
(Core error-free Input patient record where IP4='2' AND IP10 IN ['2','9'] that matches a Base tumour record where IP3=BT4 AND BT15 IN [ICD-O-2/3 Topography codes associated to male organ] that matches no Core error-free Input tumour record where IT5 IN ['2','3'] AND IT1=BT1 AND IT2=BT2 AND IT3=BT3) |
Patient record Rejected |
Table
Feedback report messages (DIM5)
ICD-O-2/3 Topography does not agree with Sex code on matching Input patient record. |
Core error |
ICD-O-2/3 Topography does not agree with Sex code on matching Base patient record. |
Core error |
Sex code does not agree with ICD-O-2/3 Topography on a matching Base tumour record. |
Core error |
Table
Revision (DIM5)
Edit renamed: Formerly known as COR31. Business rules changed: Verification is now performed on ICD-O-3 values only. |
DIM6
Purpose
This edit ensures that no "duplicate" tumour records are created for any given patient record (1992-2006 data years only). As of 2007 the CCR has adopted SEER rules. New edits will be implemented to adhere to these new rules.
Table
Referenced fields (DIM6)
2 |
Tumour reporting province/territory |
TREPPROV |
4 |
First 4 digits of Date of diagnosis (year of date of diagnosis) |
Not applicable |
12 |
Tumour patient identification number |
TPIN |
9 |
Tumour reference number |
TTRN |
9 |
CCR identification number |
CCR_ID |
1 |
Tumour record type |
TRECTYPE |
4 |
ICD-O-2/3 Topography |
TICD_O2T |
3 |
First 3 digits of T15 (ICD-O-2/3 Topography site) |
Not applicable |
1 |
Last digit of T15 (ICD-O-2/3 Topography sub-site) |
Not applicable |
1 |
Laterality |
TLATERAL |
4 |
ICD-O-3 Histology |
TICD_O3H |
Business rules
Definitions
- Tumours with "equivalent topographies" are tumours that have:
- The same ICD-O-3 sites56 and sub-sites59or
- The same ICD-O-3 sites but at least one sub-site is 'Overlapping' (8) or 'NOS' (9) or
- Overlapping topographies based on Equivalent Topographies for Overlapping and Unspecified Sites63 concordance table.
- Tumours with "equivalent histologies" are tumours that have:
- The same ICD-O-3 Histology code or
- The same histological group based on Equivalent Histologies56 concordance table.
- A Patient may have multiple Hematopoietic tumours (tumours with ICD-O-3 Histology codes in range 9590-9989) only if they have non-equivalent histologies. (Thus, a patient may not have more than one Hematopoietic tumour in each equivalent histology group, regardless of their respective topography and laterality.)
- A Patient may have multiple non-Hematopoietic tumours with equivalent topographies and equivalent histologies only if they are found on paired organs with specific (right, left one side involved, origin not specified and bilateral) and different laterality.
See Appendix D – Multiple primary tumours rules for
CCR for more detail.
Important notes
These sub-edits must be processed in a specific order. See Section - 3.6.3.1 Special order of execution
Table
Edit logic DIM6)
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 |
Not applicable61 |
Not applicable |
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 |
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 |
Not applicable59 |
Not applicable |
Core error-free Input tumour record (say A) where A.T5 IN ['1','2'] AND A.T4 IS NOT NULL that matches a Base tumour record (say B) where A.T4=B.T4 AND (A.T1<>B.T1 OR A.T3<>B.T3) AND NOT (A.T21 IN ['9590'-'9989'] AND NOT B.T21 IN ['9590'-'9989']) AND (A.T15=B.T15 OR (A.T15.SITE=B.T15.SITE AND (A.T15.SUBSITE IN ['8','9'] OR B.T15.SUBSITE IN ['8','9'])) OR (A.T15 and B.T15 are equivalent based on Equivalent Topographies for Overlapping and Unspecified Sites)) AND (A.T21=B.T21 OR (A.T21 and B.T21 are equivalent based on Equivalent Histologies)) AND (A.T19 IN ['9','0'] OR B.T19 IN ['9','0'] OR A.T19=B.T19) that matches no Core error-free Input Tumour record (say C) where C.T5 IN ['2','3'] AND C.T1=B.T1 AND C.T2=B.T2 AND C.T3=B.T3. |
Tumour record A rejected |
Table
Feedback report messages (DIM6)
Duplicate Input tumour records of the Hematopoietic system based on ICD-O-3 Histology. |
Core error |
Not applicable61 |
Not applicable |
Duplicates an existing Base tumour record of the Hematopoietic system based on ICD-O-3 Histology. |
Core error |
Duplicate Input tumour records based on ICD-O-3 Topography, ICD-O-3 Histology and Laterality. |
Core error |
Not applicable59 |
Not applicable |
Duplicates an existing Base tumour record based on ICD-O-3 Topography, ICD-O-3 Histology and Laterality. |
Core error |
Table
Revision (DIM6)
Edit no longer used (only applied for data years 1992-2006). New multiple primary/histology rules adopted. |
Edit renamed: Formerly known as Correlation Edit No.34A-F. Business rule changed: Potential duplicate tumours with unknown laterality are now rejected.
Edit logic changed to allow the addition of a Tumour record that duplicates a Base tumour record that is about to be updated or deleted. |
3.6.4 Pre-posting match edits
The purpose of the pre-posting match edits is to identify core error-free4 input records that cannot be posted to the CCR because some other related input records are either missing or have core errors.
The following table summarizes the purpose of each individual edit of this category.
Table 32
Pre-posting edits summary
Ensures that no orphan Patient record is created in the CCR. |
Ensures that no orphan Tumour record is created in the CCR. |
PPM1
Purpose
This edit ensures that no orphan patient record is created in the CCR.
Table
Referenced fields (PPM1)
2 |
Tumour reporting province/territory |
TREPPROV |
9 |
Tumour patient identification number |
TPIN |
9 |
CCR identification number |
CCR_ID |
1 |
Tumour record type |
TRECTYPE |
2 |
Patient reporting province/territory |
PREPPROV |
9 |
Patient identification number |
PPIN |
9 |
CCR identification number |
CCR_ID |
1 |
Patient record type |
PRECTYPE |
Business rules
Every Base patient record must have at least one Base tumour record with the same
Reporting province/territory and
Patient identification number and
CCR identification number.
Table
Edit logic (PPM1)
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 |
One or more Core error-free Input tumour records with the same IT4 where IT5='3' that match no Core error-free Input patient record where IP4='3' AND IP3=IT4 and match no Core error-free Input tumour record where IT5 IN ['1','2'] AND IT4=IT4 but match a Base Patient record where IT1=BP1 AND IT4=BP3 and match as many Base tumour records where BT1=IT1 AND BT4=IT4. |
Tumour records rejected |
Table
Feedback report messages (PPM1)
Patient record cannot be added because all associated Add Tumour records have been rejected. |
Core error |
Tumour records cannot be deleted because it would create an orphan Patient record. |
Core error |
Table
Revision (PPM1)
Renamed: Formerly known as Additional rules for updating the CCR #2. Business rules added: Prevent the addition of a new Patient record without Tumour record. |
PPM2
Purpose
This edit ensures that no orphan tumour record is created in the CCR.
Table
Referenced fields (PPM2)
2 |
Tumour reporting province/territory |
TREPPROV |
9 |
Tumour patient identification number |
TPIN |
9 |
CCR identification number |
CCR_ID |
1 |
Tumour record type |
TRECTYPE |
2 |
Patient reporting province/territory |
PREPPROV |
9 |
Patient identification number |
PPIN |
9 |
CCR identification number |
CCR_ID |
1 |
Patient record type |
PRECTYPE |
Business rules
Every Base tumour record must have one Base patient record with the same
CCR identification number.
Table
Edit logic (PPM2)
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 |
Core error-free Input patient record where IP4='3' that matches less Core error-free Input tumour records where IT5='3' AND IT4=IP3 than Base tumour Record where BT1=IP1 AND BT4=IP3 |
Patient record rejected |
Table
Feedback report messages (PPM2)
Tumour record cannot be added because associated Add Patient record has been rejected. |
Core error |
Patient record cannot be deleted because not all related Base tumour records with the same Reporting province/territory have been deleted. |
Core error |
Table
Revision (PPM2)
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. |
Description
The data posting phase is the actual registration of validated data on the CCR database. During this phase, successfully validated input records are added, updated or deleted from the CCR database in accordance with the operation specified by the PTCR on each record. Depending on the operation, a CCR identification number is generated and some derived variables are computed.
In addition to the data registration, the data posting phase also updates auxiliary tables used by other processes such as internal record linkage and death clearance. These tables are:
- Deleted CCR ID,
- Alternate surnames,
- Internal Record Linkage – Don't Link Cross Reference table,
- Death Clearance – Don't Link Cross Reference.
The content and purpose of the above tables are described in Appendix F – Auxiliary tables
Organization
This section is organized as follow:
Table
Data posting
How Input records are processed based on the operation and the record type. |
How patient and tumour derived variables are computed. |
Writing Conventions
Throughout the following pages, the prefixes "I" and "B" preceding field numbers indicate input or base fields respectively. These prefixes are used to indicate the origin of the corresponding variable in expressions.
Example: IP6 stands for P6 variable on an input record.
Example: BTD2 stands for TD2 variable on a base record
3.7.1 Add patient record processing
For each successfully validated add patient record, the following actions are conducted:
A new base patient record is created using:
- CCR identification number (P3): A new CCR identification number (see below);
- Core data items (P1 to -P21 except P4 – input record type): corresponding input record variables values;
- Derived variables (PD1 to PD8): applicable patient derived variables values (see 3.7.7 patient derived variable calculations).
3.7.1.1 CCR identification number creation
The logic to create a new CCR identification number is the following:
LET
- Today _Year4 be the year of today's date (4 digits).
- Today_Year2 be the last two digits of the year of today's date (2 digits).
- Last_CCRID_Year4 be the year the last CCR identification number was created (4 digits).
- CCR_sequence_number be the numeric sequence used to create the CCR identification number (6 digits).
- Check_Digit be a placeholder for the new CCR ID check digit (1 digit)
- New_CCR_ID be a placeholder for the new CCR identification number (9 digits).
- Check_Digit() be a function that returns a check digit based on the logic described in Appendix X – CCR_ID Check Digit Routine.
- || be a string operator that concatenates two text strings together.
BEGIN
- IF Last_CCRID_Year4 < Today_Year4THEN
- CCR_Sequence_Number = '000000';
- Last_CCRID_Year4 =Today _Year4;
- End IF;
- Check_Digit = Check_Digit (Today _Year2 || CCR_Sequence_Number)
- New_CCR_ID = Today _Year2 || CCR_Sequence_Number ||Check_Digit
- CCR_Sequence_Number =CCR_Sequence_Number + 1;
- RETURN New_CCR_ID;
END;
3.7.2 Add tumour record processing
For each add tumour record where the core data items (T1 to T26, T53 to T63 and T84 to T87) are valid, the following actions are conducted:
A new base tumour record is created using:
- Core data items (T1 to T26 (except T5 – Input record type), T53 to T63, and T84 to T87): corresponding input core data items;
- CCR identification number (T4): reported CCR identification number or, if missing, the CCR identification number assigned to the corresponding new patient record (Patient record with the same reporting province/territory and patient identification number);
- CS data items (T27 to T41 and T52 and T64 to T83):
- If the tumour is within the CCR collaborative staging scope and the input CS data items are valid then the input CS data items are loaded onto the database.
- If the tumour is within the CCR collaborative staging scope and one or more of the input CS data items is invalid then the corresponding database fields are "R" filled.
- If the tumour is outside the CCR collaborative staging scope then the corresponding database fields are filled with blanks.
- AJCC TNM data items (T42 to T51 (reported 2003 to 2007)):
- If the tumour is within the CCR AJCC TNM staging scope and the input AJCC TNM data items are valid then the input AJCC TNM data items are loaded onto the database.
- If the tumour is within the CCR AJCC TNM staging scope and one or more of the input AJCC TNM data items is invalid then the corresponding database fields are "R" filled.
- If the tumour is outside the CCR AJCC TNM staging scope then the corresponding database fields are "NULL" filled.
- Derived data items (TD1 to TD20): applicable tumour derived variables values (see 3.7.8 Tumour derived variable calculations).
3.7.3 Update patient record processing
For each successfully validated Update patient record, the following actions are conducted:
- Alternate surname table is updated (see below);
- Death Clearance – Don't Link Cross Reference table is updated (see below);
- Corresponding base patient record is updated using:
- Core data items (P1 to P21 except P4 – Input record type): all input record variable values,
- Derived variables (PD1-PD8): applicable patient derived variables values (see 3.7.7 Patient derived variable calculations).
3.7.3.1 Alternate surname table update
Alternate surname table is updated as following:
Let P3 be the CCR identification number
Let P6 be the patient Current Surname
IF BP6 IS NOT NULL AND (IP6 IS NULL OR IP6 <> BP6) AND (BP3, BP6 combination NOT IN [Alternate Surname table]) THEN
BP3, BP6 combination is added to Alternate Surname table.
END IF
See Appendix F – Auxiliary Tables – Alternate surname for more details.
3.7.3.2 Death Clearance – Don't Link Cross Reference Table Update
If a base Patient is Death-Cleared and the corresponding Input transaction resets all Death Information, the Death Confirmation is said to be Refused and the Death Clearance – Don't Link Cross Reference Table is updated as follows;
Let P3 be the CCR Identification Number
Let P14 be the patient Date of Death
Let P15 be the patient Province/Territory or Country of Death
Let P16 be the patient Death Registration Number
Let P17 be the patient Underlying Cause of Death
Let P18 be the patient Autopsy Confirming Cause of Death
Let PD5 be the Death Clearance Status
IF (BPD5='2' AND IP14='00000000' AND IP15='000' AND IP16='000000' AND IP17='0000' AND IP18='0') THEN
BP3, BP14, BP15, BP16 combination is added to Death Clearance – Don't Link Cross Reference table.
END IF
See Appendix F – Auxiliary Tables – Death Clearance – Don't Link Cross Reference Table for more details.
3.7.4 Update tumour record processing
For each update tumour record where the core data items (T1 to T26 and T53 to T63) are valid, the following actions are conducted:
- Corresponding base tumour record is updated using:
Core data items (T1 to T26 except T5 and T53 to T63– Input record type): Corresponding input core data items;
CS data items (T27 to T41, and T52 and T63 to T83):
- If the tumour is within the CCR collaborative staging scope and the input CS data items are valid then the input CS data items are used.
- If the tumour is within the CCR collaborative staging scope but the input CS data items are invalid then the corresponding base data items are "R" filled.
- If the tumour is outside the CCR collaborative staging scope then NULL values are used.
AJCC TNM data items (T42 to T51 (reported 2003 to 2007)):
- If the tumour is within the CCR AJCC TNM stagingscope and the input AJCC TNM data items are valid then the input AJCC TNM data items are used.
- If the tumour is within the CCR AJCC TNM staging scope but input AJCC TNM data items are invalid then the corresponding base data items are "R" filled.
- If the tumour is outside the CCR AJCC TNM staging scope then NULL values are used.
Derived data items (TD1 to TD20): applicable tumour derived variables values (see 3.7.8 Tumour derived variable calculations)
3.7.5 Delete patient record processing
For each successfully validated delete patient record, the following actions are conducted:
- Deletion or reversal of ownership of the corresponding base patient record (see below);
- If reversal of ownership takes place, corresponding patient derived variables are updated (See3.7.7 Patient derived variable calculations).
If true patient record deletion takes place:
- Deleted CCR_ID table is updated (see below);
- Alternate surname table is updated (see below);
- Internal Record Linkage – Don't Link Cross Reference table is updated (see below);
- Death Clearance – Don't Link Cross Reference table is updated (see below).
3.7.5.1 Patient record deletion or reversal of ownership
A reversal of ownership is needed when a PTCR deletes a patient record but does not own all related tumours records (that is, at least one related tumour record is owned by another jurisdiction). In such case, the Patient record cannot be deleted from the database because it would otherwise create orphan tumour records. In lieu, the ownership (express by P1 – Patient Reporting Province/Territory and P2 – Patient Identification Number values) of the existing base patient record is changed to the jurisdiction that owns Patient's Last Diagnosed Tumour among remaining tumour records.
The Patient's Last Diagnosed Tumour is based on Date of Diagnosis (TDATDIAG) sorted in chronological order and the following additional rules:
When sorting in chronological order tumours based on the Date of Diagnosis, less precise dates must come before more precise dates. For example, if one tumour has a Date of Diagnosis of '19951099' and another tumour has a Date of Diagnosis of '19959999', then the tumour with the Date of Diagnosis of '19951099' is considered the Latest Tumour.
When two or more tumours share the same Date of Diagnosis, tumours are sorted in ascending order by Tumour Reference Number (TTRN), Health Insurance Number (THIN) and Reporting Province Code (TREPPROV) using an alphabetic comparison method63.
For example, if two tumours have the same Date of Diagnosis but one tumour has TTRN='2' and the other has a TTRN='12345', then the latest tumour will be the one with TTRN='2'.
The following box shows the conditions that need to be assessed and the action that must be performed when processing a delete patient record.
Let
P1 be Patient reporting province/territory.
Let
P2 be Patient Identification Number.
Let
P3 be Patient
CCR identification number.
Let
T1 be Tumour reporting province/territory.
Let
T2 be Tumour Patient Identification Number.
Let
T4 be Tumour
CCR identification number.
Let
T12 be Tumour Date of diagnosis.
Let Patient Last Diagnosed Tumour () be a function that returns the latest diagnosed tumour based on the rules specified above.
IF [Base tumour records where BT4 = IP3 AND BT1 <> IP1] IS NOT NULL THEN
-- Reversal of Ownership: BP1 – Base patient reporting province/territory is updated.
BP1 and BP2 = BT1 and BT2 from Patient Last Diagnosed Tumour ([Base tumour record
where BT4 = IP3 AND BT1 <> IP1 AND MAX(BT12)])
ELSE
-- True Patient Deletion must take place
The corresponding Base record is deleted.
END IF
Since the corresponding base patient record is not really deleted from the CCR when a reversal of ownership occurs, the applicable patient derived variables must be updated.
3.7.5.2 Deleted CCR_ID Table update
When a true patient record deletion takes place (contrary to a reversal of ownership), a new entry in Deleted CCR_ID table must be created as following:
Table
Deleted CCR_ID Table update
IP3 |
IP1 |
IP2 |
Today's date using YYYYMMDD format. |
[blank] |
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
Each time a Patient record is written (created or updated), the date of the transaction is saved.
PD1 = Today's date using YYYYMMDD format. |
Not applicable: These variables are only derived for Tabulation master files. See Chapter 4 Tabulation master files for more detail. |
Patient never underwent Death clearance
PD4 = '00000000' |
PD4 stays the same. |
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 |
---|
Each time a Tumour record is written (created or updated), the date of the transaction is saved.
TD1 = Today's date using YYYYMMDD format. |
Not applicable: these variables are only derived for Tabulation master files. See Chapter 4 Tabulation master files for more detail. |
- Description
- Scope
- Content and layout
- Derived variables calculations
- Confidentiality
The Tabulation master file (TMF) produced from the Canadian Cancer Registry (CCR) serves as a snapshot of the entire CCR database. The resulting flat file merges the patient and tumour records from the CCR, using the unique patient record identifier (CCR identification number) to produce a composite record containing both patient and tumour information, with one record for each tumour.
The TMF is used by researchers, academics, regional health unit personnel, health policy/program planners and decision-makers, epidemiologists and public health professionals. It is provided to representatives from organizations such as Health Canada, the Public Health Agency of Canada, the Canadian Institute for Health Information, and other health-related non-government organizations in accordance with applicable legal agreements and Statistics Canada's guidelines pertaining to release of confidential information. It is created on a yearly basis or, in some instances, as warranted by operational requirements.
See http://www.statcan.ca/english/about/privact.htm section 4.5 Confidentiality
4.2 Scope
There are 2 versions of the tabulation master file, the Canadian Cancer Registry tabulation master file (CCRTMF) and the International Agency for Research on Cancer tabulation master file (IARCTMF). These two versions differ in scope as different rules for determining multiple primary neoplasms are applied.
In addition, each of the TMF can either be national (based on patients from all PTCRs) or provincial/territorial (based on patients from only one PTCR). Provincial/territorial TMFs are based on the ownership of Patient records, i.e. tumours are selected based on the reporting province or territory of its related patient record regardless of the province or territory that actually owns the tumour record itself.
4.2.1 CCRTMF – Canadian Cancer Registry tabulation master file.
Variations exist between provincial/territorial Cancer Registries in the coding practices for multiple primaries. Many registries adhere to CCR rules while others use IARC (Québec), IARC/Berg (Ontario) and SEER (Alberta from 1994) for recording tumours in their registries. Given that all cancer records submitted to the CCR are subjected to specific CCR rules for determining multiple primary tumours (see Appendix D – Multiple primary tumours rules for CCR for more details), the resulting CCRTMF consists of a mixture of IARC and CCR rules for determining multiple tumours. As of 2007 the CCR has adopted SEER rules.
4.2.2 IARCTMF – International agency for research on cancer (IARC) tabulation master file
Important note: IARCTMF implementation has changed in 2004. See Revision box at the end of this section for details.
Since not all registries follow the CCR standards, the annual release of cancer incidence and survival statistics are disseminated from STC using the IARC rules for determining multiple primary tumours for the purpose of comparability between registries over time.
All tumour records on IARCTMF have been selected from the CCR according to IARC coding rules for determining multiple primary tumours as specified by the IARC/IACR's Working Groups' Recommendations for coding Multiple Primaries. The International Classification of Diseases for Oncology – Third Edition outlines the rules as follows:
A working party of IARC recommended definitions of multiple neoplasms for the purpose of incidence reporting for international comparison. Their recommendations are:
- Recognition of the existence of two or more primary cancers does not depend on time.
- A primary cancer is one that originates in a primary site or tissue and is neither an extension, nor a recurrence, nor a metastasis.
- Only one tumour shall be recognized as arising in an organ or pair of organs or tissue. For tumours where site is coded by the first edition of ICD-O (or by ICD-9), an organ or tissue is defined by the three-character category of the topography code.
ICD-1O and the Second and Third editions of ICD-O have a more detailed set of topography codes. The sites covered by some groups of codes are considered to be a single organ for the purposes of defining multiple tumours. These topography code groups are shown in Table 24*.
Multifocal tumours – that is, discrete masses apparently not in continuity with other primary cancers originating in the same primary site or tissue, for example bladder – are counted as a single cancer.
Skin cancer presents a special problem as the same individual may have many such neoplasms over a lifetime. The IARC/IACR rules imply that only the first tumour of a defined histological type, anywhere on the skin, is counted as an incident cancer unless, for example, one primary was a malignant melanoma and the other a basal cell carcinoma.
- Rule 3 does not apply in two circumstances:
4.1. For systemic or multicentric cancers potentially involving many discrete organs, four histological groups – lymphomas, leukemias, Kaposi sarcoma, and mesothelioma (groups 7, 8, 9 and 10 in Table 25*) – are included. They are counted only once in any individual.
4.2. Other specific histologies – groups 1, 2, 3, 4, 6, and 11 in Table 25 – are considered to be different for the purpose of defining multiple tumours. Thus, a tumour in the same organ with a 'different' histology is counted as a new tumour. Groups 5 and 12 include tumours that have not been satisfactorily typed histologically and cannot therefore be distinguished from the other groups.
- Source International Classification of Diseases for Oncology – Third Edition, page 35
"* "Table 24" and "Table 25" are reproduced on the following pages.
Table 24
Groups of topography codes from ICD-O-2 and ICD-O-3 considered a single site in the definition of multiple cancers
Base of tongue |
Other and unspecified parts of tongue |
Palate |
Other and unspecified parts of mouth |
Parotid gland |
Other and unspecified major salivary glands |
Tonsil |
Oropharynx |
Pyriform sinus |
Hypopharynx |
Gallbladder |
Other and unspecified parts of biliary tract |
Nasal cavity and middle ear |
Accessory sinus |
Trachea |
Bronchus and lung |
Thymus |
Heart |
Mediastinum |
Overlapping lesion of heart, mediastinum and pleura |
Pleura (visceral, parietal, NOS) |
Vulva |
Vagina |
Other specified female genital organs |
Unspecified female genital organs |
Ovary |
Fallopian tube |
Broad ligaments |
Round ligament |
Parametrium |
Uterine adnexa |
Penis |
Other and unspecified male genital organs |
Kidney |
Renal pelvis |
Ureter |
Other and unspecified urinary organs |
Adrenal gland |
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)
Squamous carcinomas |
805 to 808, 812, 813 |
Basal cell carcinomas |
809 to 811 |
Adenocarcinomas |
814, 816, 819 to 822, 826to 833, 835 to 855, 857, 894 |
Other specific carcinomas |
803, 804, 815, 817 to 818, 823 to 825, 834, 856, 858 to 867 |
Unspecified carcinomas (NOS) |
801, 802 |
Sarcomas and soft tissue tumours |
868 to 871, 880 to 892, 899, 904, 912 to 913, 915 to 925, 937, 954 to 958 |
Lymphomas |
959 to 972 |
Leukemia |
980 to 994, 995, 996, 998 |
Kaposi sarcoma |
914 |
Mesothelioma |
905 |
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 |
Unspecified types of cancer |
800, 997 |
Source: INTERNATIONAL CLASSIFICATION OF DISEASES FOR ONCOLOGY, Third Edition, 2000, page 37, World Health Organization. |
Based on the above rules and tables, the following algorithm is used to eliminate duplicate tumours from the IARC tabulation master files.
Table 35
Algorithm used to eliminate duplicate tumours from IARC TMF
Definitions
Site: Identified by the 3 first digits of the ICD-O-2/3 Topography code.
Topography Group: See Table 24.
Histology Group: See Table 25.
Systemic and Multicentric groups: 7, 8, 9, 10
Non-Systemic and Non-Multicentric groups: 1, 2, 3, 4, 5, 6, 11, 12
Specific Histology groups: 1, 2, 3, 4, 6, 11
Non-Specific Histology groups: 5, 12
Rule 1: When there is more than one tumour in a subset keep the tumour with the highest behaviour/site rank (see Table 35b below), if more than one tumour has the same rank keep the tumour with the earliest Date of diagnosis. If more than one tumour has the same Date of diagnosis, then the tumour with the lowest TTRN, TPIN and TREPPROV is kept.
Logic
For a given patient with more than one tumour:
For Systemic and Multicentric Tumours:
Eliminate duplicate tumours in each Systemic and Multicentric Group using Rule1(regardless of the Site).
For Non-Systemic and Non-Multicentric Tumours:
Eliminate duplicate tumours within the same Site and same Specific Histology group using Rule1;
Eliminate duplicate tumours within the same Site and any Non-Specific Histology group using Rule1;
Eliminate all tumours within Non-Specific Histology groups when there is at least one tumour within Specific Histology groups for the same Site;
Eliminate duplicate tumours within the same Topography group and same Specific Histology group using Rule 1;
Eliminate duplicate tumours within the same Topography group and any Non-Specific Histology group using Rule 1;
Eliminate all tumours within Non-Specific Histology groups when there is at least one tumour within Specific Histology groups for the same Topography group.
Table 35b
Ranking of Behaviour to Identify most 'malignant' tumour:
0 |
4 |
4 |
---|
1 |
3 |
3 |
---|
2 |
2 |
1 |
---|
3 |
1 |
1 |
---|
When a patient has only two tumours, it may be easier to use the following decision tree instead of the above algorithm to assess if tumours are duplicates. When a patient has more than two tumours, the above algorithm must always be used to eliminate duplicate tumours since the decision tree does not indicate the order in which to process tumours pairs which in turn may lead to incorrect results.
Figure 1 Decision tree to assess if two tumours are duplicates based on IARC rules

Table
Revision (Description)
Table 35 changed: Behaviour/site ranking to take precedence for duplicate tumours Table 35b added: Ranking of Behaviour to Identify the most 'malignant' tumour: |
Table 24 changed:Topography group added: C38.4 |
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. |
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
2 |
1 |
- |
2 |
Patient reporting province/territory |
PREPPROV |
12 |
3 |
- |
14 |
Patient identification number |
PPIN |
9 |
15 |
- |
23 |
CCR identification number |
CCR_ID |
1 |
24 |
- |
24 |
Type of Current surname |
PTYP_CUR |
25 |
25 |
- |
49 |
Current surname |
PCURSNAM |
15 |
50 |
- |
64 |
First given name |
PGNAME_1 |
15 |
65 |
- |
79 |
Second given name |
PGNAME_2 |
7 |
80 |
- |
86 |
Third given name |
PGNAME_3 |
1 |
87 |
- |
87 |
Sex |
PSEX |
8 |
88 |
- |
95 |
Date of birth |
PDATBIR |
3 |
96 |
- |
98 |
Province/territory or country of birth |
PPROVBIR |
25 |
99 |
- |
123 |
Birth surname |
PBIRNAM |
8 |
124 |
- |
131 |
Date of death |
PDATDEA |
3 |
132 |
- |
134 |
Province/territory or country of death |
PPROVDEA |
6 |
135 |
- |
140 |
Death registration number |
PDEAREG |
4 |
141 |
- |
144 |
Underlying cause of death |
PCAUSDEA |
1 |
145 |
- |
145 |
Autopsy confirming cause of death |
PAUTOPSY |
8 |
146 |
- |
153 |
Patient date of transmission |
PDATTRAN |
2 |
154 |
- |
155 |
Date of birth flag (blank until 2010) |
PDATBIRFLAG |
2 |
156 |
- |
157 |
Date of death flag (blank until 2010) |
PDATDEAFLAG |
8 |
158 |
- |
165 |
Processing date – patient record |
PDCCRDATPROC |
1 |
166 |
- |
166 |
Vital status |
PDCCRVITALST |
2 |
167 |
- |
168 |
Number of tumours |
PDCCRNBRTMRS |
8 |
169 |
- |
176 |
Death clearance cut off date |
PDDCDATCO |
1 |
177 |
- |
177 |
Death clearance status |
PDDCSTAT |
1 |
178 |
- |
178 |
Death clearance method |
PDDCMETH |
4 |
179 |
- |
182 |
Death clearance underlying cause of death |
PDDCUCD |
8 |
183 |
- |
190 |
Date of death (un) confirmation |
PDDCDATCN |
2 |
191 |
- |
192 |
Tumour reporting province/territory |
TREPPROV |
12 |
193 |
- |
204 |
Tumour patient identification number |
TPIN |
9 |
205 |
- |
213 |
Tumour reference number |
TTRN |
25 |
214 |
- |
238 |
Name of place of residence |
TPLACRES |
6 |
239 |
- |
244 |
Postal code |
TPOSTCOD |
7 |
245 |
- |
251 |
Standard geographic code |
TCODPLAC |
9 |
252 |
- |
260 |
Census tract |
TCENTRAC |
15 |
261 |
- |
275 |
Health insurance number |
THIN |
1 |
276 |
- |
276 |
Method of diagnosis |
TMETHDIAG |
8 |
277 |
- |
284 |
Date of diagnosis |
TDATDIAG |
4 |
285 |
- |
288 |
ICD-9 cancer code |
TICD_9 |
1 |
289 |
- |
289 |
Source classification flag |
TSCF |
4 |
290 |
- |
293 |
ICD-O-2/3 Topography |
TICD_O2T |
4 |
294 |
- |
297 |
ICD-O-2 Histology |
TICD_O2H |
1 |
298 |
- |
298 |
ICD-O-2 Behaviour |
TICD_O2B |
1 |
299 |
- |
299 |
Laterality |
TLATERAL |
4 |
300 |
- |
303 |
ICD-O-3 Histology |
TICD_O3H |
1 |
304 |
- |
304 |
ICD-O-3 Behaviour |
TICD_O3B |
1 |
305 |
- |
305 |
Grade, differentiation or cell indicator |
TGRADE |
2 |
306 |
- |
307 |
Method used to establish date of diagnosis |
TMETHUSED |
2 |
308 |
- |
309 |
Diagnostic confirmation |
TMETHCONF |
8 |
310 |
- |
317 |
Tumour date of transmission |
TDATTRAN |
3 |
318 |
- |
320 |
CS tumour size |
TCSTSIZE |
3 |
321 |
- |
323 |
CS extension |
TCSEXTN |
1 |
324 |
- |
324 |
CS tumour size/ext eval |
TCSEVAL |
3 |
325 |
- |
327 |
CS lymph nodes |
TCSLNODE |
1 |
328 |
- |
328 |
CS reg nodes eval |
TCSRNEVAL |
2 |
329 |
- |
330 |
Regional nodes examined |
TCSRNEXAM |
2 |
331 |
- |
332 |
Regional nodes positive |
TCSRNPOS |
2 |
333 |
- |
334 |
CS mets at dx |
TCSMDIAG |
1 |
335 |
- |
335 |
CS mets Eval |
TCSMEVAL |
3 |
336 |
- |
338 |
CS site-specific factor 1 |
TCSSSF1 |
3 |
339 |
- |
341 |
CS site-specific factor 2 |
TCSSSF2 |
3 |
342 |
- |
344 |
CS site-specific factor 3 |
TCSSSF3 |
3 |
345 |
- |
347 |
CS site-specific factor 4 |
TCSSSF4 |
3 |
348 |
- |
350 |
CS site-specific factor 5 |
TCSSSF5 |
3 |
351 |
- |
353 |
CS site-specific factor 6 |
TCSSSF6 |
9 |
354 |
- |
362 |
AJCC clinical T |
TAJCCCLINT |
3 |
363 |
- |
365 |
AJCC clinical N |
TAJCCCLINN |
3 |
366 |
- |
368 |
AJCC clinical M |
TAJCCCLINM |
9 |
369 |
- |
377 |
AJCC pathologic T |
TAJCCPATHT |
6 |
378 |
- |
383 |
AJCC pathologic N |
TAJCCPATHN |
3 |
384 |
- |
386 |
AJCC pathologic M |
TAJCCPATHM |
4 |
387 |
- |
390 |
AJCC clinical TNM stage group |
TAJCCCLINSG |
4 |
391 |
- |
394 |
AJCC pathologic TNM stage group |
TAJCCPATHSG |
4 |
395 |
- |
398 |
AJCC TNM stage group |
TAJCCSG |
2 |
399 |
- |
400 |
AJCC TNM edition number |
TAJCCEDNUM |
6 |
401 |
- |
406 |
CS version input original |
TCSVERINORIG |
1 |
407 |
- |
407 |
Ambiguous Terminology Diagnosis |
TAMBIGTERM |
8 |
408 |
- |
415 |
Date of conclusive diagnosis |
TDATCONCLUSDIAG |
2 |
416 |
- |
417 |
Type of multiple tumours reported as one primary |
TMULTTUMONEPRIM |
8 |
418 |
- |
425 |
Date of multiple tumours |
TDATMULT |
2 |
426 |
- |
427 |
Multiplicity counter |
TMULTCOUNT |
2 |
428 |
- |
429 |
Date of diagnosis flag (blank until 2010) |
TDATDIAGFLAG |
2 |
430 |
- |
431 |
Date of conclusive diagnosis flag (blank until 2010) |
TDATCONCLUSDIAGFLAG |
2 |
432 |
- |
433 |
Date of multiple tumours flag (blank until 2010) |
TDATMULTFLAG |
1 |
434 |
- |
434 |
Grade Path Value (blank until 2010) |
TGRADEPATHVAL |
1 |
435 |
- |
435 |
Grade Path System (blank until 2010) |
TGRADEPATHSYS |
1 |
436 |
- |
436 |
Lymph-vascular invasion |
TLYMPHVASINV |
6 |
437 |
- |
442 |
CS Version input current |
TCSVERINCUR |
3 |
443 |
- |
445 |
CS Site-Specific Factor 7 |
TCSSSF7 |
3 |
446 |
- |
448 |
CS Site-Specific Factor 8 |
TCSSSF8 |
3 |
449 |
- |
451 |
CS Site-Specific Factor 9 |
TCSSSF9 |
3 |
452 |
- |
454 |
CS Site-Specific Factor 10 |
TCSSSF10 |
3 |
455 |
- |
457 |
CS Site-Specific Factor 11 |
TCSSSF11 |
3 |
458 |
- |
460 |
CS Site-Specific Factor 12 |
TCSSSF12 |
3 |
461 |
- |
463 |
CS Site-Specific Factor 13 |
TCSSSF13 |
3 |
464 |
- |
466 |
CS Site-Specific Factor 14 |
TCSSSF14 |
3 |
467 |
- |
469 |
CS Site-Specific Factor 15 |
TCSSSF15 |
3 |
470 |
- |
472 |
CS Site-Specific Factor 16 |
TCSSSF16 |
3 |
473 |
- |
475 |
CS Site-Specific Factor 17 |
TCSSSF17 |
3 |
476 |
- |
478 |
CS Site-Specific Factor 18 |
TCSSSF18 |
3 |
479 |
- |
481 |
CS Site-Specific Factor 19 |
TCSSSF19 |
3 |
482 |
- |
484 |
CS Site-Specific Factor 20 |
TCSSSF20 |
3 |
485 |
- |
487 |
CS Site-Specific Factor 21 |
TCSSSF21 |
3 |
488 |
- |
490 |
CS Site-Specific Factor 22 |
TCSSSF22 |
3 |
491 |
- |
493 |
CS Site-Specific Factor 23 |
TCSSSF23 |
3 |
494 |
- |
496 |
CS Site-Specific Factor 24 |
TCSSSF24 |
3 |
497 |
- |
499 |
CS Site-Specific Factor 25 |
TCSSSF25 |
1 |
500 |
- |
500 |
CS Mets at Dx - Bone (blank until 2010) |
TCSMDXBONE |
1 |
501 |
- |
501 |
CS Mets at Dx - Brain (blank until 2010) |
TCSMDXBRAIN |
1 |
502 |
- |
502 |
CS Mets at Dx - Liver (blank until 2010) |
TCSMDXLIVER |
1 |
503 |
- |
503 |
CS Mets at Dx - Lung (blank until 2010) |
TCSMDXLUNG |
8 |
504 |
- |
511 |
Processing date – tumour record |
TDCCRDATPROC |
2 |
512 |
- |
513 |
Sequence number |
TDCCRSEQNUM |
3 |
514 |
- |
516 |
Age at diagnosis |
TDCCRAGEDIAG |
2 |
517 |
- |
518 |
Age group at diagnosis |
TDCCRAGEGRP |
5 |
519 |
- |
523 |
Survival interval |
TDDCSURVINT |
1 |
524 |
- |
524 |
Survival censor |
TDDCCENSOR |
2 |
525 |
- |
526 |
Derived AJCC T |
TDCSAJCCT |
2 |
527 |
- |
528 |
Derived AJCC N |
TDCSAJCCN |
2 |
529 |
- |
530 |
Derived AJCC M |
TDCSAJCCM |
1 |
531 |
- |
531 |
Derived AJCC T descriptor |
TDCSAJCCTDESC |
1 |
532 |
- |
532 |
Derived AJCC N descriptor |
TDCSAJCCNDESC |
1 |
533 |
- |
533 |
Derived AJCC M descriptor |
TDCSAJCCMDESC |
2 |
534 |
- |
534 |
Derived AJCC stage group |
TDCSAJCCSG |
1 |
536 |
- |
536 |
Derived AJCC flag |
TDCSAJCCF |
1 |
537 |
- |
537 |
Derived SS1977 |
TDCSSS1977 |
1 |
538 |
- |
538 |
Derived SS1977 flag |
TDCSSS1977F |
1 |
539 |
- |
539 |
Derived SS2000 |
TDCSSS2000 |
1 |
540 |
- |
540 |
Derived SS2000 flag |
TDCSSS2000F |
6 |
541 |
- |
546 |
CS version derived |
TCSVERDER |
Table
Revision (Content and layout)
Variable names changed: CS version 1st to CS version input original (acronym changed from TCSFVER to TCSVERINORIG), CS reg nodes eval to CS lymph nodes eval (acronym changed from TCSRNEVAL to TCSLNEVAL), CS version latest to CS version derived (acronym changed from TCSLVER to TCSVERDER) . The length of variables Method used to establish date of diagnosis, Diagnostic confirmation, CS extension and CS lymph nodes has changed.
Addition of P20, P21, T58 – T87
Re-positioning of many variables |
Addition of T53 to T57 |
Addition of T52, deletion of TD20 |
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
Let P14 be the patient Date of death
IF P14 = '00000000' THEN
PD2 = '1'
ELSE
PD2 = '2'
End IF |
PD3 = Patient's total number of tumours within the applicable TMF scope. |
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. |
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 = Corresponding age group based on TD3 value. (See TD4 – Specified values and meaning.) |
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 |
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. |
Table
Revision (Derived variable calculations)
PD2 – Vital Status is now derived at TMF time |
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
- |
- |
Hidden |
- |
Hidden |
Hidden |
- |
Hidden |
Hidden |
- |
Hidden |
Hidden |
- |
Hidden |
Hidden |
- |
Hidden |
Hidden |
- |
- |
Hidden |
- |
Hidden |
Hidden |
In order to keep the same record layout for all Tabulation Master Files, hidden fields are simply filled with 'X'.
Appendix C – AJCC TNM reference tables
Appendix D – Multiple primary tumours rules for CCR
Appendix E – Interval and mean time between dates
Appendix F – Auxiliary tables
Appendix G – Grade, differentiation or cell indicator guidelines (for T23)
Appendix H – CCR Ambiguous Terms (for T12 and T53)
Appendix I – Guidelines for Abstracting and Determining Death Certificate Only (DCO) Cases for
Provincial/Territorial Cancer Registries (PTCRs) in Canada (for T12 and P18)
Appendix J – Internal between two dates (complete or partial)
Appendix K - Flavours of Null Table
Appendix T – Residency guidelines in Canada (for T1, T6, P1)
Appendix X – CCR_ID check digit routine
Appendix Z – References
This appendix describes all AJCC TNM reference tables, namely:
- Valid AJCC clinical T by site;
- Valid AJCC clinical N by site;
- Valid AJCC clinical M by site;
- Valid AJCC pathologic T by site;
- Valid AJCC pathologic N by site;
- Valid AJCC pathologic M by site;
- Valid AJCC clinical TNM stage group by site;
- Valid AJCC pathologic TNM stage group by site;
- Valid AJCC TNM stage group by site;
- Valid AJCC T, N, M and stage group combination by site
Valid AJCC clinical T by site (2003 to 2007)
Table usage notes:
See Chapter 1 for a complete description of each eligible site in terms of topography, histology and behaviour.
Table 39
Valid AJCC clinical T by stageable site
TX |
TX |
TX |
T0 |
T0 |
T0 |
Tis |
-- |
Tis |
TisDCIS |
-- |
-- |
TisLCIS |
-- |
-- |
TisPagets |
-- |
-- |
T1 |
T1 |
T1 |
T1mic |
-- |
-- |
T1a |
T1a |
-- |
T1b |
T1b |
-- |
T1c |
T1c |
-- |
T2 |
T2 |
T2 |
-- |
T2a |
-- |
-- |
T2b |
-- |
-- |
T2c |
-- |
T3 |
T3 |
T3 |
-- |
T3a |
-- |
-- |
T3b |
-- |
T4 |
T4 |
T4 |
T4a |
-- |
-- |
T4b |
-- |
-- |
T4c |
-- |
-- |
T4d |
-- |
-- |
99 |
99 |
99 |
Valid AJCC clinical N by site (2003 to 2007)
Table usage notes:
See Chapter 1 for a complete description of each stageable site in terms of topography, histology and behaviour.
Table 40
Valid AJCC clinical N by stageable site
NX |
NX |
NX |
N0 |
N0 |
N0 |
N1 |
N1 |
N1 |
N2 |
-- |
N2 |
N2a |
-- |
-- |
N2b |
-- |
-- |
N3 |
-- |
-- |
N3a |
-- |
-- |
N3b |
-- |
-- |
N3c |
-- |
-- |
99 |
99 |
99 |
Valid AJCC clinical M by site (2003 to 2007)
Table usage notes:
See Chapter 1 for a complete description of each stageable site in terms of topography, histology and behaviour.
Table 41
Valid AJCC clinical M by stageable site
MX |
MX |
MX |
M0 |
M0 |
M0 |
M1 |
M1 |
M1 |
-- |
M1a |
-- |
-- |
M1b |
-- |
-- |
M1c |
-- |
99 |
99 |
99 |
Valid AJCC pathologic T by site (2003 to 2007)
Table usage notes:
See Chapter 1 for a complete description of each stageable site in terms of topography, histology and behaviour.
Table 42
Valid AJCC pathologic T by stageable site
TX |
TX |
TX |
T0 |
-- |
T0 |
Tis |
-- |
Tis |
TisDCIS |
-- |
-- |
TisLCIS |
-- |
-- |
TisPagets |
-- |
-- |
T1 |
-- |
T1 |
T1mic |
-- |
-- |
T1a |
-- |
-- |
T1b |
-- |
-- |
T1c |
-- |
-- |
T2 |
T2 |
T2 |
-- |
T2a |
-- |
-- |
T2b |
-- |
-- |
T2c |
-- |
T3 |
T3 |
T3 |
-- |
T3a |
-- |
-- |
T3b |
-- |
T4 |
T4 |
T4 |
T4a |
-- |
-- |
T4b |
-- |
-- |
T4c |
-- |
-- |
T4d |
-- |
-- |
99 |
99 |
99 |
Valid AJCC pathologic N by site (2003 to 2007)
See Chapter 1 for a complete description of each stageable site in terms of topography, histology and behaviour.
Table 43
Valid AJCC pathologic N by stageable site
NX |
NX |
NX |
N0 |
N0 |
N0 |
N0i- |
-- |
-- |
N0i+ |
-- |
-- |
N0mol- |
-- |
-- |
N0mol+ |
-- |
-- |
N1 |
N1 |
N1 |
N1mi |
-- |
-- |
N1a |
-- |
-- |
N1b |
-- |
-- |
N1c |
-- |
-- |
N2 |
-- |
N2 |
N2a |
-- |
-- |
N2b |
-- |
-- |
N3 |
-- |
-- |
N3a |
-- |
-- |
N3b |
-- |
-- |
N3c |
-- |
-- |
99 |
99 |
99 |
Valid AJCC pathologic M by site (2003 to 2007)
Table usage notes:
See Chapter 1 for a complete description of each stageable site in terms of topography, histology and behaviour.
Table 44
Valid AJCC pathologic M by stageable site
MX |
MX |
MX |
M0 |
M0 |
M0 |
M1 |
M1 |
M1 |
-- |
M1a |
-- |
-- |
M1b |
-- |
-- |
M1c |
-- |
99 |
99 |
99 |
Valid AJCC clinical TNM stage group by site (2003 to 2007)
Table usage notes:
See Chapter 1 for a complete description of each stageable site in terms of topography, histology and behaviour.
Table 45
Valid AJCC TNM clinical stage group by stageable site
X |
X |
X |
0 |
-- |
0 |
I |
I |
I |
-- |
II |
-- |
IIA |
-- |
IIA |
IIB |
-- |
IIB |
-- |
III |
-- |
IIIA |
-- |
IIIA |
IIIB |
-- |
IIIB |
IIIC |
-- |
IIIC |
IV |
IV |
IV |
99 |
99 |
99 |
Valid AJCC pathologic TNM stage group by site (2003 to 2007)
Table usage notes:
See Chapter 1 for a complete description of each stageable site in terms of topography, histology and behaviour.
Table 46
Valid AJCC TNM pathologic stage group by stageable site
X |
X |
X |
0 |
-- |
0 |
I |
I |
I |
-- |
II |
-- |
IIA |
-- |
IIA |
IIB |
-- |
IIB |
-- |
III |
-- |
IIIA |
-- |
IIIA |
IIIB |
-- |
IIIB |
IIIC |
-- |
IIIC |
IV |
IV |
IV |
99 |
99 |
99 |
Valid AJCC TNM stage group by site (2003 to 2007)
Table usage notes:
See Chapter 1 for a complete description of each stageable site in terms of topography, histology and behaviour.
Table 47
Valid AJCC TNM stage group by stageable site
0 |
-- |
0 |
I |
I |
I |
II61 |
II |
II61 |
IIA |
-- |
IIA |
IIB |
-- |
IIB |
III61 |
III |
III61 |
IIIA |
-- |
IIIA |
IIIB |
-- |
IIIB |
IIIC |
-- |
IIIC |
IV |
IV |
IV |
99 |
99 |
99 |
Valid AJCC T, N, M and stage group combination by site (2003 to 2007)
Table usage notes
- The following tables assess the validity of the T, N, M and stage group values combination. They can be used to assess either clinical or pathologicvalues.
- TNM values in the tables include all their sub-values. Thus, the expression 'T1' includes {T1, T1a, T1b, T1is...}. The actual list of included values depends on the site.
- In the context of the CCR System, the expression 'Any T' or 'Any N' include all their respective sub-values and the value '99'. Thus, the expression 'Any N' includes {99, NX, N0, N1, N1a...}
Table 48
Valid AJCC T, N, M and stage group combination for colorectal sites
Tis |
N0 |
M0 |
T1 |
N0 |
M0 |
T2 |
N0 |
M0 |
T3 |
N0 |
M0 |
T4 |
N0 |
M0 |
T1 |
N1 |
M0 |
T2 |
N1 |
M0 |
T3 |
N1 |
M0 |
T4 |
N1 |
M0 |
Any T |
N2 |
M0 |
Any T |
Any N |
M1 |
Table 49
Valid AJCC T, N, M and stage group combination for breast sites
Tis |
N0 |
M0 |
T1 |
N0 |
M0 |
T0 |
N1 |
M0 |
T1 |
N1 |
M0 |
T2 |
N0 |
M0 |
T2 |
N1 |
M0 |
T3 |
N0 |
M0 |
T0 |
N2 |
M0 |
T1 |
N2 |
M0 |
T2 |
N2 |
M0 |
T3 |
N1 |
M0 |
T3 |
N2 |
M0 |
T4 |
N0 |
M0 |
T4 |
N1 |
M0 |
T4 |
N2 |
M0 |
Any T |
N3 |
M0 |
Any T |
Any N |
M1 |
Table 50
Valid AJCC T, N, M and stage group combination for prostate sites
T1a |
N0 |
M0 |
T1a |
N0 |
M0 |
T1b |
N0 |
M0 |
T1c |
N0 |
M0 |
T2 |
N0 |
M0 |
T3 |
N0 |
M0 |
T4 |
N0 |
M0 |
Any T |
N1 |
M0 |
Any T |
Any N |
M1 |
This table has been slightly modified from the AJCC cancer staging manual, 6,th Edition since the CCR system does not consider the grade when validating the stage group and T, N, M values combination
Table
Revision (Valid AJCC T, N, M and stage group combination by site)
Year |
Description |
2008 |
Table 50: updated Stage group II with T1a, T1b and T1c |
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
The following algorithm can be used to assess the number of days or complete years between two dates. When both dates are complete, the algorithm returns the exact number of days or complete years between the two dates. When one or both dates are partial, the mean number of days or complete years between the two dates is returned. This algorithm cannot be used if one or both dates are totally unknown, i.e. equal to '99999999'. The returned value is always a positive whole number (including zero).
Definitions
Let Date1 and Date2 be the two dates from which the interval must be calculated and where Date1 <= Date2.
Let Y1, M1 and D1 be the year, month and day of date1.
Let Y2, M2 and D2 be the year, month and day of date2.
Let MOD (X, Y) be a function that returns the remainder of X divided by Y.
Let MIDDLE_DAY (Month) be a function that returns the middle day of month using the following logic:
If Month='02' Then
Return '15'
Otherwise
Return '16'
Let LAST_DAY (Year, Month) be a function that returns the last day of the month for the specified year using the following logic:
If Month='02' Then
If (MOD(Y2,4)=0 AND MOD(Y2,100)<>0) OR (MOD(Y2,4)=0 AND MOD(Y2,400)=0) Then
Return '29'
Else
Return '28'
Else If Month in ('04','06','09','11') Then
Return '30'
Else
Return '31'
Let MONTH_BETWEEN (Date1, Date2) be a function that returns the number of months between date1 and date2. If date1 is later than date2, then the result is positive. If date1 is earlier than date2, then the result is negative. If date1 and date2 are either the same days of the month or both last days of months, then the result is always a whole number. Otherwise a fractional portion of the result based on a 31-day month is also added.
Table
Algorithm (Appendix E – Interval and mean time between dates)
Based on unknown date components and existing conditions between Date1 and Date2, found the right expression to compute the number of days between Date1 and Date2 using the following table.
Evaluate the expression.
Return rounded result. |
Based on unknown date components and existing conditions between Date1 and Date2, found the right expression to compute the number complete years between Date1 and Date2 using the following table.
Evaluate the expression.
Return truncated result. |
Table
Table 51
Interval and mean time between dates calculation
None |
Y2/M2/D2 - Y1/M1/D1 |
MONTH_BETWEEN (Y2/M2/D2, Y1/M1/D1) / 12 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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
This section describes all auxiliary tables used by several processes, namely:
- Delete CCR ID;
- Alternate surname;
- Internal Record Linkage – Don't Link Cross Reference;
- Death Clearance – Don't Link Cross Reference.
Delete CCR ID
Description
This table keeps a log of patient record deletions.
Content
- CCR identification number: The CCR identification number of the deleted patient record.
- Reporting province/territory: The reporting province/territory of the deleted patient record.
- Patient identification number: The patient identification number of the deleted patient record.
- Date of deletion: The date of the day the patient record was deleted or merged with another.
- New CCR_ID: The CCR identification number of the remaining patient record when two patient records are merged through internal record linkage resolution.
- Process: Code indicating which process has deleted the patient record. Possible values are:
- Data loading process through posting step.
- Internal record linkage through resolution step.
Usage
This table can be used to know how and when a patient record has been deleted. This is especially useful when providing feedback to PTCR about an input patient record that is rejected because the corresponding base patient record is not found on the CCR.
Used By
- Data loading – posting
- Internal record linkage
Table
Revision (Delete CCR ID)
Not applicable |
Alternate surname
Description
This table keeps a copy of other patient surnames used since a patient enters the CCR.
Content
- CCR identification number: The CCR identification number of the patient.
- Surname: Former surname used by the patient.
Usage
This table is used during record linkage activities to augment the chances of a link between two records. This is useful when a patient surname changed overtime. Generally speaking, an additional patient record is created for every alternate patient surname. Doing so will allow a better link between a jurisdiction that uses the former patient surname and another jurisdiction that uses the latter patient surname.
Used By
- Data loading – posting;
- Internal record linkage – Record explosion;
- Death clearance process – Record explosion.
Table
Revision (Alternate surname)
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
Table
Internal Record Linkage – Don't Link Cross Reference
Not applicable |
Death Clearance – Don't Link Cross Reference
Description
This table keeps a log of Death Confirmation refused by PTCR through the Death Confirmation Refusal Process.
Content
- CCR Identification Number: The CCR Identification Number of the patient.
- Date of Death: The Date of Death as specified on the rejected Death Event (format: YYYYMMDD);
- Place of Death: The Place of Death as specified on the rejected Death Event;
- Death Registration Number: The Death Registration Numner as specified on the rejected Death Event
- Refusal Date: The date when the Death Confirmation Refusal has been processed (Format: YYYYMMDD)
The Year of Death, the Place of Death and the Death Registration Number altogether create a key that uniquely identifies a Death Event.
Usage
This table is used during Death Clearance process to avoid resending for review Death Clearance Confirmation that have been already reviewed and rejected by PTCR.
Used By
- Data Loading – Posting (Death Confirmation Refusal);
- Internal Record Linkage – Resolution;
- Death Clearance – Probabilistic Linkage.
Table
Revision (Death Clearance – Don't Link Cross Reference)
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. |
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
- 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.
- 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.
- 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.
- If grade is not stated in the final pathology diagnosis, use the information in the microscopic section, addendum, or comment to code grade.
- If there is no tissue diagnosis (pathology or cytology report), code the grade from the Magnetic Resonance Imaging (MRI) or Positron Emission Tomography (PET).
- 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.
- Code the grade information from the consultation or tumour board round if the specimen is sent to a specialty pathology department for a consult.
- Code the grade from the primary tumour only, never from a recurrence or metastatic site (distant and/or regional) even if this is the only reference to grade that you have.
- Code the grade for all unknown primaries to 9 (unknown grade) unless grade is implied by histology (i.e. anaplastic carcinoma (grade = 4).
- 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
- 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.
- 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):
- Bloom-Richardson (BR) scores 3-9 converted to grade
- Bloom Richardson (BR) grade (low, intermediate, high)
- Terminology
a. Differentiation (well differentiated, moderately differentiated, etc)
- Histologic grade (Breast Grade NOS, invasive cancer, histologic grade is implied).
a. Grade 1/I/i, grade 2/II/ii, grade 3/III/iii, grade 4/IV/iv
Note: The conversion of low, intermediate, and high grade for breast is different from the conversion used for all other tumours. Do not use three-grade conversion for breast primaries (see page 10).
Table
Breast Grading Conversion Table
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)
- 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
- 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)
- BR may be expressed as a grade (low, intermediate, high)
- BR grade is derived from the BR score
- 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:
- Fuhrman grade (grade 1, 2 ,3 ,4)
- Nuclear grade (grade 1, 2, 3, 4)
- Terminology (well diff, mod diff)
- Histologic grade (grade 1, grade 2)
Table
Fuhrman Conversion Table
Well differentiated |
1 |
Moderately differentiated |
2 |
Poorly differentiated |
3 |
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:
- Gleason's Grade (score or pattern)
- Terminology
a. Differentiation (well differentiated, moderately differentiated, etc.)
- Histologic grade
a. Grade 1/I/i, grade 2/II/ii, grade 3/III/iii, grade 4/IV/iv
Use the following table to convert Gleason's pattern or score into CCR codes:
Table
Gleason Conversion Table
1, 2 |
Well differentiated |
I |
1 |
3 |
Moderately differentiated |
II |
2 |
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.
- 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.
- 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.
- 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.
- 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
- 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.
- 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.
- Do not automatically code glioblastoma multiforme as grade IV, if no grade is given, code to '9' unknown. (9440/39).
- All glioma's with histology 938-946 with the exception of those with an implied grade are '9' not applicable.
- Grade astrocytomas according to ICD-O-3 rules. Do not use the WHO grade to code this field.
Lymphoma and Leukemia 9590-9989
- 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.
- Do not use the terms "high grade," "low grade," and "intermediate grade" to code differentiation or Cell Indicator field. These terms refer to prognosis, not grade.
a. In some instances, the term 'grade' does not imply differentiation and should not be used to code the 6th digit of the morphology code. It is important to recognize when the term "grade" refers to category and when it refers to biologic activity. When describing some diseases, pathologists use the term "grade" as a synonym for "type" or "category." Registrars recognize the term "grade" as an indicator of cell differentiation that is coded in the 6th digit of the ICD-O morphology code.
i. The grade descriptors for nodular sclerosing Hodgkin lymphoma and follicular lymphoma are actually types or categories of these diseases. The 6th digit should not be coded as grade 1, 2 or 3 for these cases.
ii. Poorly differentiated lymphocytic lymphoma or a B-cell or T-cell lymphoma should be coded in the 6th digit of the morphology code.
iii. Other terms described as high grade or low grade as part of the diagnostic term may be used to code the 6th digit of the morphology code.
- Do not code the descriptions "Grade 1," "Grade 2," or "Grade 3" in the Grade, Differentiation or Cell Indicator field.
- Codes 9950-9989 rarely have a grade associated with them and are generally coded as a '9'.
- Grade codes 5-8 are T-cell, B-cell, or NK cell indicators used for leukemias and lymphomas only. Therefore, codes 5-8 may only be used with morphologies in the range of 9590-9989.
Sarcoma
Several grading systems exist and may be used to grade sarcomas. The following table incorporates two, three and four-tier grading systems. If a sarcoma is graded using terminology, refer to the Terminology Conversion Table on page 11.
Table
Gleason Conversion Table
1/2 1/3 1/4 2/4 |
2 |
2/3 |
3 |
2/2 3/3 3/4 4/4 |
4 |
Common Grading Systems
Two-Grade System
There are some cancers for which a two-grade system is used (i.e. colon cancer, papillary transitional cell carcinoma, bladder, endometrial stromal sarcoma). The patterns of cell growth are measured on a scale of 1 or 2 (also referred to as low and high grade). The expected outcome is more favorable for lower grades.
- If the grade is listed as 1/2 or as low grade, assign code 2.
- If the grade is listed as 2/2 or as high grade, assign code 4.
Table
Two-Grade Conversion Table
Low grade |
2 |
High grade |
4 |
Three-Grade System
There are several cancers for which a three-grade system is used (for example peritoneum, endometrium, fallopian tube, prostate, bladder and soft tissue sarcoma). The patterns of cell growth are measured on a scale of 1, 2, and 3 (also referred to as low, medium/intermediate, and high grade). This system measures the proportion of cancer cells that are growing and making new cells and how closely they resemble the cells of the host tissue. Thus, it is similar to a four-grade system (see Terminology Conversion Table on page 10), but simply divides the spectrum into 3 rather than 4 categories (see Three-Grade Conversion Table below). The expected outcome is more favorable for lower grades.
- If the grade is listed as1/3 or as low grade, assign code 2.
- If the grade is listed as 2/3 or as medium/intermediate grade, assign code 3.
- If the grade is listed as 3/3 or as high grade, assign code 4.
Use the following table to convert the grade to CCR codes:
Table
Three-Grade Conversion Table*
Grade |
Differentiation /
Description |
CCR Code |
1/3, I/III |
Low grade |
2 |
2/3, II/III |
Medium/Intermediate grade |
3 |
3/3, III/III |
High grade |
4 |
*Do not use for breast primaries
Terminology Conversion Table
This system measures the proportion of cancer cells that are growing and making new cells and how closely they resemble the cells of the host tissue. The expected outcome is more favorable for lower grades.
Table
Terminology Conversion Table
I |
1 |
I |
1 |
II |
2 |
II |
2 |
I-II |
2 |
II |
2 |
II |
2 |
II |
2 |
II |
2 |
I-II |
2 |
II |
2 |
II-III |
3 |
III |
3 |
III |
3 |
III |
3 |
III |
3 |
III |
3 |
III |
3 |
III |
3 |
III-IV |
4 |
IV |
4 |
9 |
References:
- 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.
- International Classification of Diseases for Oncology, Third Edition. WHO.
- NAACCR Edit Logic Report for Metafile NAACR10E.EMF
- Centers for Disease Control and Prevention. Data collection of primary central nervous system tumors. National Program of Cancer Registries Training Materials. Atlanta, Georgia: Department of Health and Human Services, Centers for Disease Control and Prevention, 2004.
Table
Revision (Terminology Conversion Table)
New appendix |
Effective for January 1, 2001 data and forward
The Data Quality Management Committee, with the approval of the CCR, recommends that the SEER Program list4 of ambiguous terms be adopted as the Canadian list when identifying cancer cases5. Where possible, it is best to obtain additional information or consult with a pathologist for clarification. If neither is possible, use the following list for determining whether to register/report a cancer case to the CCR.
Table
Appendix H – CCR Ambiguous Terms
apparent(ly) |
cannot be ruled out |
appears to |
equivocal |
comparable with |
possible |
compatible with |
potentially malignant |
consistent with |
questionable |
favor(s) |
rule out |
malignant appearing |
suggests |
most likely |
worrisome |
presumed |
|
probable |
|
suspect(ed) |
|
suspicious (for) |
|
typical of |
* without additional information |
Exception:
If cytology is reported as "suspicious", do not
interpret this as a diagnosis of cancer.
Abstract the case only if a positive biopsy
or a physician's clinical impression of cancer supports the cytology findings. |
Do not include patients who have a diagnosis consisting only of these terms. |
Table
Revision (Appendix H – CCR Ambiguous Terms)
New appendix |
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:
- 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.
- 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:
- If FB is not returned from facility/physician, the information from the DCN may be used and the case considered a DCO.
- 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.
- Follow standard coding conventions for site/histology.
- There may be more than one primary noted on the Death Certificate. More than one DCO abstract may be required.
- 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.
- Code the Primary Site recorded on the Death Certificate, i.e., lung, prostate, breast.
- Melanoma, unknown primary site code to Malignant melanoma of skin, site unspecified (ICD-9 172.9, ICD-10 C43.9).
- Lymphoma, unknown primary site code to Lymph Nodes, NOS (ICD-9 202.8, ICD-10 C85.9).
- Leukemia is always coded to Bone Marrow (ICD-9 208.9, ICD-10 C95.9).
- Watch for primary sites where metastases are common (Lung, Liver, Brain and Bone).
- 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).
- Stage is always "unknown".
- Diagnostic confirmation is always "unknown".
- No treatment is recorded, even if noted on the DCN.
- Include DCO cases in edits.
(Cover letter to Institution)
PTCR
Inside address
To Whom It May Concern
The Registry Name is presently completing the Death Certificate Only (DCO) follow back process for year/s. DCO means that the only source of information about the case was a death certificate. The death certificate identified the decedent as having expired in your facility however the cancer registry has no prior information on this case through its routine data collection. Data collection is legislated by act/privacy act. Enclosed you will find a Registry Form letter for completion, it is important that we collect the initial date and address at time of diagnosis. If, your records do not identify this patient as having cancer please indicate and we will adjust our records accordingly.
By completing the enclosed Registry Form letter we can finalize the information on this patient. Complete information permits the calculation of survival rates on patients diagnosed with cancer, facilitates epidemiological studies and improves the completeness and quality of reported death and other demographic information. Your continued support in improving the quality of data allows us to participate in provincial and national studies and to provide accurate statistics on an ongoing basis to our stakeholders.
If there are any questions or concerns, please do not hesitate to contact me, contact name at facility name and phone number.
Sincerely yours,
Signature
Enclosure
(Cover letter to Informant)
PTCR
Inside address
Dear Insert name here,
The Registry Name is presently completing the Death Certificate Only (DCO) follow back process for year/s. DCO means that the only source of information about the case was a death certificate. The death certificate stated the decedent had cancer, however the cancer registry has no prior information on this case through its routine data collection. Data collection is legislated by act/privacy act. The death certificate identifies you as the last attending physician at time of death for patient name. Enclosed you will find a Registry Form letter for completion, it is important that we collect the initial date and address at time of diagnosis. If, your records do not identify this patient as having cancer please indicate and we will adjust our records accordingly.
By completing the enclosed Registry Form letter we can finalize the information on this patient. Complete information permits the calculation of survival rates on patients diagnosed with cancer, facilitates epidemiological studies and improves the completeness and quality of reported death and other demographic information. Your continued support in improving the quality of data allows us to participate in provincial and national studies and to provide accurate statistics on an ongoing basis to our stakeholders.
If there are any questions or concerns, please do not hesitate to contact me, contact name at facility name and phone number.
Sincerely yours,
Signature
Enclosure
Table
Death Certificate Notification (DCN)
New appendix |
The following algorithm can be used to assess the number of days between two dates. When both dates are complete, the algorithm returns the exact number of days. When one or both dates are partial, the missing parts of the dates are "derived" and the number of days returned, based on the derived dates. This algorithm cannot be used if one or more dates is totally unknown, i.e. equal to '99999999'. The returned value is always a positive whole number (including zero).
Definitions
Let Date1 and Date2 be the two dates for which the interval must be calculated and where Date1 <= Date2.
Let Y1, M1 and D1 be the year, month and day of date1.
Let Y2, M2 and D2 be the year, month and day of date2.
Let DIFF_DAYS (Date1, Date2) be a function that returns the number of days between date1 and date2.
Table
Assumptions if there are partial dates
If MONTH is not reported then MONTH is assumed to be '01'.
If DAY is not reported then DAY is assumed to be '01'. |
If MONTH is not reported then MONTH is assumed to be '12'.
If DAY is not reported then DAY is assumed to be the last day of the reported MONTH (28, 29, 30 or 31). |
Examples
Date1 = 20060627.
Date2 = 20060930.
DIFF_DAYS (20060627, 20060930)
Date1 = 20060699
Date2 = 20070999.
DIFF_DAYS = (20060601, 20070930)
Date1 = 20069999
Date2 = 20079999
DIFF_DAYS = (200601, 20071231)
Table
Appendix J – Interval between two dates (complete or partial)
New appendix |
Definition: If a value is an exceptional value (NULL-value), this specifies in what way and why proper information is missing.
NI |
no information |
No information whatsoever can be inferred from this exceptional value. This is the most general exceptional value. It is also the default exceptional value. It is unknown whether this event occurred (for example, radiation treatment). |
NA |
not applicable |
No proper value is applicable in this context (for example, last menstrual period for a male). |
UNK |
unknown |
A proper value is applicable but not known. This event occurred, but the date is unknown (for example, birth date). |
NASK |
not asked |
This information has not been sought (for example, patient was not asked). |
ASKU |
asked but
unknown |
Information was sought but not found (for example, patient was asked but did not know). |
NAV |
temporarily
unavailable |
Information is not available at this time, but it is expected that it will be available later. |
OTH* |
other* |
The actual value is not an element in the value domain of a variable (for example, concept not provided by required code system). |
PINF |
positive infinity |
Positive infinity of numbers. |
NINF |
negative infinity |
Negative infinity of numbers. |
MSK |
masked |
Information on this item is available, but it has not been provided by the sender due to security, privacy, or other reasons. An alternate mechanism for gaining access to this information may be available. Note: Using this null flavor does provide information that may be a breach of confidentiality. Its primary purpose is for those circumstances where it is necessary to inform the receiver that the information does exist. |
NP |
not present |
Value is not present in a message. This is only defined in messages, never in application data! All values not present in the message must be replaced by the applicable default or No-Information (NI) as the default of all defaults. |
The null flavors are a general domain extension of all normal data types. Note the distinction between value domain of any data type and the vocabulary domain of coded data types. A vocabulary domain is a value domain for coded values, but not all value domains are vocabulary domains.
* The null flavor Other is used whenever the actual value is not in the required value domain. This may be, for example, when the value exceeds some constraints that are defined too restrictively (for example, age < 100 years).
Note: Null flavors are applicable to any property of a data value or a higher-level object attribute. Where the difference of null flavors is not significant, ITs are not required to represent them. If nothing else is noted in this specification, ITs need not represent general NULL flavors for data-value property.
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.
- Residence (one residence). The dwelling in Canada where a person lives most of the time.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
The last digit of the CCR_ID is a check digit, for example, digit calculated from the other CCR_ID digits. The purpose of using a check digit is twofold: it allows the detection of some data corruption and prevents one from creating new IDs too easily. The next routine returns a check digit for a given CCR_ID.
Pseudo code
Let N1 be the first digit of CCR_ID (starting from the left)
Let N2 be the second digit of CCR_ID (starting from the left)
Let N8 be the eighth digit of CCR_ID (starting from the left)
Change the values of N2, N4, N6, N8 according to the following pattern
Initial value |
0 |
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
9 |
New value |
0 |
2 |
4 |
6 |
8 |
1 |
3 |
5 |
7 |
9 |
Let REMAINDER be the remainder of ((N1 + N2 + N3 + N4 + N5 + N6 + N7 + N8) / 10)
If REMAINDER = 0 then
RETURN 0
Else
RETURN (10 – REMAINDER)
Used by
- Data loading – Edit
- Data loading – posting
Collaborative Staging Task Force of the American Joint Committee on Cancer. Collaborative Staging Manual and Coding Instructions, Version 01.04.01. Jointly published by American Joint Committee on Cancer (Chicago, IL) and U.S. Department of Health and Human Services (Bethesda, MD), 2004. NIH Publication Number 04-5496.
http://www.cancerstaging.org/cstage/index.html
Fritz A, Percy C, Jack A, et al (eds): ICD-O: International Classification of Diseases for Oncology, Third Edition. Geneva, World Health Organization, 2000.
SEER Program Coding and Staging Manual 2004, Surveillance, Epidemiology and End Results (SEER) Program, National Cancer Institute, National Institutes of Health, Bethesda, MD. NIH Publication Number 04-5581.
SEER Program Coding and Staging Manual 2007, Surveillance, Epidemiology and End Results (SEER) Program, National Cancer Institute, National Institutes of Health, Bethesda, MD. NIH Publication Number 07-5581.
Johnson CH, Peace S, Adamo P, Fritz A, Percy-Laurry A, Edwards BK. The 2007 Multiple Primary and Histology Coding Rules. National Cancer Institute, Surveillance, Epidemiology and End Results Program. Bethesda, MD, 2007. Revised April 30, 2008
NAACCR Standards for Cancer Registries, Volume II Version 11.3 - Data Standards and Data Dictionary, Thirteenth Edition.
National Cancer Institute Surveillance Epidemiology and End Results training website, American Joint Committee on Cancer. http://www.training.seer.cancer.gov/
module_staging_cancer/unit03_sec03_part00_ajcc.html
CCR Committee on Data and Quality Management - Clinical Core Data Set - March 2001 version
AJCC Cancer Staging Manual, 6th Edition, American Joint Committee on Cancer (AJCC), 2002
Facility Oncology Registry Data Standards (FORDS), revised for 2007. Published by the American College of Surgeons (ACoS) and the Commission on Cancer (COC), 2007.
Facility Oncology Registry Data Standards (FORDS) manual, revised for 2009. Published by the American College of Surgeons (ACoS) and the Commission on Cancer (COC), 2009.
1.The original set of ISO codes has been expanded to include individual Canadian provinces and territories and other Statistics Canada specific codes.
2. Available upon request.
3.The only source of information about the case was a death certificate. This category includes deaths where either the underlying cause of death (patient record, Field No.17) is cancer, or there is any mention of cancer on the death certificate.
4. Input records that passed successfully through all validation edits, correlation edits and other match edits.
5. Because CS and AJCC TNM data items are fairly new to CCR, it has been temporarily decided that CS and AJCC TNM errors (including fatal errors)will not prevent valid core data items from being loaded on the CCR database
6. See Appendix A – Core reference tables - ICD-9 to ICD-O-2 conversion table for details.
7. See P1 Specific values & meaning.
8. See Appendix X - CCR_ID check digit routine.
9. See P4 Specific values & meaning.
10. See P5 Specific values & meaning.
11. See P10 Specific values & meaning.
12. See Appendix A (Part III - CCR System Guide) – Core reference tables.
13. See Appendix A (Part III - CCR System Guide) – Core reference tables.
14. See P18 Specific values & meaning.
15. See T1 Specific values & meaning.
16. See Appendix X – CCR_ID check digit routine.
17. See T5 Specific values & meaning.
18. See T11 Specific values & meaning.
19. See T13 Specific values & meaning.
20. See T14 Specific values & meaning.
21. See T17 Specific values & meaning.
22. See T19 Specific values & meaning.
23. Eligible ICD-O-3 histology codes do not include '0000' since this value should have been converted to a more meaningful value during the Pre-edit processing.
24. See T22 Specific values & meaning.
25. See T23 Specific values & meaning.
26. See T24 Specific values & meaning.
27.See T25 Specific values & meaning.
28. See section 1.1.2.2 – CCR collaborative staging scope.
29. See section 1.1.2.3 – CCR AJCC TNM staging scope.
30. See Appendix C – AJCC TNM concordance tables - Valid AJCC clinical T by site.
31. See Appendix C – AJCC TNM concordance tables - Valid AJCC clinical N by site.
32. See Appendix C – AJCC TNM concordance tables – Valid AJCC clinical M by site.
33. See Appendix C – AJCC TNM concordance tables – Valid AJCC pathologic T by site.
34. See Appendix C – AJCC TNM concordance tables – Valid AJCC pathologic N by site.
35. See Appendix C – AJCC TNM concordance tables – Valid AJCC pathologic M by site.
36. See Appendix C – AJCC TNM concordance tables – Valid AJCC TNM clinical stage group by site.
37. See Appendix C – AJCC TNM concordance tables – Valid AJCC TNM staging group by site.
38. See T51 Specific values & meaning.
39. Collaborative staging data items (T27-T41) and AJCC TNM staging data items (T42-T51) may or may not be reported. See TCOR-18 and TCOR-19 respectively for more details.
40. Already enforced by TVAL15.
41. Impossible to enforce since the code that stands for 'Not Reported' also stands for 'Benign behaviour'.
42. Already enforced by TVAL21.
43. See Appendix A (Part III - CCR System Guide) – Core reference tables – ICD-9 to ICD-O-2 conversion table.
44.See Appendix A (Part III - CCR System Guide) – Core reference tables – ICD-O-2 to ICD-O-3 conversion table.
45. See Appendix A (Part III - CCR System Guide) – Core reference tables – CCR core scope.
46. See Appendix A (Part III - CCR System Guide) – Core reference tables – Invalid site and histology combinations.
47. See Appendix A (Part III - CCR System Guide) – Core reference tables – Invalid histology and behaviour combinations.
48. See collaborative staging scope in Chapter 1.
49.See Appendix C – AJCC TNM concordance tables – Valid AJCC T, N, M and stage group combination bysite.
50. Thus, unknown or not assessed AJCC clinical/pathologic T, N, M values are excluded.
51. All related patient and tumour records are rejected, but corresponding message is only attached to each conflicting patient record of the family.
52. All related patient and tumour records are rejected, but corresponding message is only attached to each conflicting tumour record of the family.
53. All related patient and tumour records are rejected, but corresponding message is only attached to each erroneous or conflicting patient record of the family.
54. The match with a delete patient transaction is covered by KIM4.
55. All related patient and tumour records are rejected, but corresponding message is only attached to each erroneous or conflicting tumour record of the family.
56. Input record that has neither core fatal errors nor core errors from all previous edits.
57. Method of diagnosis can be 'Autopsy' even when date of diagnosis is before date of death. This is possible since method of diagnosis is not linked to date of diagnosis. See corresponding definitions for more detail.
58. According to cancer staging manual, 6th edition, this value is not a valid stage group for the site.
59. Place holder to keep sub-edit numbering in accordance with the required processing order. See Data Item match edits introduction for more information.
60. Based on the underlying cause of death coding rules, these 2 codes cannot be used.
61. According to cancer staging manual, 6th edition, this value is not a valid stage group for the site. On the other hand, since AJCC TNM stage group is likely to be assigned by a physician rather than derived from any T, N and M values, this value must be accepted.
62. Lymphoma, leukemia or immunoproliferative disease is identified by the following ICD-0-3 codes: 9590-9989 excluding 9731, 9734, 9740, 9750, 9755-9758, 9930.
63. Alphabetic comparison as opposed to numeric comparison is used because TTRN and Health Insurance Number may contain letters.