Skip to content Skip to navigation
National Cancer Data Base - Data Dictionary PUF 2013

Collaborative Stage Data Collection System

CS Mets Eval

PUF Data Item Name: 
CS_METS_EVAL
NAACCR Item #: 
2860
length: 
1
text: 
Site-specific
Description: 
Records how the code for CS Mets at DX was determined based on the diagnostic methods employed.
Analytic Note: 

CS Mets Eval is part of the Collaborative Stage Data Collection System (CS), and was implemented in 2004.  It describes whether the staging basis for CS Mets at Dx was clinical or pathologic, and whether any systemic treatment was given prior to that code assignment.
 
Some detective work is required to interpret codes in CS Mets Eval.  The codes may differ by type of cancer and by the version of CS in which the case was coded.  In the PUF, CS fields are retained in the form in which they are submitted.  That means that it will be necessary to identify the CS Version Numbers that are used in the PUF file, and use those to identify whether the contents of the CS Mets Eval field may have changed over time.  Links to the site-specific codes can be found at http://ncdbpuf.facs.org/?q=node/370.

CS Site Specific Factors 1-25

PUF Data Item Name: 
CS_SITESPECIFIC_FACTOR_1 through CS_SITESPECIFIC_FACTOR_25
NAACCR Item #: 
2861- 2880, 2890, 2900, 2910, 2920, 2930
length: 
3
Allowable values: 
000-999
text: 
Site-specific
Description: 
The CS Site Specific Factors are part of the Collaborative Stage Data Collection System, which was implemented in 2004 and expanded in 2010. CS Site Specific Factors 1-24, when used for a particular site, contain information that is used to assign AJCC 6th and/or 7th edition T, N, M and stage group, or prognostic information identified in the AJCC Cancer Staging Manual, 7th edition. CS Site Specific Factor 25 is used to distinguish between or among staging schema when site and histology codes are not sufficient, for consistency with the AJCC 7th edition for the following: Nasopharynx/ Pharyngeal Tonsil; Esophagus GE Junction / Stomach; Bile Ducts Distal / Bile Ducts Perihilar / Cystic Duct; Peritoneum / Peritoneum Female Genital; Melanoma Ciliary Body / Melanoma Iris; Lacrimal Gland / Lacrimal Sac.
Analytic Note: 

Using the Site Specific Factors from the Collaborative Stage Data Collection System
 
Several PUF projects will examine one or more laboratory prognostic indicators.  These are available as Site Specific Factors (SSF) collected as part of the Collaborative Stage Data Collection System (CS).  The term “collaborative” means that the data collection tool was devised to meet the various needs of cancer registry data standard setters such as the Commission on Cancer (CoC), Surveillance Epidemiology and End Results (SEER), and the National Program of Cancer Registries (NPCR). 
 
Up to 25 data fields are used to collect SSFs.  Being site specific, they contain different information depending on the type of cancer in the report.  For example, for breast cancer reports SSF1 contains “Estrogen Receptor (ER) Assay” results, but for colon cancer reports SSF1 contains “Carcinoembryonic Antigen (CEA)” results. 
 
SSFs also may convey non-laboratory site specific information that is relevant to prognosis for some cases.  For example, SSF1 for gastric cancers is “Clinical Assessment of Regional Lymph Nodes”, and for melanoma of skin it is “Measured Thickness (Depth), Breslow Measurement”.
 
Some detective work is required to identify the data fields of interest, the applicable codes, and the adequacy of the data for the particular study. 
 
            The codes, and occasionally the fields used, for a particular prognostic factor changed over time.  In the PUF the SSF data are retained in the form in which they were submitted.  That means that it will be necessary to identify the CS Version Numbers that are used in the PUF file, and use those to identify whether the data contents for the desired SSF may have changed or moved over time.  Links to the site-specific codes can be found at http://ncdbpuf.facs.org/?q=node/370.  
 
 
The quality of the SSF data items has undergone minimal review by NCDB, and PUF users are advised to examine the data consistency and completeness of these items carefully before proceeding with the study. 
 
1.       All SSF data items are edited for validity and internal consistency before the case report is submitted, and the submitter is required to correct any edit errors.  However, some coding errors remain. 
 
2.      Case coverage of the SSFs is limited for a variety of reasons, potentially seriously affecting their applicability for some studies.
                                      a.   The availability of the measures to hospital registrars at the time of data entry is sparse for many prognostic measures.  The source of information is usually the laboratory report as it appears in the hospital patient record.  The information may not be available in the hospital if it was requested by a physician and the report was sent to the physician’s office.  Or it may be delayed and not picked up later.
                                      b.   The individual tests are not run at all locations or for all patients, even if the test is part of an acknowledged treatment protocol. 
                                      c.   Finally, many hospital registries began abstracting data for the years the measures were introduced prior to the hospital’s upgrade of the software necessary to collect those items, and they did not necessarily return to the cases to abstract the missed data.  No SSFs are available for cases diagnosed prior to 2004.  Some of the items were first introduced in 2004, and are underrepresented for cases diagnosed that year compared to later years.  Most prognostic SSFs were introduced in 2010, and are certainly underrepresented for 2010 diagnoses; they are not available at all for earlier years.
 
The SSFs in use in for Versions 2.02 through the current version and whether the field was required for CoC registries are described in http://seer.cancer.gov/csreqstatus/index.html.   To access the list of Site-Specific Factors required by the Commission on Cancer, click the "Get Started" button in the Collaborate Stage Requirements Status box on the right-hand side of the page. Then, press the plus sign in the middle of the page, select "Required Factors" as Report, "CoC" as the Standard Setter, and the applicable version under Version. As noted above, the fields in which these items were stored and the codes used may have changed over time.
 
 
Please direct questions about the use of SSFs to NCDB_PUF@facs.org

CS Mets at DX-Lung

PUF Data Item Name: 
CS_METS_DX_LUNG
NAACCR Item #: 
2854
length: 
1
format: 
String
Allowable values: 
0, 1, 8, 9
Description: 
Identifies the presence of distant metastatic involvement of the lung at the time of diagnosis.
Registry Coding Instructions: 

Code information about lung metastases only (discontinuous or distant metastases to the lung) identified at the time of diagnosis.  This field should not be coded for pleural or pleural fluid involvement.
 
Lung involvement may be single or multiple.
 
Information about lung involvement may be clinical or pathologic.
 
Code this field whether or not the patient had any preoperative systemic therapy.
 
This field should be coded for all solid tumors, Kaposi sarcoma, Unknown Primary Site, and Other and Ill-Defined Primary Sites.
 
Use code 8 for Hematopoietic, Reticuloendothelial, Immunoproliferative and Myeloproliferative Neoplasms, and Hodgkin and non-Hodgkin Lymphoma.
 
Use code 9 when it cannot be determined from the medical record whether the patient specifically had lung metastases; for example, when CS Mets at Dx is coded as carcinomatosis but the lung is not specifically mentioned as a meatastatic site.  Also use code 9 when it is not known whether the patient had any distant metastases.

NCDB System Code Assignments: 

0 = None; no lung metastases
1 = Yes
8 = Not applicable
9 =Unknown whether the lung is involved; Not documented in patient record

Analytic Note: 

This item was first collected in 2010.  Because of delays in some hospitals in implementing registry software updates, data may be incomplete for 2010.

Links to the site-specific codes can be found at http://ncdbpuf.facs.org/?q=node/370.

CS Mets at DX-Liver

PUF Data Item Name: 
CS_METS_DX_LIVER
NAACCR Item #: 
2853
length: 
1
format: 
String
Allowable values: 
0, 1, 8, 9
Description: 
Identifies the presence of distant metastatic involvement of the liver at the time of diagnosis.
Registry Coding Instructions: 

Code information about liver metastases only (discontinuous or distant metastases to the liver) identified at the time of diagnosis.
 
Liver involvement may be single or multiple.
 
Information about liver involvement may be clinical or pathologic.
 
Code this field whether or not the patient had any preoperative systemic therapy.
 
This field should be coded for all solid tumors, Kaposi sarcoma, Unknown Primary Site, and Other and Ill-Defined Sites.
 
Use code 8 for Hematopoietic, Reticuloendothelial, Immunoproliferative and Myeloproliferative Neoplasms, and Hodgkin and non-Hodgkin Lymphoma.
 
Use code 9 when it cannot be determined from the medical record whether the patient had liver metastases; for example, when CS Mets at DX is coded as carcinomatosis but the liver is nto specifically mentioned as a metastatic site.  Also use code 9 when it is not known whehtehr the patient had any distant metastases.

NCDB System Code Assignments: 

0 = None; no liver metastases
1 = Yes
8 = Not applicable
9 = Unknown whether the liver is involved; Not documented in patient record.

Analytic Note: 

This item was first collected in 2010.  Because of delays in some hospitals in implementing registry software updates, data may be incomplete for 2010 diagnoses.

Links to the site-specific codes can be found at http://ncdbpuf.facs.org/?q=node/370.

CS Mets at DX-Brain

PUF Data Item Name: 
CS_METS_DX_BRAIN
NAACCR Item #: 
2852
length: 
1
Allowable values: 
0, 1, 8, 9
Description: 
Identifies the presence of distant metastatic involvement of the brain at the time of diagnosis.
Registry Coding Instructions: 

Code information about brain metastases only (discontinuous or distant metastases to brain) known at the time of diagnosis.  This field should not be coded for involvement of the spinal cord or other parts of the central nervous system.
 
Brain involvement may be single or multiple.
 
Information about brain involvement may be clinical or pathologic.
 
Code this fields whether or not the patient had any preoperative systemic therapy.
 
This field should be coded for all solid tumors, Kaposi sarcoma, Unknown Primary Site, and Other and Ill-Defined Primary Sites.
 
Use code 8 for Hematopoietic, Reticuloendothelial, Immunoproliferative aned Myeloproliferative Neoplasms, and Hodgkin and non-Hodgkin Lymphoma.
 
Use code 9 when it cannot be determined from the medical record whether the patient specifically had brain metastases; for example, when CS Mets at DX is coded as carcinomatosis but the brain is not specifically mentioned as a metastatic site.  Also use code 9 when it is not known whether the patient had any distant metastases.

NCDB System Code Assignments: 

0 = None; no brain metastases
1 = Yes
8 = Not applicable
9 = Unknown whether the brain is involved; Not documented in patient record

Analytic Note: 

This item was first collected in 2010.  Because of delays in some hospitals in implementing registry software updates, data may be incomplete for 2010 diagnoses.

Links to the site-specific codes can be found at http://ncdbpuf.facs.org/?q=node/370.

CS Mets at DX-Bone

PUF Data Item Name: 
CS_METS_DX_BONE
NAACCR Item #: 
2851
length: 
1
Allowable values: 
0, 1, 8, 9
Description: 
Identifies the presence of distant metastatic involvement of bone at the time of diagnosis.
Registry Coding Instructions: 

Code information about bone metastases only (discontinuous or distant metastases to bone) identified at the time of diangosis.  This field should not be coded for bone marrow involvement.
 
Bone involvement may be single or multiple.
 
Information about bone involvement may be clinical or pathologic.
 
Code this field whether or not the patient had any preoperative systemic therapy.
 
This field should be coded for all solid tumors, Kaposi sarcoma, Unknown Primary Site, and Other and Ill-Defined Sites.
 
Use code 8 for Hematopoietic, reticuloendothelial, Immunopolifereative and Myeloproliferative Neoplasms, and Hodgkin and non-Hodgkin Lymphoma.
 
Use code 9 when it cannot be determined from the medical record whether the patient specifically had bone metastases; for example, when CS Mets at DX is coded as carcinomatosis but bone is not specifically mentioned as a metastatic site.  Also use code 9 when it is not known whether the patient had any distant metastases.

NCDB System Code Assignments: 

0 = None; no bone metastases
1 = Yes
8 = Not applicable
9 = Unknown whether bone is involved; Not documented in patient record

Analytic Note: 

This item was first collected in 2010.  Because of delays in some hospitals in implementing registry software updates, data may be incomplete for 2010 diagnoses.

Links to the site-specific codes can be found at http://ncdbpuf.facs.org/?q=node/370.

CS Mets at DX

PUF Data Item Name: 
CS_METS_AT_DX
length: 
2
text: 
Site-specific
Description: 
Identifies whether there is metastatic involvement of distant site(s) at the time of diagnosis.
Analytic Note: 

CS Mets at Dx is part of the Collaborative Stage Data Collection System (CS), and was first introduced in 2004.  It is used to derive some AJCC M values and SEER Summary Stage codes.
 
Some detective work is required to interpret codes in the CS Mets at Dx field.  The codes differ by type of cancer and by the version of CS in which the case was coded.  In the PUF, CS fields are retained in the form in which they were submitted.  That means that it will be necessary to identify the CS Version Numbers that are used in the PUF file, and use those to identify whether the contents of the CS Mets at Dx filed may have change dover time.  Links to the site-specific codes can be found at http://ncdbpuf.facs.org/?q=node/370.
 

Lymph-vascular Invasion

PUF Data Item Name: 
LYMPH_VASCULAR_INVASION
NAACCR Item #: 
1182
length: 
1
Allowable values: 
0-1, 8-9
Description: 
Indicates the presence or absence of tumor cells in lymphatic channels (not lymph nodes) or blood vessels within the primary tumor as noted microscopically by the pathologist. This data item is separate from the CS data items but is included in this manual because of its relationship to the Collaborative Stage Data Collection System. Lymph-vascular invasion is an item of interest to both pathologists and clinicians and is mentioned in many chapters of the AJCC Cancer Staging Manual, seventh edition. This field is required for mapping of T in some sites, such as testis and penis.
Registry Coding Instructions: 
  1. Code from pathology report(s).  Code the absence or presence of lymph-vascular invasion as described in the medical record.
    1. The primary sources of information about lymph-vascular invasion are the pathology check lists (synoptic reports) developed by the College of American Pathologists.  If the case does not have a checklist or synoptic report, code from the pathology report or a physician’s statement, in that order.
    2. Do not code perineural invasion in this field.  
    3. Information to code this field can be taken from any specimen from the primary tumor.  
    4. If lymph-vascular invasion is identified anywhere in the resected specimen, it should be coded as present/identified.
  2. Use of codes.
    1. Use code 0 when the pathology report indicates that there is no lymph-vascular invasion.  This includes cases of purely in situ carcinoma, which biologically have no access to lymphatic or vascular channels below the basement membrane.
    2. Use code 1 when the pathology report or a physician’s statement indicates that lymph-vascular invasion (or one of its synonyms) is present in the specimen.
    3. Use code 8 for the following primary sites: Hodgkin and Non-Hodgkin lymphoma, Leukemias, Hematopoietic and reticuloendothelial disorders, Myelodysplastic syndromes including refractory anemias and refractory cytopenias, Myeloproliferative disorders
    4. Use code 9 when
    1. there is no microscopic examination of a primary tissue specimen
    2. the primary site specimen is cytology only or a fine needle aspiration
    3. the biopsy is only a very small tissue sample
    4. it is not possible to determine whether lymph-vascular invasion is present
    5. the pathologist indicates the specimen is insufficient to determine lymph-vascular invasion
    6. lymph-vascular invasion is not mentioned in the pathology report
NCDB System Code Assignments: 

0 = Lymph-vascular invasion is not present (absent) or not identified
1 = Lymph-vascular invasion is present or identified
8 = Not applicable
9 = Unknown if lymph-vascular invasion is present, or indeterminant

Analytic Note: 

This data item was not collected for cases diagnosed prior to 2010.  Due to delays in some hospitals for implementing registry data updates, it may be incomplete for 2010 cases.

Links to the site-specific codes can be found at http://ncdbpuf.facs.org/?q=node/370.

CS TS/Ext Eval

PUF Data Item Name: 
CS_TUMOR_SIZEEXT_EVAL
NAACCR Item #: 
2820
length: 
1
text: 
Site-specific
Description: 
Records how the codes for the two items, CS Tumor Size and CS Extension were determined, based on the diagnostic methods employed.
Analytic Note: 

CS Tumor Size/Ext Eval is part of the Collaborative Stage Data Collection System (CS), and was implemented in 2004.  It is used to describe whether the staging basis for the AJCC T value is clinical or pathologic and to record whether systemic treatment was performed prior to assignment of either CS Tumor Size or CS Extension codes.
 
Some detective work is required to interpret codes in the CS Tumor Size/Ext field.  The codes differ by type of cancer and occasionally by the version of CS in which the case was coded.  In the PUF, CS fields are retained in the form in which they were submitted.  That means that it will be necessary to identify the CS Version Numbers that are used in the PUF file, and to use those to identify whether the contents of the CS Tumor Size/Ext Eval fields may have changed over time.  Links to the site-specific codes can be found at
http://ncdbpuf.facs.org/?q=node/370.

CS Extension

PUF Data Item Name: 
CS_EXTENSION
NAACCR Item #: 
2810
length: 
2
text: 
Site-specific
Description: 
Identifies contiguous growth (extension) of the primary tumor within the organ or origin or its direct extension into neighboring organs. For some sites such as ovary, discontinuous metastasis is coded in CS Extension.
Analytic Note: 

CS Extension is part of the Collaborative Stage Data Collection System (CS), and was implemented in 2004.  It is used to derive some AJCC T-values and some SEER Summary Stage codes. 
 
Some detective work is required to interpret codes in the CS Extension field.  The codes differ by type of cancer and by the version of CS in which the case was coded.  In the PUF, CS fields are retained in the form in which they were submitted.  That means that it will be necessary to identify the CS Version Numbers that are used in the PUF file, and use those to identify whether the contents of the CS Extension field may have changed over time.  Links to the site-specific codes can be found at http://ncdbpuf.facs.org/?q=node/370.  

Pages

Subscribe to Collaborative Stage Data Collection System