Version: Click here to use the Query Builder for Version 18.

Item Search:

CHAPTER X:

DATA DICTIONARY

In this chapter, data items are presented in alphabetical order by item names. For each item, a general description, specific codes and definitions are provided. For many items, the document provides a brief rationale for collecting the data item or for using the codes listed. The at-a-glance header for each data item has alternate name(s), item number, length, source of standard, year and version implemented, and column numbers (for a discussion of NAACCR’s standard naming conventions, see Chapter I). 

Differences from Version 16 are marked “Revised” or “New” following the item name. Changes are highlighted in the table or indicated by black vertical lines in the outside margins of the text portion of a data item. Text of previous versions is revealed by hovering over a highlighted cell. Revised and new items are summarized in Appendix F.

Alternate names by which the same item is called under NAACCR’s naming convention are listed alphabetically in Appendix D.

The Source of Standard designates the reference for detailed coding instructions for many of the data items. References can be found in Chapter VI. A list of reference manuals for Version 18 (and prior versions) is provided in Chapter II, Table 1. Websites for the standard setting organizations:

SEER: http://seer.cancer.gov/registrars/
CoC: http://www.facs.org/cancer/coc/storemanual.html
NPCR: http://www.cdc.gov/cancer/npcr/
CCCR: http://www23.statcan.gc.ca/imdb/p2SV.pl?Function=getSurvey&SDDS=3207&lang=en&db=imdb&adm=8&dis=2

The Collaborative Staging website serves as the main repository for CS-related items including publications, software, educational activities, etc., for cancer registrars and cancer registry software vendors: https://cancerstaging.org/cstage/Pages/default.aspx.

The date format (YYYYMMDD) specifically addresses the NAACCR standard data transmission format; not how the data should be stored in an individual registry’s database or viewed on the screen. Only valid portions of the date should be transmitted. Below are the common formats to handle the situation where only certain components of date are known.

The field is fixed-length and left-justified. Any missing component should be replaced by spaces. If there are no known date components, the fixed-length variable will be completely blank.

For unknown values and codes that have meanings other than dates the HL7 Flavors of Null Table (Appendix H) has been adopted for flagging each non-system-generated missing date as a way to eliminate the ambiguity of missing values. A date flag field, to serve as a flag or indicator, is used for each date field for which an “unknown” or “not applicable” value is appropriate. This item would be blank if a valid date is transmitted in its associated date item. The only date fields that would not have a flag are system-generated dates (e.g., Date Case Completed [2090]), for which “unknown” would never be a legitimate value.
ABSTRACTED BYRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
5703CoC756 - 758
Alternate Name:
XML NAACCR ID:abstractedBy
PARENT XML ELEMENT:Tumor
Description
An alphanumeric code assigned by the reporting facility that identifies the individual abstracting the case.
ACCESSION NUMBER--HOSPRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
5509CoC745 - 753
Alternate Name:Accession Number (CoC)
XML NAACCR ID:accessionNumberHosp
PARENT XML ELEMENT:Tumor
Description

Provides a unique identifier for the patient consisting of the year in which the patient was first seen at the reporting facility and the consecutive order in which the patient was abstracted.

The first four numbers specify the year and the last five numbers are the numeric order in which the patient was entered into the registry database. Within a registry, all primaries for an individual must have the same accession number. The first four digits must be greater than or equal to 1944.
Rationale
This data item protects the identity of the patient and allows cases to be identified on a local, state, and national level. If the central registry preserves this number, they can refer to it when communicating with the reporting facilities. It also provides a way to link computerized follow-up reports from reporting facilities into the central database.
ADDR AT DX--CITYRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
7050CoC74 - 123
Alternate Name:City or Town (pre-96 CoC)
City/Town at Diagnosis (CoC)
XML NAACCR ID:addrAtDxCity
PARENT XML ELEMENT:Tumor
Description
Name of the city in which the patient resides at the time the reportable tumor was diagnosed. If the patient resides in a rural area, record the name of the city used in the mailing address. If the patient has multiple primaries, the city of residence may be different for each primary.
Codes (in addition to valid City)
UNKNOWNCity at diagnosis unknown
ADDR AT DX--COUNTRYRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
1023NAACCR201313464 - 466
Alternate Name:
XML NAACCR ID:addrAtDxCountry
PARENT XML ELEMENT:Tumor
Description
Country code for the address of the patient's residence at the time the reportable tumor is diagnosed. If the patient has multiple tumors, the country of residence may be different for each tumor. This data item became part of the NAACCR transmission record effective with Volume II, Version 13 in order to include country and state for each geographic item and to use interoperable codes. It supplements the item Addr at Dx--State [80].
Rationale
Country of patient's residence at the time of diagnosis is an important element of the patient’s residential history profile and might be useful for understanding risk factors, assessment of patient prognosis, and chances for survival.
Codes Use the International Standards Organization (ISO) 3166-1 Country Three Character Codes, whenever possible, augmented by custom codes. See Appendix B for complete list of country names and corresponding three character alpha codes.
ZZNNorth America NOS
ZZCCentral America NOS
ZZSSouth America NOS
ZZPPacific NOS
ZZEEurope NOS
ZZFAfrica NOS
ZZAAsia NOS
ZZXNon-US NOS
ZZUUnknown
Custom codes for historic use only
XNINorth American Islands
XCBOther Caribbean Islands
XENEngland, Channel islands, Isle of Man
XSCScandinavia
XGRGermanic Countries
XSLSlavic Countries
CSKCzechoslovakia (former)
YUGYugoslavia
XUMUkraine and Moldova
XNFNorth Africa
XSDSudanese Countries
XWFWest Africa
XSFSouth Africa
XEFEast Africa
XIFAfrican Islands
XETEthiopia and Eritrea
XAPArabian Peninsula
XISIsrael and Palestine
XCRCaucasian Republics of former USSR
XOROther Asian Republics of former USSR
XSESoutheast Asia
XMSMalaysia, Singapore, Brunei
XCHChina, NOS
XMLMelanesian Islands
XMCMicronesian Islands
XPLPolynesian Islands
ADDR AT DX--NO & STREETRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
233060CoC4348 - 4407
Alternate Name:Patient Address (Number and Street) at Diagnosis (CoC)
Number and Street (pre-96 CoC)
XML NAACCR ID:addrAtDxNoStreet
PARENT XML ELEMENT:Tumor
Description
The number and street address or rural mailing address of the patient's residence at the time the reportable tumor was diagnosed. Residential street address should not include PO Boxes. For consolidated records, street address may be based on reported or corrected residential address information.
Rationale
The address is part of the patient's demographic data and has multiple uses. It can be used to evaluate referral patterns, allows for the analysis of cancer cluster concerns, and supports epidemiological studies that use area-based social measures.

Coding Instructions and Summary of USPS Guidelines.
  • This field is intended to store street address information for the patient’s physical, residential address. All efforts should be made to find the patient’s true street address and postal code, including reviewing relevant sources outside the medical record if available. A PO Box mailing address should only be recorded when no other address information is available in the medical record and no other information sources are available.
  • If the patient has multiple tumors, address at diagnosis may be different for each tumor.
  • Do not update this item if the patient’s residential address changes. Store updated address information in the affiliated current address data items. Only update based on improved information on the residential address at time of diagnosis. For instance, it is appropriate to correct an address during the geocoding or consolidation process.
  • Refer to FORDS for residency rules.
  • Additional address information such as facility, nursing home, name of apartment complex, or a PO Box used for mailing purposes, should be entered in Addr At Dx--Supplementl [2335].
  • U.S. addresses should conform to the U.S. Postal Service (USPS) Postal Addressing Standards. These standards are referenced in USPS Publication 28, Postal Addressing Standards. The current USPS Pub. 28 may be found and downloaded here: http://pe.usps.gov/cpim/ftp/pubs/Pub28/pub28.pdf.
  • The address should be fully spelled out with standardized use of abbreviations and punctuation per USPS postal addressing standards (USPS Pub. 28, available at link above). Mixed case allowed.
  • Canadian addresses should conform to the Canada Postal Guide. The current Canadian Postal Address Standards may be found here: https://www.canadapost.ca/tools/pg/manual/PGaddress-e.pdf.
  • Punctuation marks should be avoided, except when punctuation is necessary to convey the meaning. Punctuation normally is limited to periods when the period carries meaning (e.g., 39.2 RD), slashes for fractional addresses (e.g., 101 1/2 Main St), and hyphens when the hyphen carries meaning (e.g., 289-01 Montgomery Ave). Use of the pound sign (#) to designate address units should be avoided whenever possible. The preferred notation is as follows: 102 Main St Apt 101. If a pound sign is used, there must be a space between the pound sign and the secondary number (e.g., 425 Flower Blvd # 72).
  • Abbreviations should be limited to those recognized by USPS standard abbreviations, these include, but are not limited, to the list below: (A complete list of recognized street abbreviations is provided in Appendix C of USPS Pub. 28 available at link above):

APT

apartment

N

north

BLDG

building

NE

northeast

FL

floor

NW

northwest

STE

suite

S

south

UNIT

unit

SE

Southeast

RM

room

SW

southwest

DEPT

department

E

east

 

 

W

west

Codes (in addition to valid street address)
UNKNOWNPatient's address is unknown
ADDR AT DX--POSTAL CODERevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
1009CoC126 - 134
Alternate Name:Zip Code (pre-CoC)
Postal Code (CCCR)
Postal Code at Diagnosis (CoC)
XML NAACCR ID:addrAtDxPostalCode
PARENT XML ELEMENT:Tumor
Description
Identifies the postal code of the patient’s address at diagnosis. For consolidated records, postal code may be based on reported or corrected residential address information.
Rationale
The postal code is part of the patient’s demographic data and has multiple uses. It can be used to evaluate referral patterns, allows for the analysis of cancer cluster concerns, and supports epidemiological studies that use area-based social measures.
 
Instructions for Coding
  • This field is intended to store ZIP Code or other postal code for the patient's physical, residential address. The postal code for PO Box mailing address should not be entered into this data item except in the infrequent case when no other address information is available.
  • If the patient has multiple tumors, the postal code at diagnosis may be different for each tumor.
  • Do not update this item if the patient's residential address changes. Store address update information in the affiliated current address data items. Only update based on improved information on the residential address at time of diagnosis. For instance, it is appropriate to correct a ZIP Code during the geocoding or consolidation process.
  • For U.S. residents, use either the 5-digit or the extended 9-digit ZIP code. Blanks follow the 5-digit code if the 4-digit extension is not collected.
  • For Canadian residents, use the 6-character alphanumeric postal code.
  • When available, enter the postal code for other countries for out-of-country addresses.
Codes (in addition to known US and Canadian or other postal codes)
888888888Resident of country other than the United States, U.S. possessions or territories, or Canada and the postal code is unknown
999999999Resident of the United States (including its possessions, etc.) and the postal code is unknown
999999Resident of Canada and postal code is unknown
ADDR AT DX--STATERevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
802CoC201112.2124 - 125
Alternate Name:State at Diagnosis (CoC)
State (pre-96 CoC)
XML NAACCR ID:addrAtDxState
PARENT XML ELEMENT:Tumor
Description
Identifies the patient’s state or province of residence at the time of diagnosis as identified by the Reporting Source. For consolidated records, the state may be based on reported or corrected residential address information.
Rationale
The state of residence is part of the patient's demographic data and has multiple uses. It can be used to evaluate referral patterns, allows for the analysis of cancer cluster concerns, and supports epidemiological studies that use area-based social measures.
 
Instructions for Coding
  • This field is intended to store residential state for the patient's physical, residential address. The state for PO Box mailing address should not be entered into this data item except in the infrequent case when no other address information is available.
  • If the patient has multiple tumors, state at diagnosis may be different for each tumor.
  • Do not update this item if the patient's residential address changes. Store address update information in the affiliated current address data items. Only update based on improved information on the residential address at time of diagnosis. For instance, it is appropriate to correct a state during the geocoding or consolidation process.
  • Use the U.S. Postal Service abbreviation (for the state, territory, commonwealth, U.S. possession) or Canada Post abbreviation (for the Canadian province/territory) in which the patient resides at the time the reportable tumor is diagnosed.
  • If the patient is a foreign resident, then code either XX or YY depending on the circumstance.
Codes (in addition to USPS abbreviations)
CDResident of Canada, NOS (province/territory unknown)
USResident of United States, NOS (state/commonwealth/territory/possession unknown)
XXResident of country other than the United States (including its territories, commonwealths, or possessions) or Canada, and country is known
YYResident of country other than the United States (including its territories, commonwealths, or possessions) or Canada, and country is unknown
ZZResidence unknown
ADDR AT DX--SUPPLEMENTLRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
233560CoC2003104408 - 4467
Alternate Name:Patient Address (Number and Street) at Diagnosis--Supplemental (CoC)
XML NAACCR ID:addrAtDxSupplementl
PARENT XML ELEMENT:Tumor
Description
Provides the ability to store additional address information such as the name of a place or facility (for example a nursing home, apartment complex, jail or PO Box residential or other mailing address) at the time of diagnosis.
Rationale
Sometimes the registry receives the name of a facility instead of a proper street address containing the street number, name, direction, and other elements necessary to locate an address on a street file for the purpose of geocoding. By having a second street address field to hold address information, the registry can look up and store the street address and not lose the facility name due to a shortage of space.

The presence of a second street address field to hold additional address information also aids in follow-up. For instance, Addr At DX--No & Street [2330] should contain a street address only. However, it is important to retain any known PO Box information when linking for cohort studies or patient contact studies. Retaining facility name can also help correct errors in Addr At DX--No & Street [2330] or assist with geocoding or consolidation. Additionally, researchers can use this field to verify if geographic areas of high risk are driven by location of facilities, such as jails, nursing homes, or homeless shelters.
 
Instructions for Coding
  • Record the name of the place or facility (for example nursing home, apartment complex, prison/jail or group home) of the patient’s residence when the tumor was diagnosed. Do not use this item for information stored in other address items such as Addr At DX--NO & Street [2330].
  • Record a full residential PO Box here (including city & zip code) or other non-physical, residential mailing address here.
  • Record HOMELESS here when the street address used is a shelter or diagnosing facility for persons with no usual residence.
  • If the patient has multiple tumors, address at diagnosis supplemental may be different for each tumor.
  • Do not update this item if the patient’s residential address changes. Store updated address information in the affiliated current address data items. Only update based on improved information on the residential address at time of diagnosis. For instance, it is appropriate to correct supplemental address during the geocoding or consolidation process.
  • Refer to STORE for residency rules.
ADDR CURRENT--CITYRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
181050CoC2803 - 2852
Alternate Name:City/Town--Current (CoC)
XML NAACCR ID:addrCurrentCity
PARENT XML ELEMENT:Patient
Description
Name of city of the patient’s current usual residence. If the patient has multiple tumors, the current city of residence should be the same for all tumors.
Rationale
"Current address" can be used to measure the regional "cancer burden" (cost, medical care needs), especially in major retirement regions. Sometimes central registries carry out follow-up by contacting the patients by a letter or telephone calls to ascertain their vital status. The most current reported address and telephone number are needed. This information is also useful for conducting interview studies.
ADDR CURRENT--COUNTRYRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
18323NAACCR201313467 - 469
Alternate Name:
XML NAACCR ID:addrCurrentCountry
PARENT XML ELEMENT:Patient
Description
Country code for the address of patient’s current usual residence. If the patient has multiple tumors, the current country of residence should be the same for all tumors. This data item became part of the NAACCR transmission record effective with Volume II, Version 13 in order to include country and state for each geographic item and to use interoperable codes. It supplements the item Addr Current--State [1820].
Rationale
Country of patient’s current residence is an important element of the patient’s residential history profile and is useful for understanding risk factors, assessment of patient prognosis, and chances for survival.
Codes Use the International Standards Organization (ISO) 3166-1 Country Three Character Codes, whenever possible, augmented by custom codes, see below. See Appendix B for complete list of country names and corresponding three character alpha codes.
Custom codes for historic use only
ZZNNorth America NOS
ZZCCentral America NOS
ZZSSouth America NOS
ZZPPacific NOS
ZZEEurope NOS
ZZF Africa NOS
ZZAAsia NOS
ZZXNon-US NOS
ZZUUnknown
Custom codes for historic use only
XNINorth American Islands
SCBOther Caribbean Islands
XENEngland, Channel Island, Isle of Man
XSCScandinavia
XGRGermanic Countries
XSL Slavic Countries
CSKCzechoslovakia (former)
YUGYugoslavia (former)
XUMUkraine and Moldova
XNFNorth Africa
XSDSudanese Countries
XWF West Africa
XSFSouth Africa
XEFEast Africa
XIFAfrican Islands
XETEthiopia and Eritrea
XAPArabian Peninsula
XISIsrael and Palestine
XCRCaucasian Republics of former USSR
XOROther Asian Republics of former USSR
XSESoutheast Asia
XMSMalaysia, Singapore, Brunei
XCHChina, NOS
XMLMelanesian Islands
XMCMicronesian Islands
XPLPolynesian Islands
ADDR CURRENT--NO & STREETRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
235060CoC4468 - 4527
Alternate Name:Patient Address (Number and Street)-Current (CoC)
XML NAACCR ID:addrCurrentNoStreet
PARENT XML ELEMENT:Patient
Description
The number and street address or the rural mailing address of the patient’s current usual residence. This can be used to generate a follow-up inquiry, and must correspond to other fields in the current address. If the patient has multiple tumors, the current address should be the same. Additional address information such as facility, nursing home, or name of apartment complex should be entered in item Addr Current--Supplemental [2335].

U.S. addresses should conform to the USPS Postal Addressing Standards. These standards are referenced in USPS Pub. 28, July, 2008, Postal Addressing Standards. The current USPS Pub. 28 may be found and downloaded from the following website: http://pe.usps.gov/cpim/ftp/pubs/Pub28/pub28.pdf.

Canadian addresses should conform to the Canada Postal Guide. The current Canadian Postal Address standards may be found at the following website: http://www.canadapost.ca.
Rationale
“Current address” can be used to measure the regional “cancer burden” (cost, medical care needs), especially in major retirement regions. Sometimes central registries carry out follow-up by contacting the patients via letter or telephone calls to ascertain their vital status. The most current reported address and telephone number are needed. This information also is useful for conducting interview studies.

Addresses that are formatted to conform to USPS Postal Addressing Standards can be more properly geocoded by GIS software and vendors to the correct census tract. The USPS Standards also address a number of issues that are problematic in producing precise addresses, including the use of punctuation, abbreviations, and proper placement of address elements, such as street direction, apartment and suite numbers, and unusual addressing situations. Spanish-language addresses also are covered by the USPS Standard.

Coding Instructions (summary of USPS guidelines)

The address should be fully spelled out with standardized use of abbreviations and punctuation per USPS postal addressing standards (USPS Postal Addressing Standards, Pub. 28, July 2008). Upper case recommended. Mixed case allowed.

Abbreviations should be limited to those recognized by USPS standard abbreviations, these include but are not limited to (a complete list of recognized street abbreviations is provided in Appendix C of USPS Pub. 28.):

APT

apartment

N

north

BLDG

building

NE

northeast

FL

floor

NW

northwest

STE

suite

S

south

UNIT

unit

SE

Southeast

RM

room

SW

southwest

DEPT

department

E

east

 

 

W

west


Punctuation marks should be avoided, except when punctuation is necessary to convey the meaning. Punctuation normally is limited to periods when the period carries meaning (e.g., 39.2 RD), slashes for fractional addresses (e.g., 101 ½ MAIN ST), and hyphens when the hyphen carries meaning (e.g., 289-01 MONTGOMERY AVE). Use of the pound sign (#) to designate address units should be avoided whenever possible. The preferred notation is as follows: 102 MAIN ST APT 101. If a pound sign is used, there must be a space between the pound sign and the secondary number (e.g., 425 FLOWER BLVD # 72).
ADDR CURRENT--POSTAL CODERevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
18309CoC2855 - 2863
Alternate Name:Postal Code--Current (CoC)
XML NAACCR ID:addrCurrentPostalCode
PARENT XML ELEMENT:Patient
Description
Postal code for the address of the patient’s current usual residence. If the patient has multiple tumors, the postal codes should be the same. For U.S. residents, use either the 5-digit or the extended 9-digit ZIP code. Blanks follow the 5-digit code. For Canadian residents, use the 6-character alphanumeric postal code. Blanks follow the 6-character code. When available, enter postal code for other countries.
Rationale
“Current address” can be used to measure the regional “cancer burden” (cost, medical care needs), especially in major retirement regions. Sometimes central registries carry out follow-up by contacting the patients by a letter or telephone calls to ascertain their vital status. The most current reported address and telephone number are needed. This information also is useful for conducting interview studies.
Codes (in addition to U.S., Canadian, and Foreign postal codes)
999999Resident of Canada and postal code unknown
888888888Resident of country other than the United States (including its possessions, etc.) or Canada, and postal code unknown
999999999Resident of the United States (including its possessions, etc.) and postal code unknown
ADDR CURRENT--STATERevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
18202CoC2853 - 2854
Alternate Name:State--Current (CoC)
XML NAACCR ID:addrCurrentState
PARENT XML ELEMENT:Patient
Description
USPS abbreviation for the state, territory, commonwealth, U.S. possession, or CanadaPost abbreviation for the Canadian province/territory of the patient’s current usual residence. If the patient has multiple tumors, the current state of residence should be the same for all tumors. Effective with NAACCR Volume II, Version 13 a new data item, Addr Current--Country [1832] was added to the standard transmission record layout. The UDS Committee expects the new items to supplement the use of Addr Current--State [80].
Rationale
"Current address" can be used to measure the regional "cancer burden" (cost, medical care needs), especially in major retirement regions. Sometimes central registries carry out follow-up by contacting the patients via letter or telephone calls to ascertain vital status. The most current reported address and telephone number are needed. This information also is useful for conducting interview studies.
Codes (in addition to the U.S. and Canadian postal service abbreviations)
CDResident of Canada, NOS (province/territory unknown)
USResident of United States, NOS (state/commonwealth/territory/possession unknown)
XXResident of country other than the United States (including its territories, commonwealths, or possessions) or Canada, and country is known
YYResident of country other than the United States (including its territories, commonwealths, or possessions) or Canada, and country is unknown
ZZResidence unknown
ADDR CURRENT--SUPPLEMENTLRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
235560CoC2003104528 - 4587
Alternate Name:Patient Address (Number and Street) Current--Supplemental (CoC)
XML NAACCR ID:addrCurrentSupplementl
PARENT XML ELEMENT:Patient
Description
This data item provides the ability to store additional address information such as the name of a place or facility, a nursing home, or the name of an apartment complex. This can be used to generate a follow-up inquiry, and must correspond to other fields in the current address. If the patient has multiple tumors, the current address should be the same.
Rationale
Sometimes the registry receives the name of a facility instead of a proper street address containing the street number, name, direction, and other elements necessary to locate an address on a street file for the purpose of geocoding. By having a second street address field to hold address information, the registry can look up and store the street address and not lose the facility name due to a shortage of space. The presence of a second street address field to hold additional address information also aids in follow-up.
ADENOID CYSTIC BASALOID PATTERNNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
38035NAACCR1839 - 1843
Alternate Name:
XML NAACCR ID:adenoidCysticBasaloidPattern
PARENT XML ELEMENT:Tumor
Description
Adenoid Cystic Basaloid Pattern, the presence of a basaloid pattern on pathological examination, is a prognostic factor for adenoid cystic carcinoma of the lacrimal gland.
Rationale
Adenoid Cystic Basaloid Pattern is a Registry Data Collection Variable in AJCC 8. This data item was previously collected as Lacrimal Gland, CS SSF# 6.
Codes
0.0-100.00.0 to 100.0 percent basaloid pattern
XXX.5Basaloid pattern present, percentage not stated
XXX.8Not applicable: Information not collected for this case
(If this item is required by your standard setter, use of code XXX.8 will result in an edit error.)
XXX.9Not documented in medical record
Adenoid Cystic Basaloid Pattern not assessed or unknown if assessed
Each Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.
ADENOPATHYNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
38041NAACCR2018181910 - 1910
Alternate Name:RAI Classification: Adenopathy
XML NAACCR ID:adenopathy
PARENT XML ELEMENT:Tumor
Description
Adenopathy is defined as the presence of lymph nodes greater than 1.5 cm on physical examination (PE) and is part of the staging criteria for Chronic Lymphocytic Leukemia/Small Lymphocytic Lymphoma (CLL/SLL).
Rationale
Adenopathy is a prognostic factor required for staging of Chronic Lymphocytic Leukemia/Small Lymphocytic Lymphoma (CLL/SLL) in AJCC 8th edition, Chapter 79 Hodgkin and Non-Hodgkin Lymphomas. It is a new data item for cases diagnosed 1/1/2018+.
Codes
0Adenopathy not identified/not present
No lymph nodes >1.5 cm
1Adenopathy present
Presence of lymph nodes >1.5 cm
9Not documented in medical record
Adenopathy not assessed or unknown if assessed
Each Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.
AFP POST-ORCHIECTOMY LAB VALUENew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
38057NAACCR2018181959 - 1965
Alternate Name:Testis Serum Markers: AFP (Alpha Fetoprotein) Post-Orchiectomy Lab Value
XML NAACCR ID:afpPostOrchiectomyLabValue
PARENT XML ELEMENT:Tumor
Description
AFP (Alpha Fetoprotein) Post-Orchiectomy Lab Value refers to the lowest AFP value measured post-orchiectomy. AFP is a serum tumor marker that is often elevated in patients with nonseminomatous germ cell tumors of the testis. The Post-Orchiectomy lab value is used to monitor response to therapy.
Rationale
AFP (Alpha Fetoprotein) Post-Orchiectomy Lab Value is a Registry Data Collection Variable in AJCC. It was previously collected as Testis CS SSF# 12.
Codes
0.00.0 nanograms/milliliter (ng/mL)
0.1-99999.90.1–99,999.9 ng/mL
XXXXX.1100,000 ng/mL or greater
XXXXX.7Test ordered, results not in chart
XXXXX.8Not applicable: Information not collected for this case
(If this information is required by your standard setter, use of code XXXXX.8 may result in an edit error.)
XXXXX.9Not documented in medical record
No orchiectomy performed
AFP (Alpha Fetoprotein) Post-Orchiectomy Lab Value not assessed or unknown if assessed
Each Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.
AFP POST-ORCHIECTOMY RANGENew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
38061NAACCR2018181966 - 1966
Alternate Name:Testis Serum Markers: AFP (Alpha Fetoprotein) Post-Orchiectomy Range
XML NAACCR ID:afpPostOrchiectomyRange
PARENT XML ELEMENT:Tumor
Description
AFP (Alpha Fetoprotein) Post-Orchiectomy Range identifies the range category of the lowest AFP value measured post-orchiectomy. AFP is a serum tumor marker that is often elevated in patients with nonseminomatous germ cell tumors of the testis. The Post-Orchiectomy lab value is used to monitor response to therapy.
Rationale
AFP (Alpha Fetoprotein) Post-Orchiectomy Range is a Registry Data Collection Variable in AJCC. AFP (Alpha Fetoprotein) Post-Orchiectomy Range is used to assign the S Category Pathological and was previously collected as Testis CS SSF# 13.
Codes
0Within normal limits
1Above normal and less than 1,000 nanograms/milliliter (ng/mL)
21,000 -10,000 ng/mL
3Greater than 10,000 ng/mL
4Post-Orchiectomy alpha fetoprotein (AFP) stated to be elevated
7Test ordered, results not in chart
8Not applicable: Information not collected for this case
(If this information is required by your standard setter, use of code 8 may result in an edit error.)
9Not documented in medical record
No orchiectomy performed
AFP (Alpha Fetoprotein) Post-Orchiectomy Range not assessed or unknown if assessed
Each Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.
AFP PRE-ORCHIECTOMY LAB VALUENew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
38077NAACCR2018181951 - 1957
Alternate Name:Testis Serum Markers: AFP (Alpha Fetoprotein) Pre-Orchiectomy Lab Value
XML NAACCR ID:afpPreOrchiectomyLabValue
PARENT XML ELEMENT:Tumor
Description
AFP (Alpha Fetoprotein) Pre-Orchiectomy Lab Value refers to the AFP value measured prior to treatment. AFP is a tumor marker that is often elevated in patients with nonseminomatous germ cell tumors of the testis.
Rationale
AFP (Alpha Fetoprotein) Pre-Orchiectomy Lab Value is a Registry Data Collection Variable in AJCC. It was previously collected as Testis CS SSF# 6
Codes
0.00.0 nanograms/milliliter (ng/mL)
0.1-99999.90.1–99,999.9 ng/mL
XXXXX.1100,000 ng/mL or greater
XXXXX.7Test ordered, results not in chart
XXXXX.8Not applicable: Information not collected for this case
(If this information is required by your standard setter, use of code XXXXX.8 may result in an edit error.)
XXXXX.9Not documented in medical record
AFP (Alpha Fetoprotein) Pre-Orchiectomy Lab Value not assessed or unknown if assessed
Each Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.
AFP PRE-ORCHIECTOMY RANGENew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
38081NAACCR2018181958 - 1958
Alternate Name:Testis Serum Markers: AFP (Alpha Fetoprotein) Pre-Orchiectomy Range
XML NAACCR ID:afpPreOrchiectomyRange
PARENT XML ELEMENT:Tumor
Description
AFP (Alpha Fetoprotein) Pre-Orchiectomy Range identifies the range category of the highest AFP value measured prior to treatment. AFP is a serum tumor marker that is often elevated in patients with nonseminomatous germ cell tumors of the testis.
Rationale
AFP (Alpha Fetoprotein) Pre-Orchiectomy Range is a Registry Data Collection Variable in AJCC. AFP (Alpha Fetoprotein) Pre-Orchiectomy Range is used to assign the S Category Clinical and was previously collected as Testis CS SSF# 7.
Codes
0Within normal limits
1Above normal and less than 1,000 nanograms/milliliter (ng/mL)
21,000 -10,000 ng/mL
3Greater than 10,000 ng/mL
4Pre-Orchiectomy alpha fetoprotein (AFP) stated to be elevated
7Test ordered, results not in chart
8Not applicable: Information not collected for this case
(If this information is required by your standard setter, use of code 8 may result in an edit error.)
9Not documented in medical record
AFP (Alpha Fetoprotein) Pre-Orchiectomy Range not assessed or unknown if assessed
Each Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.
AFP PRETREATMENT INTERPRETATIONNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
38091NAACCR2018181844 - 1844
Alternate Name:AFP (Alpha Fetoprotein) Pretreatment Interpretation
XML NAACCR ID:afpPretreatmentInterpretation
PARENT XML ELEMENT:Tumor
Description
AFP (Alpha Fetoprotein) Pretreatment Interpretation, a nonspecific serum protein that generally is elevated in the setting of hepatocellular carcinoma (HCC), is a prognostic factor for liver cancer.
Rationale
AFP (Alpha Fetoprotein) Pretreatment Interpretation is a Registry Data Collection Variable in AJCC. This data item was previously collected for Liver, CS SSF# 1.
Codes
0Negative/normal; within normal limits
1Positive/elevated
2Borderline; undetermined if positive or negative
7Test ordered, results not in chart
8Not applicable: Information not collected for this case
(If this item is required by your standard setter, use of code 8 will result in an edit error.)
9Not documented in medical record
AFP pretreatment interpretation not assessed or unknown if assessed
Each Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.
AFP PRETREATMENT LAB VALUENew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
38106NAACCR2018181845 - 1850
Alternate Name:AFP (Alpha Fetoprotein) Pretreatment Lab Value
XML NAACCR ID:afpPretreatmentLabValue
PARENT XML ELEMENT:Tumor
Description
AFP (Alpha Fetoprotein) Pretreatment Lab Value is a nonspecific serum protein that generally is elevated in the setting of hepatocellular carcinoma (HCC). This data item pertains to the pre-treatment lab value.
Rationale
AFP (Alpha Fetoprotein) Pretreatment Lab Value is a Registry Data Collection Variable in AJCC. This data item was previously collected for Liver, CS SSF# 3.
Codes
0.00.0 nanograms/milliliter (ng/ml); not detected
0.1-9999.90.1-9999.9 ng/ml
(Exact value to nearest tenth of ng/ml)
XXXX.110,000.0 ng/ml or greater
XXXX.7Test ordered, results not in chart
XXXX.8Not applicable: Information not collected for this case
(If this item is required by your standard setter, use of code XXXX.8 will result in an edit error.)
XXXX.9Not documented in medical record
AFP (Alpha Fetoprotein) Pretreatment Lab Value not assessed or unknown if assessed
Each Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.
AGE AT DIAGNOSISRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
2303SEER/CoC223 - 225
Alternate Name:
XML NAACCR ID:ageAtDiagnosis
PARENT XML ELEMENT:Tumor
Description
Age of the patient at diagnosis in complete years. Different tumors for the same patient may have different values.
Codes
000Less than 1 year old; diagnosed in utero
0011 year old, but less than 2 years
0022 years old
...
101101 years old
...
120120 years old
999Unknown age
AJCC IDNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
9954NAACCR2018181722 - 1725
Alternate Name:
XML NAACCR ID:ajccId
PARENT XML ELEMENT:Tumor
Description
The values for this data item are based on the chapters of the AJCC manual and will be derived primarily from the site/histology fields and other data items as required. IDs are assigned to cases for which AJCC staging is applicable. When staging is not applicable, code ‘XX’ is used.
Rationale
This data item will be used to create an efficient process for running TNM Edits.
Each Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.
AJCC TNM CLIN MNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
100315AJCC2018181120 - 1134
Alternate Name:
XML NAACCR ID:ajccTnmClinM
PARENT XML ELEMENT:Tumor
Description
Detailed site-specific codes for the clinical metastases (M) as defined by the current AJCC edition.
Rationale
CoC requires that AJCC TNM staging be used in its approved cancer programs. AJCC developed its staging system for evaluating trends in the treatment and control of cancer. This staging is used by physicians to estimate prognosis, to plan treatment, to evaluate new types of therapy, to analyze outcome, to design follow-up strategies, and to assess early detection results.
Codes (in addition to those published in the AJCC Cancer Staging Manual)
88Not applicable, no code assigned for this case in the current AJCC Staging Manual.
BlankInformation not available to code this item.
Note: See the AJCC Cancer Staging Manual, 8th edition for site-specific categories for the TNM elements and stage groups. See the CURRENT STORE manual for specifications for codes and data entry rules.
AJCC TNM CLIN NNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
100215AJCC2018181101 - 1115
Alternate Name:
XML NAACCR ID:ajccTnmClinN
PARENT XML ELEMENT:Tumor
Description
Detailed site-specific codes for the clinical nodes (N) as defined by the current AJCC edition.
Rationale
CoC requires that AJCC TNM staging be used in its approved cancer programs. AJCC developed its staging system for evaluating trends in the treatment and control of cancer. This staging is used by physicians to estimate prognosis, to plan treatment, to evaluate new types of therapy, to analyze outcome, to design follow-up strategies, and to assess early detection results.
Codes (in addition to those published in the AJCC Cancer Staging Manual)
88Not applicable, no code assigned for this case in the current AJCC Staging Manual.
BlankInformation not available to code this item.
Note: See the AJCC Cancer Staging Manual, 8th edition for site-specific categories for the TNM elements and stage groups. See the CURRENT STORE manual for specifications for codes and data entry rules.
AJCC TNM CLIN N SUFFIXNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
10344AJCC2018181116 - 1119
Alternate Name:
XML NAACCR ID:ajccTnmClinNSuffix
PARENT XML ELEMENT:Tumor
Description
Detailed site-specific codes for the clinical N category suffix as defined by AJCC.

Clinical, pathological, and postneoadjuvant therapy stage data are given three separate areas in the NAACCR Data Exchange Record Layout.
Rationale
CoC requires that AJCC TNM staging be used in its approved cancer programs. AJCC developed its staging system for evaluating trends in the treatment and control of cancer. This staging is used by physicians to estimate prognosis, to plan treatment, to evaluate new types of therapy, to analyze outcome, to design follow-up strategies, and to assess early detection results.
Codes 
(sn)Sentinel node procedure with or without FNA or core needle biopsy
(f)FNA or core needle biopsy only
BlankNo suffix needed or appropriate; not recorded
Note: Refer to the current AJCC Cancer Staging Manual for staging rules.
AJCC TNM CLIN STAGE GROUPNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
100415AJCC2018181135 - 1149
Alternate Name:
XML NAACCR ID:ajccTnmClinStageGroup
PARENT XML ELEMENT:Tumor
Description
Detailed site-specific codes for the clinical stage group as defined by the current AJCC edition.
Rationale
CoC requires that AJCC TNM staging be used in its approved cancer programs. AJCC developed its staging system for evaluating trends in the treatment and control of cancer. This staging is used by physicians to estimate prognosis, to plan treatment, to evaluate new types of therapy, to analyze outcome, to design follow-up strategies, and to assess early detection results.
Codes (in addition to those published in the AJCC Cancer Staging Manual)
88Not applicable, no code assigned for this case in the current AJCC Staging Manual.
99Unknown, not staged
Note: See the AJCC Cancer Staging Manual, 8th edition for site-specific categories for the TNM elements and stage groups. See the CURRENT STORE manual for specifications for codes and data entry rules.
AJCC TNM CLIN TNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
100115AJCC2018181082 - 1096
Alternate Name:
XML NAACCR ID:ajccTnmClinT
PARENT XML ELEMENT:Tumor
Description
Detailed site-specific codes for the clinical tumor (T) as defined by the current AJCC edition.
Rationale
CoC requires that AJCC TNM staging be used in its approved cancer programs. AJCC developed its staging system for evaluating trends in the treatment and control of cancer. This staging is used by physicians to estimate prognosis, to plan treatment, to evaluate new types of therapy, to analyze outcome, to design follow-up strategies, and to assess early detection results.
Codes (in addition to those published in the AJCC Cancer Staging Manual)
88Not applicable, no code assigned for this case in the current AJCC Staging Manual.
BlankInformation not available to code this item.
Note: See the AJCC Cancer Staging Manual, 8th edition for site-specific categories for the TNM elements and stage groups. See the CURRENT STORE manual for specifications for codes and data entry rules.
AJCC TNM CLIN T SUFFIXNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
10314AJCC2018181097 - 1100
Alternate Name:
XML NAACCR ID:ajccTnmClinTSuffix
PARENT XML ELEMENT:Tumor
Description
Detailed site-specific codes for the clinical T category suffix as defined by AJCC.

Clinical, pathological, and postneoadjuvant therapy stage data are given three separate areas in the NAACCR Data Exchange Record Layout.
Rationale
CoC requires that AJCC TNM staging be used in its approved cancer programs. AJCC developed its staging system for evaluating trends in the treatment and control of cancer. This staging is used by physicians to estimate prognosis, to plan treatment, to evaluate new types of therapy, to analyze outcome, to design follow-up strategies, and to assess early detection results
Codes (as published in the AJCC Cancer Staging Manual)
(m)Multiple synchronous tumors OR For thyroid differentiated and anaplastic only, Multifocal tumor
(s)For thyroid differentiated and anaplastic only, Solitary tumor
BlankNo information available; not recorded
Note: Refer to the current AJCC Cancer Staging Manual for staging rules.
AJCC TNM PATH MNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
101315AJCC2018181188 - 1202
Alternate Name:
XML NAACCR ID:ajccTnmPathM
PARENT XML ELEMENT:Tumor
Description
Detailed site-specific codes for the clinical path (M) as defined by the current AJCC edition.
Rationale
CoC requires that AJCC TNM staging be used in its approved cancer programs. AJCC developed its staging system for evaluating trends in the treatment and control of cancer. This staging is used by physicians to estimate prognosis, to plan treatment, to evaluate new types of therapy, to analyze outcome, to design follow-up strategies, and to assess early detection results.
Codes (in addition to those published in the AJCC Cancer Staging Manual)
88Not applicable, no code assigned for this case in the current AJCC Staging Manual.
BlankInformation not available to code this item.
Note: See the AJCC Cancer Staging Manual, 8th edition for site-specific categories for the TNM elements and stage groups. See the CURRENT STORE manual for specifications for codes and data entry rules.
AJCC TNM PATH NNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
101215AJCC2018181169 - 1183
Alternate Name:
XML NAACCR ID:ajccTnmPathN
PARENT XML ELEMENT:Tumor
Description
Detailed site-specific codes for the pathologic nodes (N) as defined by the current AJCC edition.
Rationale
CoC requires that AJCC TNM staging be used in its approved cancer programs. AJCC developed its staging system for evaluating trends in the treatment and control of cancer. This staging is used by physicians to estimate prognosis, to plan treatment, to evaluate new types of therapy, to analyze outcome, to design follow-up strategies, and to assess early detection results.
Codes (in addition to those published in the AJCC Cancer Staging Manual)
88Not applicable, no code assigned for this case in the current AJCC Staging Manual.
BlankInformation not available to code this item.
Note: See the AJCC Cancer Staging Manual, 8th edition for site-specific categories for the TNM elements and stage groups. See the CURRENT STORE manual for specifications for codes and data entry rules.
AJCC TNM PATH N SUFFIXNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
10354AJCC2018181184 - 1187
Alternate Name:
XML NAACCR ID:ajccTnmPathNSuffix
PARENT XML ELEMENT:Tumor
Description
Detailed site-specific codes for the pathological N category suffix as defined by AJCC.

Clinical, pathological, and postneoadjuvant therapy stage data are given three separate areas in the NAACCR Data Exchange Record Layout.
Rationale
CoC requires that AJCC TNM staging be used in its approved cancer programs. AJCC developed its staging system for evaluating trends in the treatment and control of cancer. This staging is used by physicians to estimate prognosis, to plan treatment, to evaluate new types of therapy, to analyze outcome, to design follow-up strategies, and to assess early detection results.
Codes
(sn)Sentinel node procedure without resection of nodal basin
(f)FNA or core needle biopsy without resection of nodal basin
BlankNo suffix needed or appropriate; not recorded
AJCC TNM PATH STAGE GROUPNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
101415AJCC2018181203 - 1217
Alternate Name:
XML NAACCR ID:ajccTnmPathStageGroup
PARENT XML ELEMENT:Tumor
Description
Detailed site-specific codes for the pathologic stage group as defined by the current AJCC edition.
Rationale
CoC requires that AJCC TNM staging be used in its approved cancer programs. AJCC developed its staging system for evaluating trends in the treatment and control of cancer. This staging is used by physicians to estimate prognosis, to plan treatment, to evaluate new types of therapy, to analyze outcome, to design follow-up strategies, and to assess early detection results.
Codes (in addition to those published in the AJCC Cancer Staging Manual)
88Not applicable, no code assigned for this case in the current AJCC Staging Manual.
99Unknown, not staged
Note: See the AJCC Cancer Staging Manual, 8th edition for site-specific categories for the TNM elements and stage groups. See the CURRENT STORE manual for specifications for codes and data entry rules.
AJCC TNM PATH TNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
101115AJCC2018181150 - 1164
Alternate Name:
XML NAACCR ID:ajccTnmPathT
PARENT XML ELEMENT:Tumor
Description
Detailed site-specific codes for the pathologic tumor (T) as defined by the current AJCC edition.
Rationale
CoC requires that AJCC TNM staging be used in its approved cancer programs. AJCC developed its staging system for evaluating trends in the treatment and control of cancer. This staging is used by physicians to estimate prognosis, to plan treatment, to evaluate new types of therapy, to analyze outcome, to design follow-up strategies, and to assess early detection results.
Codes (in addition to those published in the AJCC Cancer Staging Manual)
88Not applicable, no code assigned for this case in the current AJCC Staging Manual.
BlankInformation not available to code this item.
Note: See the AJCC Cancer Staging Manual, 8th edition for site-specific categories for the TNM elements and stage groups. See the CURRENT STORE manual for specifications for codes and data entry rules.
AJCC TNM PATH T SUFFIXNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
10324AJCC2018181165 - 1168
Alternate Name:
XML NAACCR ID:ajccTnmPathTSuffix
PARENT XML ELEMENT:Tumor
Description
Detailed site-specific codes for the pathological T category suffix as defined by AJCC.

Clinical, pathological, and postneoadjuvant therapy stage data are given three separate areas in the NAACCR Data Exchange Record Layout.
Rationale
CoC requires that AJCC TNM staging be used in its approved cancer programs. AJCC developed its staging system for evaluating trends in the treatment and control of cancer. This staging is used by physicians to estimate prognosis, to plan treatment, to evaluate new types of therapy, to analyze outcome, to design follow-up strategies, and to assess early detection results.
Codes (as published in the AJCC Cancer Staging Manual)
(m)Multiple synchronous tumors OR For thyroid differentiated and anaplastic only, Multifocal tumor
(s)For thyroid differentiated and anaplastic only, Solitary tumor
BlankNo information available; not recorded
Note: Refer to the current AJCC Cancer Staging Manual for staging rules.
AJCC TNM POST THERAPY MNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
102315AJCC2018181256 - 1270
Alternate Name:
XML NAACCR ID:ajccTnmPostTherapyM
PARENT XML ELEMENT:Tumor
Description
Detailed site-specific codes for the postneoadjuvant therapy category metastases (M) as defined by AJCC.

Clinical, pathological, and postneoadjuvant therapy stage data are given three separate areas in the NAACCR Data Exchange Record Layout.
Rationale
CoC requires that AJCC TNM staging be used in its approved cancer programs. AJCC developed its staging system for evaluating trends in the treatment and control of cancer. This staging is used by physicians to estimate prognosis, to plan treatment, to evaluate new types of therapy, to analyze outcome, to design follow-up strategies, and to assess early detection results.

M category for postneoadjuvant therapy staging remains the same as that assigned in the clinical stage before initiation of neoadjuvant therapy, cM or pM.
Codes (in addition to those published in the AJCC Cancer Staging Manual)
88Not applicable, no code assigned for this case in the current AJCC Staging Manual.
BlankThis field is left blank if no information at all is available to code this item.
Note :See the AJCC Cancer Staging Manual, current edition for site-specific categories for the TNM categories and stage groups. See the CURRENT STORE manual for specifications for codes and data entry rules.
AJCC TNM POST THERAPY NNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
102215AJCC1237 - 1251
Alternate Name:
XML NAACCR ID:ajccTnmPostTherapyN
PARENT XML ELEMENT:Tumor
Description
Detailed site-specific codes for the postneoadjuvant therapy nodes (N) as defined by AJCC.

Clinical, pathological, and postneoadjuvant therapy stage data are given three separate areas in the NAACCR Data Exchange Record Layout.
Rationale
CoC requires that AJCC TNM staging be used in its approved cancer programs. AJCC developed its staging system for evaluating trends in the treatment and control of cancer. This staging is used by physicians to estimate prognosis, to plan treatment, to evaluate new types of therapy, to analyze outcome, to design follow-up strategies, and to assess early detection results.

Identifies the absence or presence of regional lymph node (N) metastasis and describes the extent of lymph node metastasis of the tumor known known following the completion of neoadjuvant therapy (satisfying the definition for that disease site) and planned postneoadjuvant therapy surgical resection.
Codes (in addition to those published in the AJCC Cancer Staging Manual)
88Not applicable, no code assigned for this case in the current AJCC Staging Manual.
BlankThis field is left blank if no information at all is available to code this item.
Note: See the AJCC Cancer Staging Manual, current edition for site-specific categories for the TNM categories and stage groups. See the CURRENT STORE manual for specifications for codes and data entry rules.
AJCC TNM POST THERAPY N SUFFIXNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
10364AJCC2018181252 - 1255
Alternate Name:
XML NAACCR ID:ajccTnmPostTherapyNSuffix
PARENT XML ELEMENT:Tumor
Description
Detailed site-specific codes for the postneoadjuvant therapy N category suffix as defined by AJCC.

Clinical, pathological, and postneoadjuvant therapy stage data are given three separate areas in the NAACCR Data Exchange Record Layout.
Rationale
CoC requires that AJCC TNM staging be used in its approved cancer programs. AJCC developed its staging system for evaluating trends in the treatment and control of cancer. This staging is used by physicians to estimate prognosis, to plan treatment, to evaluate new types of therapy, to analyze outcome, to design follow-up strategies, and to assess early detection results.
Codes
(sn)Sentinel node procedure without resection of nodal basin
(f)FNA or core needle biopsy without resection of nodal basin
BlankNo suffix needed or appropriate; not recorded
AJCC TNM POST THERAPY STAGE GROUPNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
102415AJCC2018181271 - 1285
Alternate Name:
XML NAACCR ID:ajccTnmPostTherapyStageGroup
PARENT XML ELEMENT:Tumor
Description
Detailed site-specific codes for the postneoadjuvant therapy stage group as defined by AJCC.

Clinical, pathological, and postneoadjuvant therapy stage data are given three separate areas in the NAACCR Data Exchange Record Layout.
Rationale
CoC requires that AJCC TNM staging be used in its approved cancer programs. AJCC developed its staging system for evaluating trends in the treatment and control of cancer. This staging is used by physicians to estimate prognosis, to plan treatment, to evaluate new types of therapy, to analyze outcome, to design follow-up strategies, and to assess early detection results.

Identifies the remaining anatomic extent of disease based on the T and N following the completion of neoadjuvant therapy (satisfying the definition for that disease site) and planned postneoadjuvant therapy surgical resection, and the M status defined during the diagnostic workup.
Codes (in addition to those published in the AJCC Cancer Staging Manual)
88Not applicable, no code assigned for this case in the current AJCC Staging Manual.
99Unknown, not staged
Note: See the AJCC Cancer Staging Manual, current edition for site-specific categories for the TNM categories and stage groups. See the CURRENT STORE manual for specifications for codes and data entry rules.
AJCC TNM POST THERAPY TNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
102115AJCC2018181218 - 1232
Alternate Name:
XML NAACCR ID:ajccTnmPostTherapyT
PARENT XML ELEMENT:Tumor
Description
Detailed site-specific codes for the postneoadjuvant therapy tumor (T) as defined by AJCC.

Clinical, pathological, and postneoadjuvant therapy stage data are given three separate areas in the NAACCR Data Exchange Record Layout.
Rationale
CoC requires that AJCC TNM staging be used in its approved cancer programs. AJCC developed its staging system for evaluating trends in the treatment and control of cancer. This staging is used by physicians to estimate prognosis, to plan treatment, to evaluate new types of therapy, to analyze outcome, to design follow-up strategies, and to assess early detection results.

Evaluates the primary tumor (T) and reflects the tumor size and/or extension of the tumor known following the completion of neoadjuvant therapy (satisfying the definition for that disease site) and planned postneoadjuvant therapy surgical resection.
Codes (in addition to those published in the AJCC Cancer Staging Manual)
88Not applicable, no code assigned for this case in the current AJCC Staging Manual.
BlankThis field is left blank if no information at all is available to code this item.
Note: See the AJCC Cancer Staging Manual, current edition for site-specific categories for the TNM categories and stage groups. See the CURRENT STORE manual for specifications for codes and data entry rules.
AJCC TNM POST THERAPY T SUFFIXNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
10334AJCC1233 - 1236
Alternate Name:
XML NAACCR ID:ajccTnmPostTherapyTSuffix
PARENT XML ELEMENT:Tumor
Description
Detailed site-specific codes for the postneoadjuvant therapy T category suffix as defined by AJCC.

Clinical, pathological, and postneoadjuvant therapy stage data are given three separate areas in the NAACCR Data Exchange Record Layout.
Rationale
CoC requires that AJCC TNM staging be used in its approved cancer programs. AJCC developed its staging system for evaluating trends in the treatment and control of cancer. This staging is used by physicians to estimate prognosis, to plan treatment, to evaluate new types of therapy, to analyze outcome, to design follow-up strategies, and to assess early detection results.
Codes (as published in the AJCC Cancer Staging Manual)
(m)Multiple synchronous tumors OR For thyroid differentiated and anaplastic only, Multifocal tumor
(s)For thyroid differentiated and anaplastic only, Solitary tumor
BlankNo information available; not recorded
Note: Refer to the current AJCC Cancer Staging Manual for staging rules.
ALCOHOL HISTORYRetired
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
350201012
Alternate Name:
XML NAACCR ID:
PARENT XML ELEMENT:
Description
The NAACCR UDSC retired this data item in Version 12, as of January 1, 2010.
AMBIGUOUS TERMINOLOGY DXRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
4421SEER200611580 - 580
Alternate Name:Ambiguous Terminology
Ambiguous Terminology as Basis for Diagnosis
XML NAACCR ID:ambiguousTerminologyDx
PARENT XML ELEMENT:Tumor
Description
Identifies all cases, including death certificate only and autopsy only, for which an ambiguous term is the most definitive word or phrase used to establish a cancer diagnosis (i.e., to determine whether or not the case is reportable). Ambiguous terminology may originate from any source document, such as pathology report, radiology report, or from a clinical report. This data item is used only when ambiguous terminology is used to establish diagnosis. It is not used when ambiguous terminology is used to clarify a primary site, specific histology, histologic group, or stage of disease.
Rationale
Cases with a reportable cancer diagnosis that has been established based only on reports that contain ambiguous terminology to describe final diagnostic findings cannot currently be identified. Multiple surveys have identified a lack of consensus in the interpretation and use of ambiguous terms across physician specialties. These cases may or may not have an actual cancer diagnosis based on clinician, radiologist, and pathologist review. Furthermore, the historical interpretation and use of ambiguous terms by cancer registrars and registries has not been consistent or compatible with physician use of these terms.

This data item will identify specific primary sites where the ambiguous terminology is commonly used to describe or establish a cancer diagnosis. Data collected will be used as the basis for modifications to case inclusion and reportable rules following complete analysis and impact assessment. This data item will allow cases to be identified within an analysis file and be excluded from patient contact studies.
Codes (refer to http://seer.cancer.gov/tools/mphrules/index.html for additional instructions.)
0Conclusive term
1Ambiguous term only
2Ambiguous term followed by conclusive term
9Unknown term
Refer to Table 2 in Chapter III for a list of ambiguous terms.
ANEMIANew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
38111NAACCR2018181911 - 1911
Alternate Name:RAI Classification: Anemia
XML NAACCR ID:anemia
PARENT XML ELEMENT:Tumor
Description
Anemia is defined by a deficiency of red blood cells or of hemoglobin in the blood. In staging of Chronic Lymphocytic Leukemia/Small Lymphocytic Leukemia (CLL/SLL), anemia is defined as Hgb less than 11.0 g/dL.
Rationale
Anemia is a prognostic factor required for staging of Chronic Lymphocytic Leukemia/Small Lymphocytic Lymphoma (CLL/SLL) in AJCC 8th edition, Chapter 79 Hodgkin and Non-Hodgkin Lymphomas. It is a new data item for cases diagnosed 1/1/2018+.
Codes
0Anemia not present
Hgb >=11.0 g/dL
1Anemia present
Hgb <11.0 g/dL
6Lab value unknown, physician states patient is anemic
7Test ordered, results not in chart
9Not documented in medical record
Anemia not assessed or unknown if assessed
Each Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.
ARCHIVE FINRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
310010CoC200310735 - 744
Alternate Name:
XML NAACCR ID:archiveFin
PARENT XML ELEMENT:Tumor
Description
This field identifies the CoC Facility Identification Number (FIN) of the facility at the time it originally accessioned the tumor.
Rationale
When CoC accredited facilities merge or join networks, their unique CoC Facility Identification Number (FIN) [540] may change. Archive FIN preserves the identity of the facility at the time the case was originally accessioned so that records resubmitted subsequent to such a reorganization can be recognized as belonging to the same facility

Instructions for Coding

CoC maintains the codes, including those for non-hospital sources of reporting.

For facilities with 7-digit FINs in the range of 6020009-6953290 that were assigned by CoC before January 1, 2001, the coded FIN will consist of three leading zeroes followed by the full 7-digit number.

For facilities with FINs greater than or equal to 10000000 that were assigned by CoC after January 1, 2001, enter FIN codes of this type as two zeroes followed by the full 8-digit code. These sometimes are called CoC FIN 10-digit codes.
AUTOPSYRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
19301NAACCR2947 - 2947
Alternate Name:
XML NAACCR ID:autopsy
PARENT XML ELEMENT:Patient
Description
Code indicating whether or not an autopsy was performed.
Codes
0Not applicable; patient alive
1Autopsy performed
2No autopsy performed
9Patient expired, unknown if autopsy performed
This data item is no longer supported by CoC (As of January 1, 2003).
B SYMPTOMSNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
38121NAACCR2018181868 - 1868
Alternate Name:
XML NAACCR ID:bSymptoms
PARENT XML ELEMENT:Tumor
Description
B symptoms refer to systemic symptoms of fever, night sweats, and weight loss which can be associated with both Hodgkin lymphoma and some non-Hodgkin lymphomas. The presence of B symptoms is a prognostic factor for some lymphomas.
Rationale
B symptoms is a Registry Data Collection Variable in AJCC. This data item was previously collected for Lymphomas, SSF# 2.
Codes
0No B symptoms (asymptomatic)
Classified as "A" by physician when asymptomatic
1Any B symptom(s)
Night sweats (drenching)
Unexplained fever (above 38 degrees C)
Unexplained weight loss (generally greater than 10% of body weight in the six months before admission)
B symptoms, NOS
Classified as "B" by physician when symptomatic
8Not applicable: Information not collected for this case
(If this item is required by your standard setter, use of code 8 will result in an edit error.)
9Not documented in medical record
B symptoms not assessed or unknown if assessed
Each Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.
BEHAVIOR (73-91) ICD-O-1Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
19721SEER2604 - 2604
Alternate Name:
XML NAACCR ID:behaviorIcdO1
PARENT XML ELEMENT:Tumor
Description
Area for retaining behavior portion (1 digit) of the ICD-O-1 or field trial morphology codes entered before a conversion to ICD-O-2. See grouped data item Morph (73-91) ICD-O-1 [1970] in Appendix E. The item name includes years 73-91. However, some states may have used the codes for cases before 1973. It is a subfield of the morphology code.
Codes
For tumors diagnosed before 1992, contains the ICD-O-1 or field trial 1-digit behavior code as originally coded, if available. Blank for tumors coded directly into a later version of ICD-O.
BEHAVIOR (92-00) ICD-O-2Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
4301SEER/CoC563 - 563
Alternate Name:ICD-O-2 Behaviour (CCCR)
XML NAACCR ID:behaviorIcdO2
PARENT XML ELEMENT:Tumor
Description
Code for the behavior of the tumor being reported using ICD-O-2. NAACCR adopted ICD-O-2 as the standard coding system for tumors diagnosed from January 1, 1992, through December 31, 2000. In addition, NAACCR recommended that cases diagnosed prior to 1992 be converted to ICD-O-2. See Behavior (73-91) ICD-O-1 [1972], for ICD-O-1 and field trial codes.
Clarification of Required Status This data item was required by all standard-setting organizations for tumors diagnosed from January 1, 1992, through December 31, 2000, and recommended for tumors diagnosed before 1992.

When the histologic type is coded according to the ICD-O-2, the histology code must be reported in Histology (92-00) ICD-O-2 [420], with behavior coded in Behavior (92-00) ICD-O-2 [430].

For information on required status for related data items for histologic type and behavior when coded according to ICD-O-3, see Histologic Type ICD-O-3 [522] and Behavior Code ICD-O-3 [523].
Codes

Valid codes are 0-3. See ICD-O-2,15 page 22, for behavior codes and definitions.

BEHAVIOR CODE ICD-O-3Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
5231SEER/CoC20019568 - 568
Alternate Name:Behavior Code (CoC)
ICD-O-3 Behaviour (CCCR)
XML NAACCR ID:behaviorCodeIcdO3
PARENT XML ELEMENT:Tumor
Description
Code for the behavior of the tumor being reported using ICD-O-3. NAACCR adopted ICD-O-3 as the standard coding system for tumors diagnosed beginning January 1, 2001, and later recommended that prior cases be converted from ICD-O-2. See Behavior (92-00) ICD-O-2 [430], for ICD-O-2 codes.

Juvenile astrocytoma is coded as borderline in ICD-O-3; North American registries report as 9421/3.
Clarification of Required Status
Behavior is required by all standard-setting organizations for tumors diagnosed on or after January 1, 2001, and recommended (by conversion from ICD-O-2 codes) for tumors diagnosed before 2001.

When the histologic type is coded according to the ICD-O-3, the histology code must be reported in Histologic Type ICD-O-3 [522], with behavior coded in Behavior Code ICD-O-3 [523].

For information on required status for related data items for histologic type and behavior when coded according to ICD-O-2, see Histology (92-00) ICD-O-2 [420] and Behavior (92-00) ICD-O-2 [430].
Codes

Valid codes are 0-3. See ICD-O-3,14 page 66, for behavior codes and definitions.

BILIRUBIN PRETREATMENT TOTAL LAB VALUENew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
38135NAACCR2018181851 - 1855
Alternate Name:
XML NAACCR ID:bilirubinPretreatmentTotalLabValue
PARENT XML ELEMENT:Tumor
Description
Bilirubin Pretreatment Total Lab Value records the bilirubin value prior to treatment. Bilirubin level is an indicator of how effectively the liver excretes bile and is required to calculate the Model for End-Stage Liver Disease (MELD) score used to assign priority for liver transplant.
Rationale
Bilirubin Pretreatment Total Lab Value is a Registry Data Collection Variable in AJCC. This data item was previously collected as Liver, CS SSF# 6.
Codes
0.00.0 milligram/deciliter (mg/dL)
0.0 micromole/liter (umol/L)
0.1-999.90.1-999.9 milligram/deciliter (mg/dL)
0.1-999.9 micromole/liter (umol/L)
XXX.11000 milligram/deciliter (mg/dL) or greater
1000 micromole/liter (umol/L) or greater
XXX.7Test ordered, results not in chart
XXX.8Not applicable: Information not collected for this case
(If this item is required by your standard setter, use of code XXX.8 will result in an edit error.)
XXX.9Not documented in medical record
Bilirubin Pretreatment Total Lab Value not assessed or unknown if assessed
Each Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.
BILIRUBIN PRETREATMENT UNIT OF MEASURENew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
38141NAACCR2018181856 - 1856
Alternate Name:
XML NAACCR ID:bilirubinPretreatmentUnitOfMeasure
PARENT XML ELEMENT:Tumor
Description
Bilirubin Pretreatment Unit of Measure identifies the unit of measure for the bilirubin value measured prior to treatment. Bilirubin is commonly measured in units of Milligrams/deciliter (mg/dL) in the United States and Micromoles/liter (umol/L) in Canada and Europe.
Rationale
Bilirubin Pretreatment is a Registry Data Collection Variable in AJCC. Bilirubin Pretreatment Unit of Measure is needed to identify the unit in which bilirubin is measured and was previously collected as Liver, CS SSF# 7.
Codes
1Milligrams per deciliter (mg/dL)
2Micromoles/liter (umol/L)
7Test ordered, results not in chart
8Not applicable: Information not collected for this case
(If this item is required by your standard setter, use of code 8 will result in an edit error.)
9Not documented in medical record
Bilirubin unit of measure not assessed or unknown if assessed
Each Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.
BIRTHPLACERevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
2503SEER/CoC236 - 238
Alternate Name:Place of Birth (SEER/CoC)
XML NAACCR ID:birthplace
PARENT XML ELEMENT:Patient
Description
Code for place of birth of the patient. If a patient has multiple tumors, all records should contain the same code.
Rationale
Place of Birth is helpful for patient matching and can be used when reviewing race and ethnicity. In addition, adding birthplace data to race and ethnicity allows for a more specific definition of the population being reported. Careful descriptions of ancestry, birthplace, and immigration history of populations studied are needed to make the basis for classification into ethnic groups clear. Birthplace has been associated with variation in genetic, socioeconomic, cultural, and nutritional characteristics that affect patterns of disease. A better understanding of the differences within racial and ethnic categories also can help states develop effective, culturally sensitive public health prevention programs to decrease the prevalence of high-risk behaviors and increase the use of preventive services.
Note: For cases diagnosed January 1, 2013, and later, Birthplace--State [252] and Birthplace--Country [254] replace Birthplace [250].
Codes
See Appendix B  for numeric and alphabetic lists of places and codes (also see Appendix B of the SEER Program Code Manual at seer.cancer.gov/tools/codingmanuals/index.html).
BIRTHPLACE--COUNTRYRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
2543NAACCR201313472 - 474
Alternate Name:
XML NAACCR ID:birthplaceCountry
PARENT XML ELEMENT:Patient
Description
Code for the country in which the patient was born. If the patient has multiple tumors, all records should contain the same code. This data item became part of the NAACCR transmission record effective with Volume II, Version 13 in order to include country and state for each geographic item and to use interoperable codes. It supplements the item BIRTHPLACE--STATE [252]. These two data items are intended to replace the use of BIRTHPLACE [250].
Rationale
Place of Birth is helpful for patient matching and can be used when reviewing race and ethnicity. It is an important item in algorithms for imputing race and ethnicity. In addition, adding birthplace data to race and ethnicity allows for a more specific definition of the population being reported. Careful descriptions of ancestry, birthplace, and immigration history of populations studied are needed to make the basis for classification into ethnic groups clear. Birthplace has been associated with variation in genetic, socioeconomic, cultural, and nutritional characteristics that affect patterns of disease. A better understanding of the differences within racial and ethnic categories also can help states develop effective, culturally-sensitive public health prevention programs to decrease the prevalence of high-risk behaviors and increase the use of preventive services.
Codes
Custom codes for historic use only
ZZNNorth America NOS
ZZCCentral American NOS
ZZSSouth America NOS
ZZPPacific NOS
ZZEEurope NOS
ZZFAfrica NOS
ZZAAsia NOS
ZZXNon-US NOS
ZZUUnknown
Custom codes for historic use only
XNINorth American Islands
XCBOther Caribbean Islands
XENEngland, Channel Islands, Isle of Man
XSCScandinavia
XGRGermanic Countries
XSLSlavic Countries
CSKCzechoslovakia (former)
YUGYugoslavia (former)
XUMUkraine and Moldova
XNFNorth Africa
XSDSudanese Countries
XWFWest Africa
XSFSouth Africa
XEFEast Africa
XIFAfrican Islands
XETEthiopia and Eritrea
XAPArabian Peninsula
XISIsrael and Palestine
XCRCaucasian Republics of former USSR
XOROther Asian Republics of former USSR
XSESoutheast Asia
XMS Malaysia, Singapore, Brunei
XCHChina, NOS
XMLMelanesian Islands
XMCMicronesian Islands
XPLPolynesian Islands
See Appendix B for numeric and alphabetic lists of places and codes (also see Appendix B of the SEER Program Code Manual at seer.cancer.gov/tools/codingmanuals/index.html).
BIRTHPLACE--STATERevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
2522NAACCR201313470 - 471
Alternate Name:
XML NAACCR ID:birthplaceState
PARENT XML ELEMENT:Patient
Description
USPS abbreviation for the state, commonwealth, U.S. possession; or CanadaPost abbreviation for the Canadian province/territory in which the patient was born. If the patient has multiple primaries, the state of birth is the same for each tumor. This data item became part of the NAACCR transmission record effective with Volume II, Version 13 in order to include country and state for each geographic item and to use interoperable codes. It supplements the item BIRTHPLACE--COUNTRY [254]. These two data items are intended to replace the item BIRTHPLACE [250].
Rationale
This is a modification of the current item Birthplace [250] item in order to make use of standard codes, rather than using geographic codes that are only used by cancer registries. The intention is that item 250 be converted to populate the new corresponding, more standard, data items.
Codes
See Appendix B for numeric and alphabetic lists of places and codes (also see Appendix B of the SEER Program Code Manual at seer.cancer.gov/tools/codingmanuals/index.html).
BONE INVASIONNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
38151NAACCR2018181950 - 1950
Alternate Name:
XML NAACCR ID:boneInvasion
PARENT XML ELEMENT:Tumor
Description
Bone invasion, the presence or absence of bone invasion based on imaging, is a prognostic factor for soft tissue sarcomas.
Rationale
Bone Invasion is a Registry Data Collection Variable in AJCC. This data item was previously collected for Soft Tissue, SSF# 3.
Codes
0Bone invasion not present/not identified on imaging
1Bone invasion present/identified on imaging
8Not applicable: Information not collected for this case
(If this information is required by your standard setter, use of code 8 may result in an edit error.)
9Not documented in medical record
Bone invasion not assessed or unknown if assessed
Each Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.
BRAIN MOLECULAR MARKERSNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
38162NAACCR2018181994 - 1995
Alternate Name:
XML NAACCR ID:brainMolecularMarkers
PARENT XML ELEMENT:Tumor
Description
Multiple brain molecular markers have become standard pathology components necessary for diagnosis. This data item captures clinically important brain cancer subtypes identified by molecular markers that are not distinguishable by ICD-O-3 codes.
Rationale
Collection of these clinically important brain cancer subtypes has been recommended by CBTRUS.
Codes
01Diffuse astrocytoma, IDH-mutant (9400/3)
02Diffuse astrocytoma, IDH-wildtype (9400/3)
03Anaplastic astrocytoma, IDH-mutant (9401/3)
04Anaplastic astrocytoma, IDH-wildtype (9401/3)
05Glioblastoma, IDH-wildtype (9440/3)
06Oligodendroglioma, IDH-mutant and 1 p/19q co-deleted (9450/3)
07Anaplastic oligodendroglioma, IDH-mutant and 1 p/19q co-deleted (9451/3)
08Medulloblastoma, SHH-activated and TP53-wildtype (9471/3)
09Embryonal tumor with multilayered rosettes, C19MC-altered (9478/3)
85Not applicable: Histology not 9400/3, 9401/3, 9440/3, 9450/3, 9451/3, 9471/3, 9478/3
86Benign or borderline tumor
87Test ordered, results not in chart
88Not applicable: Information not collected for this case
(If this item is required by your standard setter, use of code 88 will result in an edit error.)
99Not documented in patient record
No microscopic confirmation
Brain molecular markers not assessed or unknown if assessed
Each Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.
BRESLOW TUMOR THICKNESS New
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
38174NAACCR2018181891 - 1894
Alternate Name:
XML NAACCR ID:breslowTumorThickness
PARENT XML ELEMENT:Tumor
Description
Breslow Tumor Thickness, the measurement of the thickness of a melanoma as defined by Dr. Alexander Breslow, is a prognostic factor for Melanoma of the Skin.
Rationale
Breslow Tumor Thickness is a Registry Data Collection Variable in AJCC. It was previously collected as Melanoma Skin, CS SSF# 1.
Codes
0.0No mass/tumor found
0.1Greater than 0.0 and less than or equal to 0.1
0.2-99.90.2 - 99.9 millimeters
XX.1100 millimeters or larger
A0.1-A9.9Stated as "at least" some measured value of 0.1 to 9.9
AX.0Stated as greater than 9.9 mm
XX.8Not applicable: Information not collected for this schema
(If this item is required by your standard setter, use of code XX.8 will result in an edit error)
XX.9Not documented in medical record
Microinvasion; microscopic focus or foci only and no depth given
Cannot be determined by pathologist
In situ melanoma
Breslow Tumor Thickness not assessed or unknown if assessed
Each Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.
CA-125 PRETREATMENT INTERPRETATIONNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
38181NAACCR2018181919 - 1919
Alternate Name:: CA-125 (Carbohydrate Antigen 125) Pretreatment Interpretation
XML NAACCR ID:ca125PretreatmentInterpretation
PARENT XML ELEMENT:Tumor
Description
Carbohydrate Antigen 125 (CA-125) is a tumor marker that is useful for following the response to therapy in patients with ovarian cancer, who may have elevated levels of this marker.
Rationale
Preoperative CA-125 is a Registry Data Collection Variable listed in AJCC. It was previously collected as Ovary, CS SSF# 1.
Codes
0Negative/normal; within normal limits
1Positive/elevated
2Stated as borderline; undetermined whether positive or negative
7Test ordered, results not in chart
8Not applicable: Information not collected for this case
(If this item is required by your standard setter, use of code 8 will result in an edit error)
9Not documented in medical record
CA-125 not assessed or unknown if assessed
Each Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.
CANCER STATUSRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
17701CoC2787 - 2787
Alternate Name:
XML NAACCR ID:cancerStatus
PARENT XML ELEMENT:Tumor
Description

Records the presence or absence of clinical evidence of the patient's malignant or non-malignant tumor as of the Date of Last Cancer (tumor) Status [1772]. If the patient has multiple primaries, the values may be different for each primary.

Rationale
This item can be used to compute disease-free survival. By maintaining this data item, central registries can assist hospital registries by sharing this information with other hospital registries that serve the same patients, if the state’s privacy laws so permit.
Codes
1No evidence of this tumor
2Evidence of this tumor
9Unknown, indeterminate whether this tumor is present, not stated in patient record
CASEFINDING SOURCERevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
5012NAACCR200611578 - 579
Alternate Name:
XML NAACCR ID:casefindingSource
PARENT XML ELEMENT:Tumor
Description
This variable codes the earliest source of identifying information. For cases identified by a source other than reporting facilities (such as through death clearance or as a result of an audit), this variable codes the type of source through which the tumor was first identified. This data item cannot be used by itself as a data quality indicator. The timing of the casefinding processes (e.g., death linkage) varies from registry to registry, and the coded value of this variable is a function of that timing.
Rationale
This data item will help reporting facilities as well as regional and central registries in prioritizing their casefinding activities. It will identify reportable tumors that were first found through death clearance or sources other than traditional reporting facilities. It provides more detail than "Type of Reporting Source."

Coding Instructions
This variable is intended to code the source that first identified the tumor. Determine where the case was first identified and enter the appropriate code. At the regional or central level, if a hospital and a non-hospital source identified the case independently of each other, enter the code for the non-hospital source (i.e., codes 30-95 have priority over codes 10-29). If the case was first identified at a reporting facility (codes 10-29), code the earliest source (based on patient or specimen contact at the facility) of identifying information.

If a death certificate, independent pathology laboratory report, consultation-only report from a hospital, or other report was used to identify a case that was then abstracted from a different source, enter the code for the source that first identified the case, not the source from which it was subsequently abstracted. If a regional or central registry identifies a case and asks a reporting facility to abstract it, enter the code that corresponds to the initial source, not the code that corresponds to the eventual reporting facility.
Codes 
10Reporting Hospital, NOS
20Pathology Department Review (surgical pathology reports, autopsies, or cytology reports)
21Daily Discharge Review (daily screening of charts of discharged patients in the medical records department)
22Disease Index Review (review of disease index in the medical records department)
23Radiation Therapy Department/Center
24Laboratory Reports (other than pathology reports, code 20)
25Outpatient Chemotherapy
26Diagnostic Imaging/Radiology (other than radiation therapy, codes 23; includes nuclear medicine)
27Tumor Board
28Hospital Rehabilitation Service or Clinic
29Other Hospital Source (including clinic, NOS or outpatient department, NOS)
30Physician-Initiated Case
40Consultation-only or Pathology-only Report (not abstracted by reporting hospital)
50Independent (non-hospital) Pathology-Laboratory Report
60Nursing Home-Initiated Case
70Coroner's Office Records Review
75Managed Care Organization (MCO) or Insurance Records
80Death Certificate (case identified through death clearance)
85Out-of-State Case Sharing
90Other Non-Reporting Hospital Source
95Quality Control Review (case initially identified through quality control activities such as casefinding audit of a regional or central registry)
99Unknown
CAUSE OF DEATHRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
19104SEER2940 - 2943
Alternate Name:Underlying Cause of Death (SEER)
Underlying Cause of Death (ICD Code) (pre-96 CoC)
XML NAACCR ID:causeOfDeath
PARENT XML ELEMENT:Patient
Description
Official cause of death as coded from the death certificate in valid ICD-7, ICD-8, ICD-9, and ICD-10 codes.
Rationale
Cause of death is used for calculation of adjusted survival rates by the life table method. The adjustment corrects for deaths other than from the diagnosed cancer.
Note: This data item is no longer supported by CoC (as of January 1, 2003).
Special codes in addition to ICD-7, ICD-8, ICD-9, and ICD-10 (refer to SEER Program Code Manual for additional instructions.)
0000Patient alive at last contact
7777State death certificate not available
7797State death certificate available but underlying cause of death is not coded
CEA PRETREATMENT INTERPRETATIONNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
38191NAACCR2018181789 - 1789
Alternate Name:
XML NAACCR ID:ceaPretreatmentInterpretation
PARENT XML ELEMENT:Tumor
Description
CEA (Carcinoembryonic Antigen) Pretreatment Interpretation refers to the interpretation of the CEA value prior to treatment. CEA is a glycoprotein that is produced by adenocarcinomas from all sites as well as many squamous cell carcinomas of the lung and other sites. CEA may be measured in blood, plasma or serum. CEA is a prognostic marker for adenocarcinomas of the appendix, colon and rectum and is used to monitor response to treatment
Rationale
CEA (Carcinoembryonic Antigen) is a Registry Data Collection Variable for AJCC 8. CEA (Carcinoembryonic Antigen) Pretreatment Interpretation was previously collected as Colon and Rectum, CS SSF #1.
Codes
 
0CEA negative/normal; within normal limits
1CEA positive/elevated
2Borderline
3Undetermined if positive or negative (normal values not available)
AND no MD interpretation
7Test ordered, results not in chart
8Not applicable: Information not collected for this case
(If this data item is required by your standard setter, use of code 8 will result in an edit error.)
9Not documented in medical record
CEA (Carcinoembryonic Antigen) Pretreatment Interpretation not assessed or unknown if assessed
Each Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.
CEA PRETREATMENT LAB VALUENew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
38206NAACCR2018181790 - 1795
Alternate Name:
XML NAACCR ID:ceaPretreatmentLabValue
PARENT XML ELEMENT:Tumor
Description
CEA (Carcinoembryonic Antigen) Pretreatment Lab Value records the CEA value prior to treatment. CEA is a nonspecific tumor marker that has prognostic significance for colon and rectum cancer.
Rationale
CEA (Carcinoembryonic Antigen) Pretreatment Lab Value is a Registry Data Collection Variable in AJCC. It was previously collected as Colon and Rectum, CS SSF# 3.
Codes
0.00.0 nanograms/milliliter (ng/m) exactly
0.1-9999.90.1-9999.9 ng/ml
(Exact value to nearest tenth in ng/ml)
XXXX.110,000 ng/ml or greater
XXXX.7Test ordered, results not in chart
XXXX.8Not applicable: Information not collected for this case
(If this information is required by your standard setter, use of code XXXX.8 may result in an edit error.)
XXXX.9Not documented in medical record
CEA (Carcinoembryonic Antigen) Pretreatment Lab Value not assessed or unknown if assessed
Each Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.
CENSUS BLOCK GROUP 2000Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
3621Census178 - 178
Alternate Name:
XML NAACCR ID:censusBlockGroup2000
PARENT XML ELEMENT:Tumor
Description
This field is provided for coding the block group of patient’s residence at time of diagnosis, as defined by the 2000 Census.
Rationale
A block group is a subdivision of a census tract designed to have an average of 1500 people, versus a census tract’s average of 4500 people. All land area in the United States is described by a census block group in the 2000 Census. The Census Bureau publishes detailed population and socioeconomic data at this level.

Block groups thus offer a high level of specificity for geographical and socioeconomic analyses. A block group has no meaning in the absence of a census tract. Refer to Census Tr Certainty 2000 [365] to ascertain basis of assignment of Census Block Group 2000.
Comment
Numerous registries find the distinction between “attempted, could not be determined” (zero) and “not coded” (blank) to be useful for geocoding planning purposes.
Note: The values 1 through 9 are nominal, with no hierarchy of values. This number determines the first digit of all the blocks which comprise the block group; for instance, census block group 3 would contain blocks numbered 3000 to 3999.
Codes
0Census block group assignment was attempted, but the value could not be determined
1-9Census block group values as defined by the Census Bureau
BlankCensus Block Group 2000 not coded
CENSUS BLOCK GROUP 2010Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
3631Census201112.1191 - 191
Alternate Name:
XML NAACCR ID:censusBlockGroup2010
PARENT XML ELEMENT:Tumor
Description
This field is provided for coding the block group of patient’s residence at time of diagnosis, as defined by the 2010 Census.
Rationale
A block group is a subdivision of a census tract designed to have an average of 1500 people, versus a census tract's average of 4500 people. All land area in the United States is described by a census block group in the 2010 Census. The Census Bureau publishes detailed population and socioeconomic data at this level. Block groups thus offer a high level of specificity for geographical and socioeconomic analyses.

A block group has no meaning in the absence of a census tract. Refer to Census Tr Certainty 2010 [367] to ascertain basis of assignment of Census Block Group 2010.
Comment
Numerous registries find the distinction between “attempted, could not be determined” (zero) and “not coded” (blank) to be useful for geocoding planning purposes.
Note: The values 1 through 9 are nominal, with no hierarchy of values. This number determines the first digit of all the blocks which comprise the block group; for instance, census block group 3 would contain blocks numbered 3000 to 3999.
Codes
0Census block group assignment was attempted, but the value could not be determined
1-9Census block group values as defined by the Census Bureau
BlankCensus Block Group 2010 not coded
CENSUS BLOCK GROUP 2020New
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
3611Census201818204 - 204
Alternate Name:
XML NAACCR ID:censusBlockGroup2020
PARENT XML ELEMENT:Tumor
Description
This field is provided for coding the block group of patient's residence at time of diagnosis, as defined by the 2020 Census.
Rationale
A block group is a subdivision of a census tract designed to have approximately 1500, socially homogeneous people, versus census tracts which are designed to have approximately 4000 people. All land area in the United States is described by a census block group in the 2020 Census. The Census Bureau publishes detailed population and socioeconomic data at this level. Block groups thus offer a high level of specificity for geographical and socioeconomic analyses.

A block group has no meaning in the absence of a census tract. Refer to Census Tr Certainty 2020 [369] to ascertain basis of assignment of Census Block Group 2020.
Codes
0-9Census block group values as defined by the Census Bureau
BlankCensus Block Group 2020 not coded
Comment:
Historically, some registries made the distinction between "attempted, could not be determined" and "not coded" by using a 0 for "attempted." However, 0 is a valid block group value.

Note: The values 0 through 9 are nominal, with no hierarchy of values. This number determines the first digit of all the blocks which comprise the block group; for instance, census block group 3 would contain blocks numbered 3000 to 3999.
CENSUS BLOCK GRP 1970/80/90Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
3681Census200811.2164 - 164
Alternate Name:Census Block Grp 1970-90
CensusBlockGroup 70/80/90
XML NAACCR ID:censusBlockGrp197090
PARENT XML ELEMENT:Tumor
Description
This field is provided for coding the block group of patient's residence at time of diagnosis, as defined by the 1970, 1980, or 1990 Census.
Rationale
A block group is a subdivision of a census tract or block numbering area (BNA). Not all of the United States was described by a census block group or BNA prior to the 2000 Census, but for areas assigned to block groups or BNAs, the Census Bureau published detailed population and socioeconomic data. Block groups thus offer a high level of specificity for geographical and socioeconomic analyses, where available.

A block group has no meaning in the absence of a census tract. Refer to Census Tr Cert 1970/80/90 [364] to ascertain the basis of assignment of Census Block Grp 1970/80/90 [368]. Refer to Census Cod Sys 1970/80/90 [120] to ascertain the decade of reference.
Comment: Numerous registries find the distinction between “attempted, could not be determined” (zero) and “not coded” (blank) to be useful for geocoding planning purposes.
Note: The values 1 through 9 are nominal, with no hierarchy of values. This number determines the first digit of all the blocks which comprise the block group; for instance, census block group 3 would contain blocks numbered 3000 to 3999
Codes
0Census block group assignment was attempted, but the value could not be determined
1-9Census block group values as defined by the Census Bureau
BlankCensus Block Grp 1970/80/90 [368] not coded
CENSUS COD SYS 1970/80/90Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
1201SEER165 - 165
Alternate Name:Coding System for Census Tract (pre-96 SEER/CoC)
Census Coding System (CoC)
XML NAACCR ID:censusCodSys19708090
PARENT XML ELEMENT:Tumor
Description
Identified the set of Census Bureau census tract definitions (boundaries) that were used to code the census tract in Census Tract 1970/80/90 [110] for a specific record.
Rationale
Allows for changes in census tracts over time. The census tract definition used to code the case must be recorded so that data are correctly grouped and analyzed. If the coding system were not recorded, the census codes would have to be converted or recoded every time the census tracts were changed.
Codes
0Not tracted
11970 Census Tract Definitions
21980 Census Tract Definitions
31990 Census Tract Definitions
BlankCensus Tract 1970/80/90 not coded

Clarification of NPCR Required Status

 

Census-1990 data items:

Census-2000 data items:

Census Tract  1970/80/90  [110]

Census Tract  2000  [130]

Census Tr Cert 1970/80/90  [364]

Census Tr Certainty 2000  [365]

Census Tract  Cod Sys--1970/80/90 [120]

 


Information on census tract, census tract certainty, and census tract coding system is required. For tumors diagnosed in or after 2003, Census Tract  2000  [130] and Census Tr Certainty 2000  [365] (Census-2000 data items) are required. For tumors diagnosed in or before 2002, the requirement can be met by collecting either the Census-1990 data items [110, 364, 120] or the Census-2000 data items, although the Census-2000 data items [130 and 365] are recommended for tumors diagnosed in 1998 through 2002.
CENSUS IND CODE 1970-2000Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
2803Census/NPCR242 - 244
Alternate Name:Industry Code--Census
XML NAACCR ID:censusIndCode19702000
PARENT XML ELEMENT:Tumor
Description
Code for the patient’s usual industry, using U.S. Census Bureau codes (2000 Census26 is preferable) according to coding procedures recommended for death certificates.25 This data item applies only to patients who are age 14 years or older at the time of diagnosis.

Note: Occupation/industry coding should NOT be performed by reporting facilities. This is a central cancer registry data item. Specially trained and qualified personnel should perform coding.
Formerly Industry Code--Census.
Note: 2000 Census codes for occupation and industry are recommended for tumors diagnosed on or after January 1, 2003.26 The 1990 Census codes are recommended for tumors diagnosed before January 1, 2003.24 For more information, see the U.S. Census Bureau website at: http://www.census.gov/hhes/www/ioindex/ioindex.html.
Rationale
Use of the Census Bureau classification system improves consistency of data collected from multiple sources. The Census Bureau industrial classification system is used for coding industry information from death certificates and from the U.S. Census of Population. The system includes specific coding rules. 22-27
Codes

Software for automated coding of industry and occupation to 1990 Census classifications is available from the Division of Safety Research, National Institute for Occupational Safety and Health, CDC (http://www.cdc.gov/niosh/SOIC/). As of press time, NIOSH is developing new web-based software for automated coding of industry and occupation to appropriate year Census (1990, 2000, or 2010) classifications. The contact person for this software (which will be available after October 2012) is Sue Nowlin, who can be contacted at sxn1@cdc.gov or (513) 841-4467.

Registries may want to wait to code industry and occupation until NAACCR Standards Volume II, Version 13 is released and the NIOSH autocoding software is available.

CENSUS IND CODE 2010 CDCRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
2724Census/NPCR201313483 - 486
Alternate Name:Census Industry Code--2010
Census Ind Code 2010
XML NAACCR ID:censusIndCode2010
PARENT XML ELEMENT:Tumor
Description
Code for the patient's usual industry, using U.S. Census Bureau codes and NIOSH non-paid worker codes. This data item applies only to patients who are age 14 years or older at the time of diagnosis. Usual industry refers to the type of activity at the patient's place of work for most of his or her working life. Formerly Census Ind Code 2010.
Rationale
Use of a standard industry classification system and associated codes improves the consistency of data collected from multiple sources and facilitates the use of data by researchers.
Coding Instructions
Occupation/industry coding should NOT be performed by reporting facilities. This is a central cancer registry data item. Specially trained and qualified personnel should perform coding.
 
Codes for industry are routinely updated to include new or more detailed codes. The 4-digit 2010 industry codes from the U.S. Census Bureau and NIOSH are the most recent codes for industry. When assigning industry codes, central registries should use the most recent code set available. The industry codes for 2010 may be used for earlier diagnosis years. Cases already coded with older industry codes do not have to be recoded to the 2010 codes.
Codes
Valid codes for industry include the U.S. Census codes and the NIOSH non-paid worker codes (listed below). CDC has combined these two sets of codes into a PHIN-VADS value set located here: http://phinvads.cdc.gov/vads/SearchAllVocab_search.action?searchOptions.searchText=2.16.840.1.114222.4.11.7187.

2010 NIOSH Codes for Non-Paid Worker Titles:
9880Retired
9890Housewife, homemaker, volunteers, student, child or infant, patient, disabled, inmate, or individual who did not work
9990Blank text, unknown, don't know, not applicable, refused, or information is inadequate to select a code
BlankCoding of Census Ind Code 2010 CDC not attempted
The Division of Safety Research at CDC’s National Institute for Occupational Safety and Health (NIOSH) has developed new web-based software for automated coding of industry and occupation to appropriate year Census (1990, 2000, or 2010) classifications. This system also includes the NIOSH non-paid worker codes. The contact person for this software is Sue Nowlin, who can be contacted at sxn1@cdc.gov or (513) 841-4467.

For more information related to the U.S. Census Bureau codes, see the following websites:

- Crosswalk: http://www.census.gov/people/io/methodology/. Utilize the following file: 1990-2012 Census Industry Codes with Crosswalk.

- Index: http://www.census.gov/people/io/methodology/indexes.html
CENSUS OCC CODE 1970-2000Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
2703Census/NPCR239 - 241
Alternate Name:Occupation Code--Census
XML NAACCR ID:censusOccCode19702000
PARENT XML ELEMENT:Tumor
Description
Code for the patient’s usual occupation, using U.S. Census Bureau codes (see note below) according to coding procedures recommended for death certificates.22 This data item applies only to patients who are age 14 years or older at the time of diagnosis. Usual occupation is defined as type of job the patient was engaged in for most of his or her working life.

Note: Occupation/industry coding should NOT be performed by reporting facilities. This is a central registry data item. Specially trained and qualified personnel should perform coding.

Note: The 3-digit 2000 Census codes for occupation are recommended for tumors diagnosed on or after January 1, 2003, and prior to January 1, 2013.23, 25 The 3 digit 1990 Census codes for occupation are recommended for tumors diagnosed before January 1, 2003.24, 26 The 4-digit Census occupation codes are recommended for tumors diagnosed on or after January 1, 2013, and should be reported in NAACCR data item Census Occ Code 2010 CDC [282]. For more information, see the U.S. Bureau of the Census website at: http://www.census.gov/hhes/www/ioindex/ioindex.html .

Formerly Occupation Code--Census.
Rationale
Use of the Census Bureau classification system improves consistency of data collected from multiple sources. The Census Bureau occupation classification system is used for coding occupation information from death certificates and from the U.S. Census of Population. The system includes specific coding rules. 22-26, 40

Codes
Software for automated coding of industry and occupation to 1990 Census classifications is available from the Division of Safety Research, National Institute for Occupational Safety and Health, CDC ( http://www.cdc.gov/niosh/SOIC/ ) . As of press time, NIOSH is developing new web-based software for automated coding of industry and occupation to appropriate year Census (1990, 2000, or 2010) classifications. The contact person for this software (which will be available after October 2012) is Sue Nowlin, who can be contacted at sxn1@cdc.gov or (513) 841-4467.

Registries may want to wait to code industry and occupation until NAACCR Standards Volume II, Version 13 is released and the NIOSH autocoding software is available.
CENSUS OCC CODE 2010 CDCRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
2824Census/NPCR201313487 - 490
Alternate Name:Census Occ Code 2010
XML NAACCR ID:censusOccCode2010
PARENT XML ELEMENT:Tumor
Description
Code for the patient's usual occupation, using U.S. Census Bureau codes and NIOSH non-paid worker codes. This data item applies only to patients who are age 14 years or older at the time of diagnosis. Usual occupation is defined as the type of job the patient was engaged in for most of his or her working life. Formerly Census Occ Code 2010.
Rationale
Use of a standard occupation classification system and associated codes improves the consistency of data collected from multiple sources and facilitates the use of data by researchers.

Coding Instructions
Occupation/industry coding should NOT be performed by reporting facilities. This is a central registry data item. Specially trained and qualified personnel should perform coding.

Codes for occupation are routinely updated to include new or more detailed codes. The 4-digit 2010 occupation codes from the U.S. Census Bureau and NIOSH are the most recent codes for occupation. When assigning occupation codes, central registries should use the most recent code set available. The occupation codes for 2010 may be used for earlier diagnosis years. Cases already coded with older occupation codes do not have to be recoded to the 2010 codes.
Valid codes for occupation include the U.S. Census codes and the NIOSH non-paid worker codes (listed below). CDC has combined these two sets of codes into a PHIN-VADS value set located here: http://phinvads.cdc.gov/vads/ViewValueSet.action?id=1445D71C-F37F-4504-8B6C-BA48C5A3F4CA
 
2010 NIOSH Occupation Codes for Non-Paid Worker Titles:
9010 Housewife, homemaker
9020Volunteers
9050Student
9060Retired
9100Child or infant, patient, disabled, inmate, or individual who did not work
9900Blank text, unknown, don't know, not applicable, refused or information is inadequate to select a code
BlankCoding of Census Occ Code 2010 CDC not attempted
Note: The Division of Safety Research at CDC’s National Institute for Occupational Safety and Health (NIOSH) has developed new web-based software for automated coding of industry and occupation to appropriate year Census (1990, 2000, or 2010) classifications. This system also includes the NIOSH non-paid worker codes. The contact person for this software is Sue Nowlin, who can be contacted at sxn1@cdc.gov or (513) 841-4467.

For more information related to the U.S. Census Bureau codes, see the following websites:
- Crosswalk: http://www.census.gov/people/io/methodology/. Utilize the 3rd tab of the following file: 2010 Census Occupation Codes with Crosswalk. The 2002 Census codes are the same as the 2000 codes with a “0” added to the end of the number due to the change from a 3-digit to 4-digit field.

- Index: http://www.census.gov/people/io/methodology/indexes.html
CENSUS OCC/IND SYS 70-00Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
3301NPCR447 - 447
Alternate Name:Occup/Ind Coding System
XML NAACCR ID:censusOccIndSys7000
PARENT XML ELEMENT:Tumor
Description
Code that identifies coding system used for occupation and industry. This is a central cancer registry data item (i .e., codes should be applied by a central or regional registry rather than collected from reporting facilities).
 
Formerly Occup/Ind Coding System.
Codes
11970 Census
21980 Census
31990 Census
42000 Census
52010 Census
7Other coding system
9Unknown coding system
BlankNot collected
Note: 2000 Census codes for occupation and industry are recommended for tumors diagnosed on or after January 1, 2003.26 The 1990 Census codes are recommended for tumors diagnosed before January 1, 2003.24 For more information, see the U.S. Bureau of the Census website at: http://www.census.gov/hhes/www/ioindex/ioindex.html.
CENSUS TR CERT 1970/80/90Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
3641SEER19975.1166 - 166
Alternate Name:Census Tract Certainty
XML NAACCR ID:censusTrCert19708090
PARENT XML ELEMENT:Tumor
Description

Code indicating basis of assignment of census tract or block numbering area (BNA) for an individual record.Helpful in identifying cases tracted from incomplete information or P.O. Box. This item is not coded by the hospital. Central registry staff manually assign the code.

Codes
1Census tract/BNA based on complete and valid street address of residence
2Census tract/BNA based on residence ZIP + 4
3Census tract/BNA based on residence ZIP + 2
4Census tract/BNA based on residence ZIP code only
5Census tract/BNA based on ZIP code of P.O. Box
6Census tract/BNA based on residence city where city has only one census tract, or based on residence ZIP code where ZIP code has only one census tract
9Not assigned, geocoding attempted
BlankNot assigned, geocoding not attempted
Clarification of NPCR Required Status

 

Census-1990 data items:

Census-2000 data items:

Census Tract  1970/80/90  [110]

Census Tract  2000  [130]

Census Tr Cert 1970/80/90  [364]

Census Tr Certainty 2000  [365]

Census Tract  Cod Sys--1970/80/90 [120]

 


Information on census tract, census tract certainty, and census tract coding system is required. For tumors diagnosed in or after 2003, Census Tract 2000 [130] and Census Tr Certainty 2000 [365] (Census-2000 data items) are required. For tumors diagnosed in or before 2002, the requirement can be met by collecting either the Census-1990 data items [110, 364, 120] or the Census-2000 data items, although the Census-2000 data items [130 and 365] are recommended for tumors diagnosed in 1998 through 2002.
CENSUS TR CERTAINTY 2000Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
3651NAACCR200310179 - 179
Alternate Name:
XML NAACCR ID:censusTrCertainty2000
PARENT XML ELEMENT:Tumor
Description
Code indicating basis of assignment of census tract for an individual record. Helpful in identifying cases tracted from incomplete information or P.O. Box. This item is not coded by the hospital. Central registry staff assign the code.
Codes
1Census tract based on complete and valid street address of residence
2Census tract based on residence ZIP + 4
3Census tract based on residence ZIP + 2
4Census tract based on residence ZIP code only
5Census tract based on ZIP code of P.O. Box
6Census tract/BNA based on residence city where city has only one census tract, or based on residence ZIP code where ZIP code has only one census tract
9Not assigned, geocoding attempted
BlankNot assigned, geocoding not attempted
Clarification of NPCR Required Status

 

Census-1990 data items:

Census-2000 data items:

Census Tract  1970/80/90  [110]

Census Tract  2000  [130]

Census Tr Cert 1970/80/90  [364]

Census Tr Certainty 2000  [365]

Census Tract  Cod Sys--1970/80/90 [120]

 


Information on census tract, census tract certainty, and census tract coding system is required. For tumors diagnosed in or after 2003, Census Tract 2000 [130] and Census Tr Certainty 2000 [365] (Census-2000 data items) are required. For tumors diagnosed in or before 2002, the requirement can be met by collecting either the Census-1990 data items [110, 364, 120] or the Census-2000 data items, although the Census-2000 data items [130 and 365] are recommended for tumors diagnosed in 1998 through 2002.
CENSUS TR CERTAINTY 2010Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
3671NAACCR201112.1192 - 192
Alternate Name:
XML NAACCR ID:censusTrCertainty2010
PARENT XML ELEMENT:Tumor
Description

Code indicating basis of assignment of census tract for an individual record. Helpful in identifying cases tracted from incomplete information or P.O. Box. This item is not coded by the hospital. Central registry staff assign the code.

Codes
1Census tract based on complete and valid street address of residence
2Census tract based on residence ZIP + 4
3Census tract based on residence ZIP + 2
4Census tract based on residence ZIP code only
5Census tract based on ZIP code of P.O. Box
6Census tract/BNA based on residence city where city has only one census tract, or based on residence ZIP code where ZIP code has only one census tract
9Not assigned, geocoding attempted
BlankNot assigned, geocoding not attempted
Clarification of NPCR Status
Census-1990 data items: Census-2000 data items: Census-2010 data items:
Census Tract  1970/80/90  [110] Census Tract  2000  [130] Census Tract  2010  [135]
Census Tr Cert 1970/80/90  [364] Census Tr Certainty 2000  [365] Census Tr Certainty 2010  [367]
Census Tract  Cod Sys--1970/80/90 [120]

 

 

 
Information on census tract and census tract certainty is required. Census Tract and Census Tract Certainty should be recorded in the year-appropriate data item fields in order to reflect demographic information at the time of diagnosis. Until the 2010 Census is completed and data are available for geocoding, tumors diagnosed in 2010 or later, should be coded to the 2000 census definitions and recorded in Census Tract 2000 [130] and Census Tr Certainty 2000 [365]. When the 2010 Census data are available for geocoding, tumors diagnosed in 2010 or later must be coded to the 2010 census tract definitions and recorded in Census Tract 2010 [135] and Census Tract Certainty 2010 [367]. For tumors diagnosed between January 1, 2008, and December 31, 2009, use of Census Tract 2010 [135] and Census Track Certainty 2010 [367] is recommended.
CENSUS TR POVERTY INDICTRRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
1451NAACCR201313491 - 491
Alternate Name:
XML NAACCR ID:censusTrPovertyIndictr
PARENT XML ELEMENT:Tumor
Description
Assigns a code for neighborhood poverty level based on the census tract of diagnosis address. Cases diagnosed between 1995 and 2004 are assigned a code based on the 2000 U.S. Census, the last decennial census for which poverty level was collected. Cases diagnosed since 2005 are assigned a code based on the American Community Survey (ACS).

The ACS publishes tract-level poverty data annually, on a rolling five-year window, with a two-year lag (e.g., poverty data for 2006-2010 will be available in 2012). Cases for a given diagnosis year are initially coded using the most recent file available when the cancer data are first released, and the item is subsequently coded using the ACS file centered on the year of diagnosis. For example, cases diagnosed in 2012 will initially be coded using the 2008-2012 ACS file, and two years later using the 2010-2014 ACS file. An exception to this rule is that cases diagnosed in 2005 and 2006 will be coded using the 2005-2009 ACS file, because this was the first such file released. Codes may be automatically assigned by running the Poverty and Census Tract Linkage Program available through the Data Analysis Tools section of the NAACCR website.
Rationale
Many cancers are associated with socioeconomic status and it is useful to include a measure of this in analyses. A detailed rationale for this data item was published in Journal of Registry Management 2010; 37(4): 148-151.
Codes
10% - <5% poverty
25% - <10% poverty
310% - <20% poverty
4 20% - 100% poverty
9Unknown or not applicable
CENSUS TRACT 1970/80/90Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
1106SEER158 - 163
Alternate Name:Census Tract/Block Numbering Area (BNA) (SEER)
Census Tract
XML NAACCR ID:censusTract19708090
PARENT XML ELEMENT:Tumor
Description
Identifies the patient's census tract of residence at the time the tumor was diagnosed. Census Tract 70/80/90 is a derived (geocoded) variables based on the Census Boundary files from 1970, 1980, 1990 Decennial Census. See Census Tract 2000 [130]; Census Tract 2010 [135]; Census Tract 2020 [125]. Codes are those used by the U.S. Census Bureau for the Year 1970, 1980 or 1990 Census. Refer to Census Cod Sys 1970/80/90 [120] to ascertain the decade of reference. For consolidated records, the geocoded state should be based on the best address at diagnosis information identified.
Rationale
Census tract codes allow central registries to calculate incidence rates for geographical areas having population estimates. This field allows a central registry to add Year 2020 Census tracts to tumors diagnosed in previous years, without losing the codes in data items Census Tract 2000 [130]; Census Tract 2010 [135]; Census Tract 2020 [125].

The Census Bureau provides population and other demographic data for census tracts. This allows for small area analysis for general surveillance or special geographical and socioeconomic analysis.
 
Instructions for Coding
  • This variable is generated through the process of geocoding either during abstracting or at the central registry level.
  • Census tract codes have a 4-digit basic number and also may have a 2-digit suffix. Census tract numbers range from 0001.00 to 9999.98, but the decimal should not be retained in the NAACCR layout.
  • At a minimum, all cases diagnosed through diagnosis year 1999 should have a Census Tract 1970/80/90. Cases diagnosed 1996-1999 must have both State at DX Geocode 1970/80/90 [81] and State at DX Geocode 2000 [82] codes for proper assignment of the Census Tr Poverty Indicatr [145].
  • If the patient has multiple tumors, geocoded state at diagnosis may be different for each tumor.
  • Do not update this item if the patient's tract of residence changes. Store updated address information in the affiliated current address data items. Only update based on improved information on the residential address at time of diagnosis. For instance, it is appropriate to correct a tract during manual geocoding or a consolidation process.
  • PO Box address information should not be used to geocode this data item except in the infrequent case when no other address information is available.
  • Blank "Not geocoded" is allowable for cases diagnosed after 1999. However, it is recommended to have all cases geocoded to a Census Tract 1970/80/90 to allow for both retrospective and cross-sectional analyses.
Codes
000100-999998Valid FIPS Codes
000000Area not census-tracted
999999Area census-tracted, but census tract is not available
BlankCensus Tract 1970/80/90 not coded
Note: For U.S. residents, historically, standard codes are those of the FIPS publication "Counties and Equivalent Entities of the United States, Its Possessions, and Associated Areas." These FIPS codes (FIPS 6-4) have been replaced by INCITS standard codes; however, there is no impact on this variable as the codes align with the system the Census used for each decennial census and changes will automatically be accounted for during geocoding. County codes issued by the Federal Information Processing Standards (FIPS) publication Counties and Equivalent Entities of the United States, Its Possessions, and Associated Areas is available in Appendix A.
CENSUS TRACT 2000Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
1306NAACCR172 - 177
Alternate Name:Census Tract--Alternate (pre-2003)
XML NAACCR ID:censusTract2000
PARENT XML ELEMENT:Tumor
Description
Identifies the patient's census tract of residence at the time the tumor was diagnosed. Census Tract 2000 is a derived (geocoded) variables based on the Census Boundary files from 2000. See Census Tract 70/80/90 [110]; Census Tract 2010 [135]; Census Tract 2020 [125]. Codes are those used by the U.S. Census Bureau for the Year 2000 Census. For consolidated records, the geocoded state should be based on the best address at diagnosis information identified.
Rationale
Census tract codes allow central registries to calculate incidence rates for geographical areas having population estimates. This field allows a central registry to add Year 2020 Census tracts to tumors diagnosed in previous years, without losing the codes in data items [110], [130] and [135].

The Census Bureau provides population and other demographic data for census tracts. This allows for small area analysis for general surveillance or special geographical and socioeconomic analysis.
 
Instructions for Coding
  • This variable is generated through the process of geocoding either during abstracting or at the central registry level.
  • Census tract codes have a 4-digit basic number and also may have a 2-digit suffix. Census tract numbers range from 0001.00 to 9999.98, but the decimal should not be retained in the NAACCR layout.
  • It is recommended that all cases diagnosed through 2009 should have a geocoded Census Tract 2000.
  • At a minimum, all cases diagnosed through 1996-2009 should have a geocoded Census Tract 2000. Cases diagnosed 1996-1999 must have both State at DX Geocode 70/80/90 [82] and State at DX 2000 Geocode [83] codes for proper assignment of the Census Tr Poverty Indicatr [145]. Cases diagnosed 2006-2009 must have both State at DX 2000 Geocode [83] and State at DX Geocode 2010 [84] codes for proper assignment of the Census Tr Poverty Indicatr [145].
  • If the patient has multiple tumors, geocoded state at diagnosis may be different for each tumor.
  • Do not update this item if the patient's tract of residence changes. Store updated address information in the affiliated current address data items. Only update based on improved information on the residential address at time of diagnosis. For instance, it is appropriate to correct a tract during manual geocoding or a consolidation process.
  • PO Box address information should not be used to geocode this data item except in the infrequent case when no other address information is available.
  • Blank "Not geocoded" is allowable for cases diagnosed before 1995 and after 2009. However, it is recommended to have all cases geocoded to a 2000 Census Tract to allow for both retrospective and cross-sectional analyses.
Codes
000100-999998Valid FIPS code
000000Area not census tracted
999999Area census-tracted, but census tract is not available
BlankCensus Tract 2000 not coded
Note: For U.S. residents, historically, standard codes are those of the FIPS publication "Counties and Equivalent Entities of the United States, Its Possessions, and Associated Areas." These FIPS codes (FIPS 6-4) have been replaced by INCITS standard codes; however, there is no impact on this variable as the codes align with the system the Census used for each decennial census and changes will automatically be accounted for during geocoding. County codes issued by the Federal Information Processing Standards (FIPS) publication Counties and Equivalent Entities of the United States, Its Possessions, and Associated Areas is available in Appendix A.
CENSUS TRACT 2010Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
1356NAACCR201112.1185 - 190
Alternate Name:
XML NAACCR ID:censusTract2010
PARENT XML ELEMENT:Tumor
Description
Identifies the patient's census tract of residence at the time the tumor was diagnosed. Census Tract 2010 is a derived (geocoded) variables based on the Census Boundary files from 2010. See Census Tract 1970/80/90 [110]; Census Tract 2000 [130]; Census Tract 2020 [125]. Codes are those used by the U.S. Census Bureau for the Year 2010 Census. For consolidated records, the geocoded state should be based on the best address at diagnosis information identified.
Rationale
Census tract codes allow central registries to calculate incidence rates for geographical areas having population estimates. This field allows a central registry to add Year 2020 Census tracts to tumors diagnosed in previous years, without losing the codes in data items [110], [130] and [135].

The Census Bureau provides population and other demographic data for census tracts. This allows for small area analysis for general surveillance or special geographical and socioeconomic analysis.

Instructions for Coding
  • This variable is generated through the process of geocoding either during abstracting or at the central registry level.
  • Census tract codes have a 4-digit basic number and also may have a 2-digit suffix. Census tract numbers range from 0001.00 to 9999.98, but the decimal should not be retained in the NAACCR layout.
  • It is recommended that all cases diagnosed through 2019 should have a geocoded Census Tract 2010.
  • At a minimum, all cases diagnosed through 2006-2019 should have a geocoded Census Tract 2010. Cases diagnosed 2006-2009 must have both State at DX Geocode 2000 [82] and State at DX Geocode 2010 [83] codes for proper assignment of the Census Tr Poverty Indicatr [145]. Cases diagnosed 2016-2019 must have both State at DX Geocode 2010 [83] and State at DX Geocode 2020 [84] codes for proper assignment of the Census Tr Poverty Indicatr [145].
  • If the patient has multiple tumors, geocoded state at diagnosis may be different for each tumor.
  • Do not update this item if the patient's tract of residence changes. Store updated address information in the affiliated current address data items. Only update based on improved information on the residential address at time of diagnosis. For instance, it is appropriate to correct a tract during manual geocoding or a consolidation process.
  • PO Box address information should not be used to geocode this data item except in the infrequent case when no other address information is available.
  • Blank “Not geocoded” is allowable for cases diagnosed before 2005 and after 2019. However, it is preferred to have all cases geocoded to a 2010 Census Tract to allow for both retrospective and cross-sectional analyses.
Codes
000100-999998Valid FIPS code
000000Area not census tracted
999999Area census tracted, but census tract is not available
BlankCensus Tract 2010 not coded
Note: For U.S. residents, historically, standard codes are those of the FIPS publication "Counties and Equivalent Entities of the United States, Its Possessions, and Associated Areas." These FIPS codes (FIPS 6-4) have been replaced by INCITS standard codes; however, there is no impact on this variable as the codes align with the system the Census used for each decennial census and changes will automatically be accounted for during geocoding. County codes issued by the Federal Information Processing Standards (FIPS) publication Counties and Equivalent Entities of the United States, Its Possessions, and Associated Areas is available in Appendix A.
CENSUS TRACT 2020New
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
1256NAACCR201818198 - 203
Alternate Name:
XML NAACCR ID:censusTract2020
PARENT XML ELEMENT:Tumor
Description
Identifies the patient's census tract of residence at the time the tumor was diagnosed. Census Tract 2020 is a derived (geocoded) variables based on the Census Boundary files from 2020 See Census Tract 1970/80/90 [110]; Census Tract 2000 [130]; Census Tract 2010 [135]. Codes are those used by the U.S. Census Bureau for the Year 2020 Census. Census tract codes have a 4-digit basic number and also may have a 2-digit suffix. Census tract numbers range from 0001.00 to 9999.98, but the decimal should not be retained in the NAACCR layout.
Rationale
Census tract codes allow central registries to calculate incidence rates for geographical areas having population estimates. This field allows a central registry to add Year 2020 Census tracts to tumors diagnosed in previous years, without losing the codes in data items [110], [130] and [135].

The Census Bureau provides population and other demographic data for census tracts. This allows for small area analysis for general surveillance or special geographical and socioeconomic analysis.
 
Instructions for Coding
  • This variable is generated through the process of geocoding either during abstracting or at the central registry level.
  • Census tract codes have a 4-digit basic number and also may have a 2-digit suffix. Census tract numbers range from 0001.00 to 9999.98, but the decimal should not be retained in the NAACCR layout.
  • It is recommended that all cases diagnosed through 2029 should have a geocoded Census Tract 2020.
  • At a minimum, all cases diagnosed through 2016-2029 should have a geocoded Census Tract 2020. Cases diagnosed 2016-2019 must have both Geocoded State at DX 2010 and Geocoded State at DX 2020 codes for proper assignment of the Census Tr Poverty Indicatr [145].
  • If the patient has multiple tumors, geocoded state at diagnosis may be different for each tumor.
  • Do not update this item if the patient's tract of residence changes. Store updated address information in the affiliated current address data items. Only update based on improved information on the residential address at time of diagnosis. For instance, it is appropriate to correct a tract during manual geocoding or a consolidation process.
  • PO Box address information should not be used to geocode this data item except in the infrequent case when no other address information is available.
  • Blank "Not geocoded" is allowable for cases diagnosed before 2015 and after 2029. However, it is preferred to have all cases geocoded to a 2020 Census Tract to allow for both retrospective and cross-sectional analyses.
Codes
000000Area not census tracted
000100-999998Valid FIPS code
999999Area census tracted, but census tract is not available
BlankCensus Tract 2020 not coded
Note: For U.S. residents, historically, standard codes are those of the FIPS publication "Counties and Equivalent Entities of the United States, Its Possessions, and Associated Areas." These FIPS codes (FIPS 6-4) have been replaced by INCITS standard codes; however, there is no impact on this variable as the codes align with the system the Census used for each decennial census and changes will automatically be accounted for during geocoding. County codes issued by the Federal Information Processing Standards (FIPS) publication Counties and Equivalent Entities of the United States, Its Possessions, and Associated Areas is available in Appendix A.
CENSUS TRACT CERTAINTY 2020New
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
3691NAACCR201818205 - 205
Alternate Name:
XML NAACCR ID:censusTractCertainty2020
PARENT XML ELEMENT:Tumor
Description
Code indicating basis of assignment of census tract for an individual record. Helpful in identifying cases geocoded from incomplete information or P.O. Box. This item is not coded by the hospital. Central registry staff assign the code based on the results of geocoding.
Codes
1Census tract based on complete and valid street address of residence
2Census tract based on residence ZIP + 4
3Census tract based on residence ZIP + 2
4Census tract based on residence ZIP code only
5Census tract based on ZIP code of P.O. Box
6Census tract/BNA based on residence city where city has only one census tract, or based on residence ZIP code where ZIP code has only one census tract
9Not assigned, geocoding attempted
BlankNot assigned, geocoding not attempted
Clarification of NPCR Required Status
Census-1990 data items: Census-2000 data items: Census-2010 data items: Census-2020 data items:
Census Tract 1970/80/90 [110] Census Tract 2000 [130] Census Tract 2010 [135] Census Tract 2020  [371]
Census Tr Cert 1970/80/90 [364] Census Tr Certainty 2000 [365] Census Tr Certainty 2010 [367] Census Tr Certainty 2010 [369]
Census Tract Cod Sys--1970/80/90 [120]    
Information on census tract and census tract certainty is required. Census Tract and Census Tract Certainty should be recorded in the year-appropriate data item fields in order to reflect demographic information at the time of diagnosis. Until the 2020 Census is completed and data are available for geocoding, tumors diagnosed in 2020 or later, should be coded to the 2010 census definitions and recorded in Census Tract 2010 [135] and Census Tr Certainty 2000 [367]. When the 2020 Census data are available for geocoding, tumors diagnosed in 2020 or later must be coded to the 2020 census tract definitions and recorded in Census Tract 2020 [371] and Census Tract Certainty 2020 [369]. For tumors diagnosed between January 1, 2018, and December 31, 2019, use of Census Tract 2020 [371] and Census Track Certainty 2020 [369] is recommended.
CENSUS TRACT COD SYS--ALTRetired
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
140200310
Alternate Name:
XML NAACCR ID:
PARENT XML ELEMENT:
Description
This data item was retired for Version 10 because Census Tract--2000 [130] is expected to contain only Census 2000 codes.
CHEMOTHERAPY FIELD 1Retired
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
160019965200410.1
Alternate Name:
XML NAACCR ID:
PARENT XML ELEMENT:
Description
This field has been listed as in development since 1996. The NAACCR UDSC retired this data item in Version 10.1, as of January 1, 2004.
CHEMOTHERAPY FIELD 2Retired
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
161019965200410.1
Alternate Name:
XML NAACCR ID:
PARENT XML ELEMENT:
Description
This field has been listed as in development since 1996. The NAACCR UDSC retired this data item in Version 10.1, as of January 1, 2004.
CHEMOTHERAPY FIELD 3Retired
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
162019965200410.1
Alternate Name:
XML NAACCR ID:
PARENT XML ELEMENT:
Description
This field has been listed as in development since 1996. The NAACCR UDSC retired this data item in Version 10.1, as of January 1, 2004.
CHEMOTHERAPY FIELD 4Retired
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
163019965200410.1
Alternate Name:
XML NAACCR ID:
PARENT XML ELEMENT:
Description
This field has been listed as in development since 1996. The NAACCR UDSC retired this data item in Version 10.1, as of January 1, 2004.
CHROMOSOME 19Q: LOSS OF HETEROZYGOSITY (LOH)New
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
38021NAACCR2018181741 - 1741
Alternate Name:
XML NAACCR ID:chromosome19qLossOfHeterozygosity
PARENT XML ELEMENT:Tumor
Description
Chromosome 19q: Loss of Heterozygosity (LOH) refers to the loss of genetic material normally found on the long arm of one of the patient's two copies of chromosome 19. Codeletion of Chromosome 1p and 19q is a diagnostic, prognostic and predictive marker for gliomas and is strongly associated with the oligodendroglioma phenotype.
Rationale
Chromosome 19q: Loss of Heterozygosity (LOH) is a Registry Data Collection Variable in AJCC. It was previously collected as Brain, CS SSF #6.
Codes
0Chromosome 19q deletion/LOH not identified/not present
1Chromosome 19q deletion/LOH present
6Benign or borderline tumor
7Test ordered, results not in chart
8Not applicable: Information not collected for this case
(If this item is required by your standard setter, use of code 8 will result in an edit error.)
9Not documented in patient record
Cannot be determined by the pathologist
Chromosome 19q: LOH not assessed or unknown if assessed
Each Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.
CHROMOSOME 1P: LOSS OF HETEROZYGOSITY (LOH)New
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
38011NAACCR2018181740 - 1740
Alternate Name:
XML NAACCR ID:chromosome1pLossOfHeterozygosity
PARENT XML ELEMENT:Tumor
Description
Chromosome 1p: Loss of Heterozygosity (LOH) refers to the loss of genetic material normally found on the short arm of one of the patient's two copies of chromosome 1. Codeletion of Chromosome 1p and 19q is a diagnostic, prognostic and predictive marker for gliomas and is strongly associated with the oligodendroglioma phenotype.
Rationale
Chromosome 1p: Loss of Heterozygosity (LOH) is a Registry Data Collection Variable in AJCC. It was previously collected as Brain, CS SSF #5.
Codes
0Chromosome 1p deletion/LOH not identified/not present
1Chromosome 1p deletion/LOH identified/present
6Benign or borderline tumor
7Test ordered, results not in chart
8Not applicable: Information not collected for this case
(If this item is required by your standard setter, use of code 8 will result in an edit error.)
9Not documented in patient record
Cannot be determined by the pathologist
Chromosome 1p deletion/LOH not assessed or unknown if assessed
Each Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.
CHROMOSOME 3 STATUSNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
38211NAACCR2018181874 - 1874
Alternate Name:
XML NAACCR ID:chromosome3Status
PARENT XML ELEMENT:Tumor
Description
Chromosome 3 Status refers to the partial or total loss of Chromosome 3, which is a prognostic factor for uveal melanoma.
Rationale
Chromosome 3 Status is a Registry Data Collection Variable in AJCC. This data item was previously collected as Uveal Melanoma, CS SSF# 5.
Codes
0No loss of chromosome 3
1Partial loss of chromosome 3
2Complete loss of chromosome 3
3Loss of chromosome 3, NOS
7Test ordered, results not in chart
8Not applicable: Information not collected for this case
(If this information is required by your standard setter, use of code 8 may result in an edit error.)
9Not documented in medical record
Chromosome 3 status not assessed or unknown if assessed
Each Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.
CHROMOSOME 8Q STATUSNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
38221NAACCR2018181875 - 1875
Alternate Name:
XML NAACCR ID:chromosome8qStatus
PARENT XML ELEMENT:Tumor
Description
Chromosome 8q Status refers to gain in Chromosome 8q, which is a prognostic factor for uveal melanoma.
Rationale
Chromosome 8q Status is a Registry Data Collection Variable in AJCC. This data item was previously collected as Uveal Melanoma, CS SSF# 7.
Codes
0No gain in chromosome 8q
1Gain in chromosome 8q
7Test ordered, results not in chart
8Not applicable: Information not collected for this case
(If this information is required by your standard setter, use of code 8 may result in an edit error.)
9Not documented in medical record
Chromosome 8q status not assessed or unknown if assessed
Each Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.
CIRCUMFERENTIAL RESECTION MARGIN (CRM)New
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
38234NAACCR2018181796 - 1799
Alternate Name:
XML NAACCR ID:circumferentialResectionMargin
PARENT XML ELEMENT:Tumor
Description
Circumferential or Radial Resection Margin, the distance in millimeters between the leading edge of the tumor and the surgically dissected margin as recorded on the pathology report, is a prognostic indicator for colon and rectal cancer. This may also be referred to as the Radial Resection Margin or surgical clearance.
Rationale
Circumferential or Radial Resection Margin is a Registry Data Collection Variable in AJCC. It was previously collected as Colon and Rectum CS SSF# 6.
Codes
0.0Circumferential resection margin (CRM) positive
Margin IS involved with tumor
Described as "less than 1 millimeter (mm)"
0.1-99.9Distance of tumor from margin: 0.1- 99.9 millimeters (mm)
(Exact size to nearest tenth of millimeter)
XX.0100 mm or greater
XX.1Margins clear, distance from tumor not stated
Circumferential or radial resection margin negative, NOS
No residual tumor identified on specimen
XX.2Margins cannot be assessed
XX.3Described as "at least" 1 mm
XX.4Described as "at least" 2 mm
XX.5Described as "at least" 3 mm
XX.6Described as "greater than" 3 mm
XX.7No resection of primary site
Surgical procedure did not remove enough tissue to measure the circumferential or radial resection margin
(Examples include: polypectomy only, endoscopic mucosal resection (EMR), excisional biopsy only, transanal disk excision)
XX.8Not applicable: Information not collected for this case
(If this information is required by your standard setter, use of code XX.8 may result in an edit error.)
XX.9Not documented in medical record
Circumferential or radial resection margin not assessed or unknown if assessed
Each Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.
CLASS OF CASERevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
6102CoC1990pre V4790 - 791
Alternate Name:
XML NAACCR ID:classOfCase
PARENT XML ELEMENT:Tumor
Description
Class of Case divides cases into two groups. Analytic cases (codes 00-22) are those that are required by CoC to be abstracted because of the program’s primary responsibility in managing the cancer. Analytic cases are grouped according to the location of diagnosis and treatment. Treatment and outcome reports may be limited to analytic cases. Nonanalytic cases (codes 30-49 and 99) may be abstracted by the facility to meet central registry requirements or because of a request by the facility’s cancer program. Nonanalytic cases are grouped according to the reason a patient who received care at the facility is nonanalytic, or the reason a patient who never received care at the facility may have been abstracted.

Class of Case can be used in conjunction with Type of Reporting Source [500]. Type of Reporting Source is designed to document the source of documents used to abstract the cancer being reported.
Rationale
Class of Case reflects the facility's role in managing the cancer, whether the cancer is required to be reported by CoC, and whether the case was diagnosed after the program's Reference Date.
Note: This expanded list of coded values is effective with Version 12. *Indicates Class of Case codes appropriate for abstracting cases from non-hospital sources such as physician offices, ambulatory surgery centers, freestanding pathology laboratories, radiation therapy centers. When applied to these types of facilities, the non-hospital source is the reporting facility. The codes are applied the same way as if the case were reported from a hospital. By using Class of Case codes in this manner for non-hospital sources, the central cancer registry is able to retain information reflecting the facility’s role in managing the cancer consistent with the way it is reported from hospitals. Using Class of Case in conjunction with Type of Reporting Source [500] which identifies the source documents used to abstract the cancer being reported, the central cancer registry has two distinct types of information to use in making consolidation decisions
Codes
Analytic Classes of Case (Required by CoC to be abstracted by accredited cancer programs; refer to STORE for additional instructions)
INITIAL DIAGNOSIS AT REPORTING FACILITY
00*Initial diagnosis at the reporting facility AND all treatment or a decision not to treat was done ELSEWHERE
10*Initial diagnosis at the reporting facility or in a staff physician's office AND PART OR ALL of first course treatment or a decision not to treat was at the reporting facility, NOS
11Initial diagnosis in staff physician's office AND PART of first course treatment was done at the reporting facility
12Initial diagnosis in staff physician's office AND ALL first course treatment or a decision not to treat was done at the reporting facility
13*Initial diagnosis at the reporting facility AND PART of first course treatment was done at the reporting facility
14*Initial diagnosis at the reporting facility AND ALL first course treatment or a decision not to treat was done at the reporting facility
INITIAL DIAGNOSIS ELSEWHERE, FACILITY INVOLVED IN FIRST COURSE TREATMENT
20*Initial diagnosis elsewhere AND PART OR ALL of first course treatment was done at the reporting facility, NOS
21*Initial diagnosis elsewhere AND PART of treatment was done at the reporting facility
22*Initial diagnosis elsewhere AND ALL first course treatment was done at the reporting facility
Classes of Case not required by CoC to be abstracted (May be required by Cancer Committee, state or regional registry, or other entity)
PATIENT APPEARS IN PERSON AT REPORTING FACILITY; BOTH INITIAL DIAGNOSIS AND TREATMENT ELSEWHERE
30*Initial diagnosis and all first course treatment elsewhere AND reporting facility participated in DIAGNOSTIC WORKUP (for example, consult only, staging workup after initial diagnosis elsewhere)
31*Initial diagnosis and all first course treatment elsewhere AND reporting facility provided IN-TRANSIT care
32*Diagnosis AND all first course treatment provided elsewhere AND patient presents at reporting facility with disease RECURRENCE OR PERSISTENCE
33*Diagnosis AND all first course treatment provided elsewhere AND patient presents at reporting facility with disease HISTORY ONLY
34Type of case not required by CoC to be accessioned (for example, a benign colon tumor) AND initial diagnosis AND part or all of first course treatment by reporting facility
35Case diagnosed before program's Reference Date AND initial diagnosis AND PART OR ALL of first course treatment by reporting facility
36Type of case not required by CoC to be accessioned (for example, a benign colon tumor) AND initial diagnosis elsewhere AND part or all of first course treatment by reporting facility
37Case diagnosed before program's Reference Date AND initial diagnosis elsewhere AND all or part of first course treatment by reporting facility
38*Initial diagnosis established by AUTOPSY at the reporting facility, cancer not suspected prior to death
PATIENT DOES NOT APPEAR IN PERSON AT REPORTING FACILITY
40Diagnosis AND all first course treatment given at the same staff physician's office
41Diagnosis and all first course treatment given in two or more different staff physician offices
42Non-staff physician or non-CoC accredited clinic or other facility, not part of reporting facility, accessioned by reporting facility for diagnosis and/or treatment by that entity (for example, hospital abstracts cases from an independent radiation facility)
43*PATHOLOGY or other lab specimens ONLY
49*DEATH CERTIFICATE ONLY
UNKNOWN RELATIONSHIP TO REPORTING FACILITY
99*Nonanalytic case of unknown relationship to facility (not for use by CoC accredited cancer programs for analytic cases.); UNKNOWN
Note: This expanded list of coded values is effective with Version 12.

*Indicates Class of Case codes appropriate for abstracting cases from non-hospital sources such as physician offices, ambulatory surgery centers, freestanding pathology laboratories, radiation therapy centers. When applied to these types of facilities, the non-hospital source is the reporting facility. The codes are applied the same way as if the case were reported from a hospital.

By using Class of Case codes in this manner for non-hospital sources, the central cancer registry is able to retain information reflecting the facility's role in managing the cancer consistent with the way it is reported from hospitals. Using Class of Case in conjunction with Type of Reporting Source [500] which identifies the source documents used to abstract the cancer being reported, the central cancer registry has two distinct types of information to use in making consolidation decisions
COC ACCREDITED FLAGNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
21521NPCR2018182624 - 2624
Alternate Name:
XML NAACCR ID:cocAccreditedFlag
PARENT XML ELEMENT:Tumor
Description
CoC Accredited Flag is assigned at the point and time of data abstraction to label an abstract being prepared for an analytic cancer case at a facility accredited by the Commission on Cancer (CoC). The flag may be assigned manually or can be defaulted by the registry’s software.
Rationale
CoC-accredited facilities are required to collect certain data items including TNM staging. It is burdensome for central registries to maintain a list of accredited facilities, and the list changes frequently. The flag is a means of incorporating the accredited status into abstracts at the time of abstraction by someone who has knowledge of the status. The flag thus simplifies validating that required items have been abstracted by CoC-accredited facilities. NPCR will use this flag to for validating and consolidating TNM.
Codes   
0Abstract prepared at a facility WITHOUT CoC accreditation of its cancer program
1ANALYTIC abstract prepared at facility WITH CoC accreditation of its cancer program (Includes Class of Case codes 10-22)
2NON-ANALYTIC abstract prepared at facility WITH CoC accreditation of its cancer program (Includes Class of Case codes 30-43 and 99, plus code 00 which CoC considers analytic but does not require to be staged)
BlankNot applicable; DCO
COC CODING SYS--CURRENTRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
21402CoC2619 - 2620
Alternate Name:Commission on Cancer Coding System-Current (CoC)
XML NAACCR ID:cocCodingSysCurrent
PARENT XML ELEMENT:Tumor
Description
Code the ACoS CoC coding system currently used in the record. CoC codes may be converted from an earlier version.
Codes
00No CoC coding system used
01Pre-1988 (Cancer Program Manual Supplement)
021988 Data Acquisition Manual
031989 Data Acquisition Manual Revisions
041990 Data Acquisition Manual Revisions
051994 Data Acquisition Manual (Interim/Revised)
06ROADS (effective with cases diagnosed 1996-1997)
07ROADS and 1998 Supplement (effective with cases diagnosed 1998-2002)
08FORDS (effective with cases diagnosed 2003-2017)
99Unknown coding system
09STORE (effective with cases diagnosed 2018 and forward)
COC CODING SYS--ORIGINALRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
21502CoC2621 - 2622
Alternate Name:
XML NAACCR ID:cocCodingSysOriginal
PARENT XML ELEMENT:Tumor
Description
Code for the ACoS CoC coding system originally used to code the record.
Codes
00No CoC coding system used
01Pre-1988 (Cancer Program Manual Supplement)
021988 Data Acquisition Manual
031989 Data Acquisition Manual Revisions
041990 Data Acquisition Manual Revisions
051994 Data Acquisition Manual (Interim/Revised)
06ROADS (effective with cases diagnosed 1996-1997)
07ROADS and 1998 Supplement (effective with cases diagnosed 1998-2002)
08FORDS (effective with cases diagnosed 2003-2017)
99Original CoC coding system is not known
09STORE (effective with cases diagnosed 2018 and forward)
CODING SYSTEM FOR EODRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
8701SEER199551045 - 1045
Alternate Name:Coding System for Extent of Disease (SEER)
XML NAACCR ID:codingSystemForEod
PARENT XML ELEMENT:Tumor
Description
Indicates the type of SEER EOD code applied to the tumor. Should be used whenever EOD coding is applied.
Rationale
Used in data editing and analysis.
Codes
02-Digit Nonspecific Extent of Disease (1973-82)
12-Digit Site-Specific Extent of Disease (1973-82)
213-Digit (expanded) Site-Specific Extent of Disease (1973-1982)
34-Digit Extent of Disease (1983-87)
410-Digit Extent of Disease, 1988 (1988-2003)
BlankCases diagnosed 2004+; or the item is not collected
COMORBID/COMPLICATION 1Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
31105CoC2003101527 - 1531
Alternate Name:Comorbidities and Complications #1
XML NAACCR ID:comorbidComplication1
PARENT XML ELEMENT:Tumor
Description
Records the patient’s pre-existing medical conditions, factors influencing health status, and/or complications during the patient’s hospital stay for the treatment of this cancer using ICD-9-CM codes. All are considered secondary diagnoses
Rationale
Pre-existing medical conditions, factors influencing health status, and/or complications may affect treatment decisions and influence patient outcomes. Information on comorbidities is used to adjust outcome statistics when evaluating patient survival and other outcomes. Complications may be related to the quality of care.
Codes (Refer to the most recent version of STORE for additional instructions.)
ICD-9-CM Codes 00100-13980, 24000-99990, E8700-E8799, E9300-E9499, V0720-V0739, V1000-V1590, V2220- V2310, V2540, V4400-V4589, and V5041-V5049.
00000No secondary diagnoses documented
Note: For comorbid conditions (ICD-9-CM codes 00100-13980 and 24000-99990), there is an assumed decimal point between the third and fourth characters. For complications (ICD-9-CM codes E8700-E8799 and E9300-E9499), there is an assumed decimal point between the fourth and fifth characters. For conditions influencing health status and contact with health services (ICD-9-CM codes V0720-V0739, V1000-V1590, V2220- V2310, V2540, V4400-V4589, and V5041-V5049), there is an assumed decimal point between the third and fourth characters.
COMORBID/COMPLICATION 10Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
31645CoC2006111572 - 1576
Alternate Name:Comorbidities and Complications #10
XML NAACCR ID:comorbidComplication10
PARENT XML ELEMENT:Tumor
Description
Records the patient’s pre-existing medical conditions, factors influencing health status, and/or complications for the treatment of this cancer using ICD-9-CM codes. All are considered secondary diagnoses.
Rationale
Pre-existing medical conditions, factors influencing health status, and/or complications may affect treatment decisions and influence patient outcomes. Information on comorbidities is used to adjust outcome statistics when evaluating patient survival and other outcomes. Complications may be related to the quality of care.
Codes (Refer to the most recent version of STORE for additional instructions.)
ICD-9-CM Codes 00100-13980, 24000-99990, E8700-E8799, E9300-E9499, V0720-V0739, V1000-V1590, V2220- V2310, V2540, V4400-V4589, and V5041-V5049.
Leave blank if no further secondary diagnosis.
Note: For comorbid conditions (ICD-9-CM codes 00100-13980 and 24000-99990), there is an assumed decimal point between the third and fourth characters. For complications (ICD-9-CM codes E8700-E8799 and E9300-E9499), there is an assumed decimal point between the fourth and fifth characters. For conditions influencing health status and contact with health services (ICD-9-CM codes V0720-V0739, V1000-V1590, V2220-V2310, V2540, V4400-V4589, and V5041-V5049), there is an assumed decimal point between the third and fourth characters.
COMORBID/COMPLICATION 2Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
31205CoC2003101532 - 1536
Alternate Name:Comorbidities and Complications #2
XML NAACCR ID:comorbidComplication2
PARENT XML ELEMENT:Tumor
Description
Records the patient’s pre-existing medical conditions, factors influencing health status, and/or complications during the patient’s hospital stay for the treatment of this cancer using ICD-9-CM codes. All are considered secondary diagnoses.
Rationale
Pre-existing medical conditions, factors influencing health status, and/or complications may affect treatment decisions and influence patient outcomes. Information on comorbidities is used to adjust outcome statistics when evaluating patient survival and other outcomes. Complications may be related to the quality of care.
Codes (Refer to the most recent version of STORE for additional instructions.)
ICD-9-CM Codes 00100-13980, 24000-99990, E8700-E8799, E9300-E9499, V0720-V0739, V1000-V1590, V2220- V2310, V2540, V4400-V4589, and V5041-V5049.
 
Leave blank if no further secondary diagnosis.
Note: For comorbid conditions (ICD-9-CM codes 00100-13980 and 24000-99990), there is an assumed decimal point between the third and fourth characters. For complications (ICD-9-CM codes E8700-E8799 and E9300-E9499), there is an assumed decimal point between the fourth and fifth characters. For conditions influencing health status and contact with health services (ICD-9-CM codes V0720-V0739, V1000-V1590, V2220-V2310, V2540, V4400-V4589, and V5041-V5049), there is an assumed decimal point between the third and fourth characters.
COMORBID/COMPLICATION 3Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
31305CoC2003101537 - 1541
Alternate Name:Comorbidities and Complications #3
XML NAACCR ID:comorbidComplication3
PARENT XML ELEMENT:Tumor
Description
Records the patient’s pre-existing medical conditions, factors influencing health status, and/or complications during the patient’s hospital stay for the treatment of this cancer using ICD-9-CM codes. All are considered secondary diagnoses.
Rationale
Pre-existing medical conditions, factors influencing health status, and/or complications may affect treatment decisions and influence patient outcomes. Information on comorbidities is used to adjust outcome statistics when evaluating patient survival and other outcomes. Complications may be related to the quality of care.
Codes (Refer to the most recent version of STORE for additional instructions.)
ICD-9-CM Codes 00100-13980, 24000-99990, E8700-E8799, E9300-E9499, V0720-V0739, V1000-V1590, V2220- V2310, V2540, V4400-V4589, and V5041-V5049.

Leave blank if no further secondary diagnoses.
Note: For comorbid conditions (ICD-9-CM codes 00100-13980 and 24000-99990), there is an assumed decimal point between the third and fourth characters. For complications (ICD-9-CM codes E8700-E8799 and E9300-E9499), there is an assumed decimal point between the fourth and fifth characters. For conditions influencing health status and contact with health services (ICD-9-CM codes V0720-V0739, V1000-V1590, V2220-V2310, V2540, V4400-V4589, and V5041-V5049), there is an assumed decimal point between the third and fourth characters.
COMORBID/COMPLICATION 4Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
31405CoC2003101542 - 1546
Alternate Name:Comorbidities and Complications #4
XML NAACCR ID:comorbidComplication4
PARENT XML ELEMENT:Tumor
Description
Records the patient’s pre-existing medical conditions, factors influencing health status, and/or complications during the patient’s hospital stay for the treatment of this cancer using ICD-9-CM codes. All are considered secondary diagnoses.
Rationale
Pre-existing medical conditions, factors influencing health status, and/or complications may affect treatment decisions and influence patient outcomes. Information on comorbidities is used to adjust outcome statistics when evaluating patient survival and other outcomes. Complications may be related to the quality of care.
Codes (Refer to the most recent version of STORE for additional instructions.)
ICD-9-CM Codes 00100-13980, 24000-99990, E8700-E8799, E9300-E9499, V0720-V0739, V1000-V1590, V2220- V2310, V2540, V4400-V4589, and V5041-V5049.

Leave blank if no further secondary diagnoses.
Note: For comorbid conditions (ICD-9-CM codes 00100-13980 and 24000-99990), there is an assumed decimal point between the third and fourth characters. For complications (ICD-9-CM codes E8700-E8799 and E9300-E9499), there is an assumed decimal point between the fourth and fifth characters. For conditions influencing health status and contact with health services (ICD-9-CM codes V0720-V0739, V1000-V1590, V2220-V2310, V2540, V4400-V4589, and V5041-V5049), there is an assumed decimal point between the third and fourth characters.
COMORBID/COMPLICATION 5Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
31505CoC2003101547 - 1551
Alternate Name:Comorbidities and Complications #5
XML NAACCR ID:comorbidComplication5
PARENT XML ELEMENT:Tumor
Description
Records the patient’s pre-existing medical conditions, factors influencing health status, and/or complications during the patient’s hospital stay for the treatment of this cancer using ICD-9-CM codes. All are considered secondary diagnoses.
Rationale
Pre-existing medical conditions, factors influencing health status, and/or complications may affect treatment decisions and influence patient outcomes. Information on comorbidities is used to adjust outcome statistics when evaluating patient survival and other outcomes. Complications may be related to the quality of care.
Codes (Refer to the most recent version of STORE for additional instructions.)
ICD-9-CM Codes 00100-13980, 24000-99990, E8700-E8799, E9300-E9499, V0720-V0739, V1000-V1590, V2220- V2310, V2540, V4400-V4589, and V5041-V5049.

Leave blank if no further secondary diagnoses.
Note: For comorbid conditions (ICD-9-CM codes 00100-13980 and 24000-99990), there is an assumed decimal point between the third and fourth characters. For complications (ICD-9-CM codes E8700-E8799 and E9300-E9499), there is an assumed decimal point between the fourth and fifth characters. For conditions influencing health status and contact with health services (ICD-9-CM codes V0720-V0739, V1000-V1590, V2220-V2310, V2540, V4400-V4589, and V5041-V5049), there is an assumed decimal point between the third and fourth characters.
COMORBID/COMPLICATION 6Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
31605CoC2003101552 - 1556
Alternate Name:Comorbidities and Complications #6
XML NAACCR ID:comorbidComplication6
PARENT XML ELEMENT:Tumor
Description
Records the patient’s pre-existing medical conditions, factors influencing health status, and/or complications during the patient’s hospital stay for the treatment of this cancer using ICD-9-CM codes. All are considered secondary diagnoses.
Rationale
Pre-existing medical conditions, factors influencing health status, and/or complications may affect treatment decisions and influence patient outcomes. Information on comorbidities is used to adjust outcome statistics when evaluating patient survival and other outcomes. Complications may be related to the quality of care.
Codes (Refer to the most recent version of STORE for additional instructions.)
ICD-9-CM Codes 00100-13980, 24000-99990, E8700-E8799, E9300-E9499, V0720-V0739, V1000-V1590, V2220- V2310, V2540, V4400-V4589, and V5041-V5049.

Leave blank if no further secondary diagnoses.
Note: For comorbid conditions (ICD-9-CM codes 00100-13980 and 24000-99990), there is an assumed decimal point between the third and fourth characters. For complications (ICD-9-CM codes E8700-E8799 and E9300-E9499), there is an assumed decimal point between the fourth and fifth characters. For conditions influencing health status and contact with health services (ICD-9-CM codes V0720-V0739, V1000-V1590, V2220-V2310, V2540, V4400-V4589, and V5041-V5049), there is an assumed decimal point between the third and fourth characters.
COMORBID/COMPLICATION 7Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
31615CoC2006111557 - 1561
Alternate Name:Comorbidities and Complications #7
XML NAACCR ID:comorbidComplication7
PARENT XML ELEMENT:Tumor
Description
Records the patient’s pre-existing medical conditions, factors influencing health status, and/or complications during the patient’s hospital stay for the treatment of this cancer using ICD-9-CM codes. All are considered secondary diagnoses.
Rationale
Pre-existing medical conditions, factors influencing health status, and/or complications may affect treatment decisions and influence patient outcomes. Information on comorbidities is used to adjust outcome statistics when evaluating patient survival and other outcomes. Complications may be related to the quality of care.
Codes (Refer to the most recent version of STORE for additional instructions.)
ICD-9-CM Codes 00100-13980, 24000-99990, E8700-E8799, E9300-E9499, V0720-V0739, V1000-V1590, V2220- V2310, V2540, V4400-V4589, and V5041-V5049.

Leave blank if no further secondary diagnosis.
Note: For comorbid conditions (ICD-9-CM codes 00100-13980 and 24000-99990), there is an assumed decimal point between the third and fourth characters. For complications (ICD-9-CM codes E8700-E8799 and E9300-E9499), there is an assumed decimal point between the fourth and fifth characters. For conditions influencing health status and contact with health services (ICD-9-CM codes V0720-V0739, V1000-V1590, V2220-V2310, V2540, V4400-V4589, and V5041-V5049), there is an assumed decimal point between the third and fourth characters.
COMORBID/COMPLICATION 8Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
31625CoC2006111562 - 1566
Alternate Name:Comorbidities and Complications #8
XML NAACCR ID:comorbidComplication8
PARENT XML ELEMENT:Tumor
Description
Records the patient’s pre-existing medical conditions, factors influencing health status, and/or complications during the patient’s hospital stay for the treatment of this cancer using ICD-9-CM codes. All are considered secondary diagnoses.
Rationale
Pre-existing medical conditions, factors influencing health status, and/or complications may affect treatment decisions and influence patient outcomes. Information on comorbidities is used to adjust outcome statistics when evaluating patient survival and other outcomes. Complications may be related to the quality of care.
Codes (Refer to the most recent version of STORE for additional instructions.)
ICD-9-CM Codes 00100-13980, 24000-99990, E8700-E8799, E9300-E9499, V0720-V0739, V1000-V1590, V2220- V2310, V2540, V4400-V4589, and V5041-V5049.

Leave blank if no further secondary diagnosis.
Note: For comorbid conditions (ICD-9-CM codes 00100-13980 and 24000-99990), there is an assumed decimal point between the third and fourth characters. For complications (ICD-9-CM codes E8700-E8799 and E9300-E9499), there is an assumed decimal point between the fourth and fifth characters. For conditions influencing health status and contact with health services (ICD-9-CM codes V0720-V0739, V1000-V1590, V2220-V2310, V2540, V4400-V4589, and V5041-V5049), there is an assumed decimal point between the third and fourth characters.
COMORBID/COMPLICATION 9Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
31635CoC2006111567 - 1571
Alternate Name:Comorbidities and Complications #9
XML NAACCR ID:comorbidComplication9
PARENT XML ELEMENT:Tumor
Description
Records the patient’s pre-existing medical conditions, factors influencing health status, and/or complications during the patient’s hospital stay for the treatment of this cancer using ICD-9-CM codes. All are considered secondary diagnoses.
Rationale
Pre-existing medical conditions, factors influencing health status, and/or complications may affect treatment decisions and influence patient outcomes. Information on comorbidities is used to adjust outcome statistics when evaluating patient survival and other outcomes. Complications may be related to the quality of care.
Codes (Refer to the most recent version of STORE for additional instructions.)
ICD-9-CM Codes 00100-13980, 24000-99990, E8700-E8799, E9300-E9499, V0720-V0739, V1000-V1590, V2220- V2310, V2540, V4400-V4589, and V5041-V5049.
Leave blank if no further secondary diagnosis.
Note: For comorbid conditions (ICD-9-CM codes 00100-13980 and 24000-99990), there is an assumed decimal point between the third and fourth characters. For complications (ICD-9-CM codes E8700-E8799 and E9300-E9499), there is an assumed decimal point between the fourth and fifth characters. For conditions influencing health status and contact with health services (ICD-9-CM codes V0720-V0739, V1000-V1590, V2220-V2310, V2540, V4400-V4589, and V5041-V5049), there is an assumed decimal point between the third and fourth characters.
COMPUTED ETHNICITYRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
2001SEER19954220 - 220
Alternate Name:
XML NAACCR ID:computedEthnicity
PARENT XML ELEMENT:Patient
Description
Code identifying those cases for which ethnicity was determined by matching Name--Last [2230] and Name--Maiden [2390] to a computer list of Spanish/Hispanic names or by a software algorithm. This field was adopted for use for tumors diagnosed 1994 forward. See also Computed Ethnicity Source [210].
Rationale
One method of identifying persons of Hispanic origin is to apply a standard computer list or algorithm to items 2230 and 2390, the patient’s surname and/or maiden name. This has advantages across large populations of being reproducible and facilitating comparisons between areas using identical methods. It may sometimes be possible to identify population denominators in which the same method was used to identify Hispanics. Generally, only central registries will have this capability.

This field provides coding to indicate both that such a computerized name-based method was applied and the results of the method. Coding is independent of that in Spanish/Hispanic Origin [190]. The computer-derived ethnicity may be different from the ethnicity reported by registries in Spanish/Hispanic Origin [190] as code 7 (Spanish Surname Only), because that field may include manual review. This field shows the results of computer-derived ethnicity only.
Codes
0No match was run (for 1994 and later tumors)
1Non-Hispanic last name and non-Hispanic maiden name
2Non-Hispanic last name, did not check maiden name or patient was male
3Non-Hispanic last name, missing maiden name
4Hispanic last name, non-Hispanic maiden name
5Hispanic last name, did not check maiden name or patient was male
6Hispanic last name, missing maiden name
7Hispanic Maiden name (females only) (regardless of last name)
Blank1993 and earlier tumors, no match was run

Note:
For SEER, blanks are required for all cases diagnosed before 1994 and blanks are not allowed for any case diagnosed 1994 and after. Other registries may have computed this item for earlier years.

Note:
NAACCR recognizes that available definitions and abstracting instructions for the data items Name--Last and Name--Maiden may be inadequate for describing names used in some cultures, including Hispanic cultures. Explicit instructions have not been provided for entering compound names, with or without hyphens or “De.” Order of names, use of maternal and paternal names, and use of hyphens can vary across cultures. It is likely, too, that abstracting and coding practice for these items varies across registries. Limitations inherent in these definitions should be kept in mind in any use of the data.
COMPUTED ETHNICITY SOURCERevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
2101SEER221 - 221
Alternate Name:
XML NAACCR ID:computedEthnicitySource
PARENT XML ELEMENT:Patient
Description
Code identifying the method used to determine ethnicity as recorded in Computed Ethnicity [200].
Codes
0No match was run, for 1994 and later tumors
1Census Bureau list of Spanish surnames, NOS
21980 Census Bureau list of Spanish surnames
31990 Census Bureau list of Spanish surnames
4GUESS Program
5Combination list including South Florida names
6Combination of Census and other locally generated list
7Combination of Census and GUESS, with or without other lists
8Other type of match
9Unknown type of match
Blank1993 and earlier tumors, no match was run
Note: For SEER, blanks are required for all cases diagnosed before 1994 and blanks are not allowed for any case diagnosed 1994 and after. Other registries may have computed this item for earlier years.
COUNTY AT DX ANALYSISNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
893NAACCR201818150 - 152
Alternate Name:
XML NAACCR ID:countyAtDxAnalysis
PARENT XML ELEMENT:Tumor
Description
County at Diagnosis Analysis Code for the county of the patient's residence at the time the tumor was diagnosed is a derived variable to be used for county and county-based (such as CHSDA) rates and analysis for all cases regardless of year of diagnosis.
Rationale
Historically, we had a single County at DX [90]. However, counties change over time (which impacts our derived variables such as poverty code indicator which don’t directly align with year of diagnosis), and the county reported by the facility does not always match the geocoded county. In the vast majority of cases where geocoded county and reported county differ, the geocoded county is correct. Including additional geocoded county codes for each census year addresses the accuracy of geocoded fields, however, it is cumbersome to pull data from different variables in order to generate county-level rates. Use of this variable ensures the most accurate and appropriate county data is used for calculating county-level rates.

Instructions for Coding
  • This variable can be generated using a standard, NAACCR supplied SAS code (or the logic below). At a minimum, this field should be derived prior to release of data for county-level analysis or rates. Ideally, the variable should be updated whenever there is a change to any county field.
  • If the County At DX Reported [90] AND the County At DX Geocoded associated with the year of diagnosis are the same, the County At DX Analysis county can be pulled from either field.
  • If the County At DX Reported [90] is "999" or NULL AND County At DX Geocoded associated with the year of diagnosis is geocoded (Census Tr Cert [#364 for cases diagnosed through 1999, #365 for cases diagnosed 2000-2009, or #367 for cases diagnosed 2010-2019] = is not null and less than 9), pull the County At DX Geocode associated with the year of diagnosis. Cases diagnosed 1990-1999, pull from County At DX Geocode 1990. Cases diagnosed 2000-2009, pull from County At DX Geocode 2000. Cases diagnosed 2010-2019, pull from County At DX Geocode 2000. Cases diagnosed 2020-2029, pull from County At DX Geocode 2020.
  • If the County At DX Geocoded associated with the year of diagnosis does not equal County At DX Reported [90] AND is a high quality geocode (Census Tr Cert [#364 for cases diagnosed through 1999, #365 for cases diagnosed 2000-2009, or #367 for cases diagnosed 2010-2019] = 1), pull the County At DX Geocode associated with the year of diagnosis. Cases diagnosed 1990-1999, pull from County At DX Geocode 1990. Cases diagnosed 2000-2009, pull from County At DX Geocode 2000. Cases diagnosed 2010-2019, pull from County At DX Geocode 2000. Cases diagnosed 2020-2029, pull from County At DX Geocode 2020.
  • If the County At DX Geocoded associated with the year of diagnosis does not equal County At DX Reported [90] AND is based on a PO Box address (Census Tr Cert [#364 for cases diagnosed through 1999, #365 for cases diagnosed 2000-2009, or #367 for cases diagnosed 2010-2019] = 5), the derived county equals the County At DX Reported [90].
  • If the County At DX Geocoded associated with the year of diagnosis is ungeocoded (Census Tr Cert [#364 for cases diagnosed through 1999, #365 for cases diagnosed 2000-2009, or #367 for cases diagnosed 2010-2019] = blank or 9), the derived county equals the County At DX Reported [90].
  • If the County At DX Geocoded associated with the year of diagnosis does not match County At DX Reported [90] AND a geocode is based on residential addresses but geocoded to the centroid of a zip code (Census Tr Cert [#364 for cases diagnosed through 1999, #365 for cases diagnosed 2000-2009, or #367 for cases diagnosed 2010-2019] = 2-4), manual review is required to resolve the discrepancy. Until manual review can be done, use the County At DX Reported [90].
  • If the patient has multiple tumors, the county codes may be different for each tumor.
  • Detailed standards have not been set for Canadian provinces/territories. Use code 998 for Canadian residents.
Codes
001-997Valid FIPS code
998Known town, city, state, or country of residence but county code not known AND a resident outside of the state of reporting institution (must meet all criteria). Use for Canadian residents.
999The county of the patient is unknown, or the patient is not a United States resident. County is not documented in the patient's medical record.
Note: For U.S. residents, historically, standard codes are those of the FIPS publication Counties and Equivalent Entities of the United States, Its Possessions, and Associated Areas. These FIPS codes (FIPS 6-4) have been replaced by INCITS standard codes; however, there is no impact on this variable as the codes align with the system the Census used for each decennial census and changes will automatically be accounted for during geocoding. County codes issued by the Federal Information Processing Standards (FIPS) publication, Counties and Equivalent Entities of the United States, Its Possessions, and Associated Areas is available in Appendix A.
COUNTY AT DX GEOCODE 1970/80/90Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
943NAACCR201616155 - 157
Alternate Name:County at DX Geocode1990
XML NAACCR ID:countyAtDxGeocode1990
PARENT XML ELEMENT:Tumor
Description
County at Diagnosis 1990 Code for the county of the patient’s residence at the time the tumor was diagnosed is a derived (geocoded) variable based on Census Boundary files from 1990 Decennial Census. This code should be used for county and county-based (such as CHSDA) rates and analysis for all cases diagnosed prior to 2000.
Rationale
Census tracts are areas geographically nested within counties and designated with a 6-digit number code. This 6-digit code is commonly repeated within a state in different counties. Census tract numbers are only unique when paired with the state and the county. Therefore, a tract cannot be accurately identified without knowing the county. Example from Massachusetts: Rural Franklin County contains a tract 040600 with 2010 population 4,612 people. Urban Suffolk County contains a tract 040600 with 2,444 people. The county must be known in order to distinguish between the two tract codes. Because we historically used a single variable for county at diagnosis [90] correct tract codes were frequently paired with the wrong county due to incorrect county assignment during abstracting or a change of county over time. Also, some variables, such as the Census Tr Poverty Indicatr [145] require the use of the decennial Census County codes closest to year of diagnosis and not the decade of year of diagnosis. Using a single county at diagnosis, and using the reported versus geocoded data, may result in erroneous assignment of geographic location as well as invalid links with census data (i.e., population, poverty category, urban/rural designation).

Instructions for Coding
  • This variable is generated through the process of geocoding either during abstracting or at the central registry level.
  • At a minimum, all cases diagnosed through diagnosis year 1999 should have a geocoded County at Diagnosis 1990. Cases diagnosed 1996-1999 must have both County at Diagnosis 1990 and County at Diagnosis 2000 codes for proper assignment of the Census Tract Poverty Indicator [145].
  • If the patient has multiple tumors, geocoded county may be different for each tumor.
  • Do not update this item if the patient's residential county changes. Store updated address information in the affiliated current address data items. Only update based on improved information on the residential address at time of diagnosis. For instance, it is appropriate to correct a county during manual geocoding or a consolidation process.
  • Refer to FORDS for residency rules.
  • PO Box address information should not be used to geocode this data item except in the infrequent case when no other address information is available.
  • Detailed standards have not been set for Canadian provinces/territories. Use code 998 for Canadian residents.
  • Blank "Not geocoded" is allowable for cases diagnosed after 1999. However, it is recommended to have all cases geocoded to a 1990 Census County to allow for both retrospective and cross-sectional analyses.
Codes
001-997County at diagnosis. Valid FIPS code
998Known town, city, state, or country of residence but county code not known AND a resident outside of the state of reporting institution (must meet all criteria). Use this code for Canadian residents.
999County unknown. The county of the patient is unknown, or the patient is not a United States resident. County is not documented in the patient's medical record.
Note: For U.S. residents, historically, standard codes are those of the FIPS publication "Counties and Equivalent Entities of the United States, Its Possessions, and Associated Areas." These FIPS codes (FIPS 6-4) have been replaced by INCITS standard codes; however, there is no impact on this variable as the codes align with the system the Census used for each decennial census and changes will automatically be accounted for during geocoding. County codes issued by the Federal Information Processing Standards (FIPS) publication Counties and Equivalent Entities of the United States, Its Possessions, and Associated Areas is available in Appendix A.
COUNTY AT DX GEOCODE2000Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
953NAACCR201616169 - 171
Alternate Name:
XML NAACCR ID:countyAtDxGeocode2000
PARENT XML ELEMENT:Tumor
Description
Code for the county of the patient's residence at the time the tumor was diagnosed is a derived (geocoded) variable based on Census Boundary files from 2000 Decennial Census. This code should be used for county and county-based (such as CHSDA) rates and analysis for all cases diagnosed in 2000-2009.
Rationale
Census tracts are areas geographically nested within counties and designated with a 6-digit number code. This 6-digit code is commonly repeated within a state in different counties. Census tract numbers are only unique when paired with the state and the county. Therefore, a tract cannot be accurately identified without knowing the county. Example from Massachusetts: Rural Franklin County contains a tract 040600 with 2010 population 4,612 people. Urban Suffolk County contains a tract 040600 with 2,444 people. The county must be known in order to distinguish between the two tract codes. Because we historically used a single variable for county at diagnosis [90], correct tract codes were frequently paired with the wrong county due to incorrect county assignment during abstracting or a change of county over time. Also, some variables, such as the Census Tr Poverty Indicatr [145] require the use of the decennial Census County codes closest to year of diagnosis and not the decade of year of diagnosis. Using a single county at diagnosis, and using the reported versus geocoded data, may result in erroneous assignment of geographic location as well as invalid links with census data (i.e., population, poverty category, urban/rural designation).
 
Instructions for Coding
  • This variable is generated through the process of geocoding either during abstracting or at the central registry level.
  • It is recommended that all cases diagnosed through 2009 have a geocoded County at Diagnosis 2000.
  • At a minimum, all cases diagnosed through 1996-2009 should have a geocoded County at Diagnosis 2000. Cases diagnosed 1996-1999 must have both County at Diagnosis 1990 and County at Diagnosis 2000 codes for proper assignment of the Census Tract Poverty Indicator [145]. Cases diagnosed 2006-2009 must have both County at Diagnosis 2000 and County at Diagnosis 2010 codes for proper assignment of the Census Tract Poverty Indicator [145].
  • If the patient has multiple tumors, geocoded county may be different for each tumor.
  • Do not update this item if the patient’s county of residence changes. Store updated address information in the affiliated current address data items. Only update based on improved information on the residential address at time of diagnosis. For instance, it is appropriate to correct a county during manual geocoding or a consolidation process.
  • PO Box address information should not be used to geocode this data item except in the infrequent case when no other address information is available.
  • Detailed standards have not been set for Canadian provinces/territories. Use code 998 for Canadian residents.
  • Blank "Not geocoded" is allowable for cases diagnosed before 1995 and after 2009. However, it is recommended to have all cases geocoded to a 2000 Census County to allow for both retrospective and cross-sectional analyses.
Codes
001-997County at diagnosis. Valid FIPS code.
998Known town, city, state, or country of residence but county code not known AND a resident outside of the state of reporting institution (must meet all criteria). Use this code for Canadian residents.
999County unknown. The county of the patient is unknown, or the patient is not a United States resident. County is not documented in the patient's medical record.
Note: For U.S. residents, historically, standard codes are those of the FIPS publication "Counties and Equivalent Entities of the United States, Its Possessions, and Associated Areas." These FIPS codes (FIPS 6-4) have been replaced by INCITS standard codes; however, there is no impact on this variable as the codes align with the system the Census used for each decennial census and changes will automatically be accounted for during geocoding. County codes issued by the Federal Information Processing Standards (FIPS) publication Counties and Equivalent Entities of the United States, Its Possessions, and Associated Areas is available in Appendix A.
COUNTY AT DX GEOCODE2010Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
963NAACCR201616182 - 184
Alternate Name:
XML NAACCR ID:countyAtDxGeocode2010
PARENT XML ELEMENT:Tumor
Description
County at Diagnosis 2010 Code for the county of the patient's residence at the time the tumor was diagnosed is a derived (geocoded) variable based on Census Boundary files from 2010 Decennial Census. This code should be used for county and county-based (such as CHSDA) rates and analysis for all cases diagnosed in 2010-2019.
Rationale
Census tracts are areas geographically nested within counties and designated with a 6-digit number code. This 6-digit code is commonly repeated within a state in different counties. Census tract numbers are only unique when paired with the state and the county. Therefore, a tract cannot be accurately identified without knowing the county. Example from Massachusetts: Rural Franklin County contains a tract 040600 with 2010 population 4,612 people. Urban Suffolk County contains a tract 040600 with 2,444 people. The county must be known in order to distinguish between the two tract codes. Because we historically used a single variable for county at diagnosis [90], correct tract codes were frequently paired with the wrong county due to incorrect county assignment during abstracting or a change of county over time. Also, some variables, such as the Census Tr Poverty Indicatr [145] require the use of the decennial Census County codes closest to year of diagnosis and not the decade of year of diagnosis. Using a single county at diagnosis, and using the reported versus geocoded data, may result in erroneous assignment of geographic location as well as invalid links with census data (i.e., population, poverty category, urban/rural designation).

Instructions for Coding
  • This variable is generated through the process of geocoding either during abstracting or at the central registry level.
  • It is recommended that all cases diagnosed through 2019 should have a geocoded County at Diagnosis 2010.
  • At a minimum, all cases diagnosed through 2006-2019 should have a geocoded County at Diagnosis 2010. Cases diagnosed 2006-2009 must have both County at Diagnosis 2000 and County at Diagnosis 2010 codes for proper assignment of the Census Tract Poverty Indicator [145]. Cases diagnosed 2016-2019 must have both County at Diagnosis 2010 and County at Diagnosis 2020 codes for proper assignment of the Census Tract Poverty Indicator [145].
  • If the patient has multiple tumors, geocoded county may be different for each tumor.
  • Do not update this item if the patient's county of residence changes. Store updated address information in the affiliated current address data items. Only update based on improved information on the residential address at time of diagnosis. For instance, it is appropriate to correct a county during manual geocoding or a consolidation process.
  • PO Box address information should not be used to geocode this data item except in the infrequent case when no other address information is available.
  • Detailed standards have not been set for Canadian provinces/territories. Use code 998 for Canadian residents.
  • Blank "Not geocoded" is allowable for cases diagnosed before 2005 and after 2019. However, it is preferred to have all cases geocoded to a 2010 Census County to allow for both retrospective and cross-sectional analyses.
Codes
001-997County at diagnosis. Valid FIPS code.
998Known town, city, state, or country of residence but county code not known AND a resident outside of the state of reporting institution (must meet all criteria). Use this code for Canadian residents.
999County unknown. The county of the patient is unknown, or the patient is not a United States resident. County is not documented in the patient's medical record.
Note: For U.S. residents, historically, standard codes are those of the FIPS publication “Counties and Equivalent Entities of the United States, Its Possessions, and Associated Areas.” These FIPS codes (FIPS 6-4) have been replaced by INCITS standard codes; however, there is no impact on this variable as the codes align with the system the Census used for each decennial census and changes will automatically be accounted for during geocoding. County codes issued by the Federal Information Processing Standards (FIPS) publication Counties and Equivalent Entities of the United States, Its Possessions, and Associated Areas is available in Appendix A.
COUNTY AT DX GEOCODE2020Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
973NAACCR201616195 - 197
Alternate Name:
XML NAACCR ID:countyAtDxGeocode2020
PARENT XML ELEMENT:Tumor
Description
Code for the county of the patient's residence at the time the tumor was diagnosed is a derived (geocoded) variable based on Census Boundary files from 2020 Decennial Census. This code should be used for county and county-based (such as CHSDA) rates and analysis for all cases diagnosed in 2020-2029.
Rationale
Census tracts are areas geographically nested within counties and designated with a 6-digit number code. This 6-digit code is commonly repeated within a state in different counties. Census tract numbers are only unique when paired with the state and the county. Therefore, a tract cannot be accurately identified without knowing the county. Example from Massachusetts: Rural Franklin County contains a tract 040600 with 2010 population 4,612 people. Urban Suffolk County contains a tract 040600 with 2,444 people. The county must be known in order to distinguish between the two tract codes. Because we historically used a single variable for County at DX [90], correct tract codes were frequently paired with the wrong county due to incorrect county assignment during abstracting or a change of county over time. Also, some variables, such as the Census Tr Poverty Indicatr [145] require the use of the decennial Census County codes closest to year of diagnosis and not the decade of year of diagnosis. Using a single county at diagnosis, and using the reported versus geocoded data, may result in erroneous assignment of geographic location as well as invalid links with census data (i.e., population, poverty category, urban/rural designation).

Instructions for Coding
  • This variable is generated through the process of geocoding either during abstracting or at the central registry level.
  • It is recommended that all cases diagnosed through 2029 should have a geocoded County at Diagnosis 2020.
  • At a minimum, all cases diagnosed through 2016-2029 should have a geocoded County at Diagnosis 2020. Cases diagnosed in 2016-2019, must have both County at Diagnosis 2010 and County at Diagnosis 2020 codes for proper assignment of the Census Tr Poverty Indicatr [145].
  • If the patient has multiple tumors, geocoded county may be different for each tumor.
  • Do not update this item if the patient's county of residence changes. Store updated address information in the affiliated current address data items. Only update based on improved information on the residential address at time of diagnosis. For instance, it is appropriate to correct a county during manual geocoding or a consolidation process.
  • PO Box address information should not be used to geocode this data item except in the infrequent case when no other address information is available.
  • If the patient has multiple tumors, the county codes may be different for each tumor.
  • Detailed standards have not been set for Canadian provinces/territories. Use code 998 for Canadian residents.
  • Blank "Not geocoded" is allowable for cases diagnosed before 2015 and after 2029. However, it is preferred to have all cases geocoded to a 2020 Census County to allow for both retrospective and cross-sectional analyses.
Codes
001-997County at diagnosis. Valid FIPS code.
998Outside state/county code unknown. Known town, city, state, or country of residence but county code not known AND a resident outside of the state of reporting institution (must meet all criteria). Use this code for Canadian residents.
999County unknown. The county of the patient is unknown, or the patient is not a United States resident. County is not documented in the patient's medical record.
Note: For U.S. residents, historically, standard codes are those of the FIPS publication "Counties and Equivalent Entities of the United States, Its Possessions, and Associated Areas." These FIPS codes (FIPS 6-4) have been replaced by INCITS standard codes; however, there is no impact on this variable as the codes align with the system the Census used for each decennial census and changes will automatically be accounted for during geocoding. County codes issued by the Federal Information Processing Standards (FIPS) publication Counties and Equivalent Entities of the United States, Its Possessions, and Associated Areas is available in Appendix A.
COUNTY AT DX REPORTEDRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
903FIPS/SEER135 - 137
Alternate Name:County (pre-96 SEER/CoC)
County at Diagnosis (CoC)
County at DX
XML NAACCR ID:countyAtDx
PARENT XML ELEMENT:Tumor
Description
Code for the county of the patients residence at the time of diagnosis as identified by the Reporting Source. For U.S. residents, standard codes are those of the FIPS publication Counties and Equivalent Entities of the United States, Its Possessions, and Associated Areas or their equivalent INCITS codes.

Calculating county and county-based variable rates using this item is not recommended. The more specific, geocoded county items should be used when available.
 
Rationale
This data item may be used for epidemiological purposes. For example, to measure cancer incidence in a particular geographic area.

Instructions for Coding
  • This field is intended to store address information for the patient's physical, residential address. All efforts should be made to find the patient's true street address and postal code, including reviewing relevant sources outside the medical record if available. The county for a PO Box mailing address should only be recorded when no other address information is available in the medical record and no other information sources are available.
  • If the patient has multiple tumors, county at diagnosis may be different for each tumor.
  • Do not update this item if the patient's county of residence changes. Store updated address information in the affiliated current address data items. Only update based on improved information on the residential address at time of diagnosis. For instance, it is appropriate to correct county during a consolidation process.
  • This variable is coded at time of abstracting and is considered less accurate than the derived, geocoded county at diagnosis variables: County at Diagnosis 1990, 2000, 2010, & 2020.
  • Detailed standards have not been set for Canadian provinces/territories. Use code 998 for Canadian residents.
Note: See Appendix A for standard FIPS county codes. See EDITS Table BPLACE.DBF in Appendix B for geocodes used by CoC.

Note:
SEER does not use code 998. CoC uses country geocodes for nonresidents of the United States (see Appendix B) and 998 for residents of other states.
Codes (in addition to FIPS and Geocodes)
001-997Valid FIPS code
998Known town, city, state, or country of residence but county code not known AND a resident outside of the state of reporting institution (must meet all criteria). Use this code for Canadian residents.
999The county of the patient is unknown, or the patient is not a United States resident. County is not documented in the patient's medical record.
Note: For U.S. residents, historically, standard codes are those of the FIPS publication Counties and Equivalent Entities of the United States, Its Possessions, and Associated Areas. These FIPS codes (FIPS 6-4) have been replaced by INCITS standard codes; however, there is no impact on this variable as the codes align with the system the Census used for each decennial census and changes will automatically be accounted for during geocoding. County codes issued by the Federal Information Processing Standards (FIPS) publication Counties and Equivalent Entities of the United States, Its Possessions, and Associated Areas is available in Appendix A.
COUNTY--CURRENTRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
18403NAACCR2864 - 2866
Alternate Name:
XML NAACCR ID:countyCurrent
PARENT XML ELEMENT:Patient
Description
Code for county of patient’s current residence. See Chapter V, Unresolved Issues, for further discussion.

Note:
This item was used by CoC only. CoC recommended use of FIPS codes (see Appendix A). The ROADS Manual also provided for use of geocodes for countries of residence outside the United States and Canada to be used in the county fields.
Rationale
This item may be used in administrative reports to define a referral area.
Codes (in addition to FIPS and geocodes)
998Known town, city, state, or country of residence but county code not known AND a resident outside of the state of reporting institution (must meet all criteria)
999County unknown
Note: This data item is no longer supported by CoC (as of January 1, 2003).
CRC CHECKSUMRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
208110NAACCR199862607 - 2616
Alternate Name:
XML NAACCR ID:crcChecksum
PARENT XML ELEMENT:Tumor
Description
Cyclic Redundancy Code (CRC) CHECKSUM for the NAACCR record in which it resides. A unique value is calculated for each unique record in a NAACCR file. The value is calculated by applying a CRC algorithm to all data fields of the NAACCR record (excluding the CRC CHECKSUM field). Following a transmission, the CRC CHECKSUM can be recalculated and compared with the transmitted CHECKSUM. Identical values indicate an error-free transmission; differing values indicate an error in transmission.

The algorithm recommended by NAACCR is on the NAACCR website at: http://www.naaccr.org. Users must provide recipients of the data with the algorithm used to create the data transmission file. Otherwise, the item should be left blank.
Rationale
The CHECKSUM can be used to determine if a record-level error occurred during transmission and can also be used to correct any such errors. Record-level CRC CHECKSUMs also allow portions of a NAACCR file to be salvaged in the event of a transmission error.
CREATININE PRETREATMENT LAB VALUENew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
38244NAACCR2018181857 - 1860
Alternate Name:
XML NAACCR ID:creatininePretreatmentLabValue
PARENT XML ELEMENT:Tumor
Description
Creatinine Pretreatment Lab Value, an indicator of kidney function is required to calculate the Model for End-Stage Liver Disease (MELD) score, which is used to assign priority for liver transplant.
Rationale
Creatinine Pretreatment Lab Value is a Registry Data Collection Variable in AJCC. This data item was previously collected for Liver, CS SSF# 4.
Codes
0.00.0 milligram/deciliter (mg/dl)
0.0 micromole/liter (umol/L)
0.1-99.90.1-99.9 milligram/deciliter (mg/dl)
0.1-99.9 micromole/liter (umol/L)
(Exact value to nearest tenth of mg/dl or umol/L)
XX.1100 mg/dl or greater
100 umol/L or greater
XX.7Test ordered, results not in chart
XX.8Not applicable: Information not collected for this case
(If this item is required by your standard setter, use of code XX.8 will result in an edit error.)
XX.9Not documented in medical record
Creatinine Pretreatment Lab Value not assessed or unknown if assessed
Each Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.
CREATININE PRETREATMENT UNIT OF MEASURENew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
38251NAACCR2018181861 - 1861
Alternate Name:
XML NAACCR ID:creatininePretreatmentUnitOfMeasure
PARENT XML ELEMENT:Tumor
Description
Creatinine Pretreatment Unit of Measure identifies the unit of measure for the creatinine value measured in blood or serum prior to treatment. Creatinine is commonly measured in units of Milligrams/deciliter (mg/dL) in the United States and Micromoles/liter (umol/L) in Canada and Europe.
Rationale
Creatinine Pretreatment is a Registry Data Collection Variable in AJCC. Creatinine Pretreatment Unit of Measure is needed to identify the unit in which creatinine is measured and was previously collected as Liver, CS SSF# 5.
Codes
1Milligrams/deciliter (mg/dL)
2Micromoles/liter (umol/L)
7Test ordered, results not in chart
8Not applicable: Information not collected for this case
(If this item is required by your standard setter, use of code 8 will result in an edit error.)
9Not documented in medical record
Creatinine unit of measure not assessed or unknown if assessed
Each Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.
CS EXTENSIONRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28103AJCC2003101301 - 1303
Alternate Name:
XML NAACCR ID:csExtension
PARENT XML ELEMENT:Tumor
Description
Identifies contiguous growth (extension) of the primary tumor within the organ of origin or its direct extension into neighboring organs. For certain sites such as ovary, discontinuous metastasis is coded in CS Extension.
Rationale
Tumor extension at diagnosis is a prognostic indicator used by Collaborative Staging to derive some TNM-T codes and some SEER Summary Stage codes.
Codes (See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
Note: For cases diagnosed prior to 2010, this was a 2 character field in CS version 1 which was converted to a 3 character field in CS version 2. Most 2 character codes were converted by adding a zero as the third character. For example, code 05 was usually converted to 050, 10 to 100, 11 to 110, etc. Special codes such as 88 and 99 were usually converted to 888 and 999, respectively.
CS LYMPH NODESRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28303AJCC2003101305 - 1307
Alternate Name:CS Lymph Nodes (SEER EOD)
XML NAACCR ID:csLymphNodes
PARENT XML ELEMENT:Tumor
Description
Identifies the regional lymph nodes involved with cancer at the time of diagnosis.
Rationale
The involvement of specific regional lymph nodes is a prognostic indicator used by Collaborative Staging to derive some TNM-N codes and SEER Summary Stage codes.
Codes (See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
Note: For cases prior to 2010, this was a 2 character field in CS version 1 which was converted to a 3 character field in CS version 2. Most 2 character codes were converted by adding a zero as the third character. For example, code 05 was usually converted to 050, 10 to 100, 11 to 110, etc. Special codes such as 88 and 99 were usually converted to 888 and 999 respectively.
CS LYMPH NODES EVALRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28401AJCC1308 - 1308
Alternate Name:CS Regional Nodes Evaluation
CS Reg Nodes Eval
XML NAACCR ID:csLymphNodesEval
PARENT XML ELEMENT:Tumor
Description
Records how the code for CS Lymph Nodes [2830] was determined, based on the diagnostic methods employed.
Rationale
This data item is used by Collaborative Staging to describe whether the staging basis for the TNM-N code is clinical or pathological and to record applicable prefix and suffix descriptors used with TNM staging.
Codes (See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS METS AT DXRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28502AJCC2003101309 - 1310
Alternate Name:CS Metastasis at Diagnosis
XML NAACCR ID:csMetsAtDx
PARENT XML ELEMENT:Tumor
Description
Identifies the distant site(s) of metastatic involvement at time of diagnosis.
Rationale
The presence of metastatic disease at diagnosis is an independent prognostic indicator, and it is used by Collaborative Staging to derive TNM-M codes and SEER Summary Stage codes.
Codes (See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS METS AT DX-BONERevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28511AJCC2010121312 - 1312
Alternate Name:
XML NAACCR ID:csMetsAtDxBone
PARENT XML ELEMENT:Tumor
Description
Identifies the presence of distant metastatic involvement of bone at time of diagnosis.
Rationale
The presence of metastatic bone disease at diagnosis is an independent prognostic indicator, and it is used by Collaborative Staging to derive TNM-M codes and SEER Summary Stage codes for some sites.
Codes (See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
Note: This includes only the bone, not the bone marrow.
CS METS AT DX-BRAINRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28521AJCC2010121313 - 1313
Alternate Name:
XML NAACCR ID:csMetsAtDxBrain
PARENT XML ELEMENT:Tumor
Description
The presence of metastatic brain disease at diagnosis is an independent prognostic indicator, and it is used by Collaborative Staging to derive TNM-M codes and SEER Summary Stage codes for some sites.
Rationale
The presence of metastatic brain disease at diagnosis is an independent prognostic indicator, and it is used by Collaborative Staging to derive TNM-M codes and SEER Summary Stage codes for some sites.
Codes (See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
Note: This includes only the brain, not spinal cord or other parts of the central nervous system.
CS METS AT DX-LIVERRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28531AJCC2010121314 - 1314
Alternate Name:
XML NAACCR ID:csMetsAtDxLiver
PARENT XML ELEMENT:Tumor
Description
Identifies the presence of distant metastatic involvement of the liver at time of diagnosis.
Rationale
The presence of metastatic liver disease at diagnosis is an independent prognostic indicator, and it is used by Collaborative Staging to derive TNM-M codes and SEER Summary Stage codes for some sites.
Codes (See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
Note: This includes only the liver.
CS METS AT DX-LUNGRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28541AJCC2010121315 - 1315
Alternate Name:
XML NAACCR ID:csMetsAtDxLung
PARENT XML ELEMENT:Tumor
Description
Identifies the presence of distant metastatic involvement of the lung at time of diagnosis.
Rationale
The presence of metastatic lung disease at diagnosis is an independent prognostic indicator, and it is used by Collaborative Staging to derive TNM-M codes and SEER Summary Stage codes for some sites.
Codes (See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
Note: This includes only the lung, not pleura or pleural fluid.
CS METS EVALRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28601AJCC2003101311 - 1311
Alternate Name:CS Metastasis Evaluation
XML NAACCR ID:csMetsEval
PARENT XML ELEMENT:Tumor
Description
Records how the code for CS Mets at Dx [2850] was determined based on the diagnostic methods employed.
Rationale
This data item is used by Collaborative Staging to describe whether the staging basis for the TNM-M code is clinical or pathological and to record applicable prefix and suffix descriptors used with TNM staging.
Codes (See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS POSTRX EXTENSIONRetired
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
2775201012201818
Alternate Name:
XML NAACCR ID:
PARENT XML ELEMENT:
CS POSTRX LYMPH NODESRetired
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
2780201012201818
Alternate Name:
XML NAACCR ID:
PARENT XML ELEMENT:
CS POSTRX METS AT DXRetired
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
2785201818
Alternate Name:
XML NAACCR ID:
PARENT XML ELEMENT:
CS POSTRX TUMOR SIZERetired
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
2770201012201818
Alternate Name:
XML NAACCR ID:
PARENT XML ELEMENT:
CS PRERX EXTENSIONRetired
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
2735201012201818
Alternate Name:
XML NAACCR ID:
PARENT XML ELEMENT:
CS PRERX LYMPH NODESRetired
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
2750201012201818
Alternate Name:
XML NAACCR ID:
PARENT XML ELEMENT:
CS PRERX METS AT DXRetired
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
2760201012201818
Alternate Name:
XML NAACCR ID:
PARENT XML ELEMENT:
CS PRERX METS EVALRetired
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
2765201012201818
Alternate Name:
XML NAACCR ID:
PARENT XML ELEMENT:
CS PRERX REG NODES EVALRetired
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
2755201012201818
Alternate Name:
XML NAACCR ID:
PARENT XML ELEMENT:
CS PRERX TUM SZ/EXT EVALRetired
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
2740201012201818
Alternate Name:
XML NAACCR ID:
PARENT XML ELEMENT:
CS PRERX TUMOR SIZERetired
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
2730201012201818
Alternate Name:
XML NAACCR ID:
PARENT XML ELEMENT:
CS SITE-SPECIFIC FACTOR 1Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28803AJCC2003101316 - 1318
Alternate Name:
XML NAACCR ID:csSiteSpecificFactor1
PARENT XML ELEMENT:Tumor
Description
Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.
Rationale
Site-specific factors are used to record additional staging information needed by Collaborative Staging to derive TNM and/or SEER Summary Stage codes for particular site-histology schema.
Codes (The information recorded in CS Site-Specific Factor 1 differs for each anatomic site. See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS SITE-SPECIFIC FACTOR 2Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28903AJCC2003101319 - 1321
Alternate Name:
XML NAACCR ID:csSiteSpecificFactor2
PARENT XML ELEMENT:Tumor
Description
Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.
Rationale
Site-specific factors are used to record additional staging information needed by Collaborative Staging to derive TNM and/or SEER Summary Stage codes for particular site-histology schema.
Codes (The information recorded in CS Site-Specific Factor 2 differs for each anatomic site. See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS SITE-SPECIFIC FACTOR 3Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
29003AJCC2003101322 - 1324
Alternate Name:
XML NAACCR ID:csSiteSpecificFactor3
PARENT XML ELEMENT:Tumor
Description
Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.
Rationale
Site-specific factors are used to record additional staging information needed by Collaborative Staging to derive TNM and/or SEER Summary Stage codes for particular site-histology schema.
Codes (The information recorded in CS Site-Specific Factor 3 differs for each anatomic site. See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS SITE-SPECIFIC FACTOR 4Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
29103AJCC2003101325 - 1327
Alternate Name:
XML NAACCR ID:csSiteSpecificFactor4
PARENT XML ELEMENT:Tumor
Description
Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.
Rationale
Site-specific factors are used to record additional staging information needed by Collaborative Staging to derive TNM and/or SEER Summary Stage codes for particular site-histology schema.
Codes (The information recorded in CS Site-Specific Factor 4 differs for each anatomic site. See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS SITE-SPECIFIC FACTOR 5Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
29203AJCC2003101328 - 1330
Alternate Name:
XML NAACCR ID:csSiteSpecificFactor5
PARENT XML ELEMENT:Tumor
Description
Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.
Rationale
Site-specific factors are used to record additional staging information needed by Collaborative Staging to derive TNM and/or SEER Summary Stage codes for particular site-histology schema.
Codes (The information recorded in CS Site-Specific Factor 5 differs for each anatomic site. See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS SITE-SPECIFIC FACTOR 6Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
29303AJCC2003101331 - 1333
Alternate Name:
XML NAACCR ID:csSiteSpecificFactor6
PARENT XML ELEMENT:Tumor
Description
Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.
Rationale
Site-specific factors are used to record additional staging information needed by Collaborative Staging to derive TNM and/or SEER Summary Stage codes for particular site-histology schema.
Codes (The information recorded in CS Site-Specific Factor 6 differs for each anatomic site. See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS SITE-SPECIFIC FACTOR 7Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28613AJCC2010121334 - 1336
Alternate Name:
XML NAACCR ID:csSiteSpecificFactor7
PARENT XML ELEMENT:Tumor
Description
Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.
Rationale
Site-specific factors are used to record additional staging information needed by Collaborative Staging to derive TNM and/or SEER Summary Stage codes for particular site-histology schema.
Codes (The information recorded in CS Site-Specific Factor 7 differs for each anatomic site. See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS SITE-SPECIFIC FACTOR 8Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28623AJCC2010121337 - 1339
Alternate Name:
XML NAACCR ID:csSiteSpecificFactor8
PARENT XML ELEMENT:Tumor
Description
Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.
Rationale
Site-specific factors are used to record additional staging information needed by Collaborative Staging to derive TNM and/or SEER Summary Stage codes for particular site-histology schema.
Codes (The information recorded in CS Site-Specific Factor 8 differs for each anatomic site. See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS SITE-SPECIFIC FACTOR 9Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28633AJCC2010121340 - 1342
Alternate Name:
XML NAACCR ID:csSiteSpecificFactor9
PARENT XML ELEMENT:Tumor
Description
Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.
Rationale
Site-specific factors are used to record additional staging information needed by Collaborative Staging to derive TNM and/or SEER Summary Stage codes for particular site-histology schema.
Codes (The information recorded in CS Site-Specific Factor 9 differs for each anatomic site. See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS SITE-SPECIFIC FACTOR10Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28643AJCC2010121343 - 1345
Alternate Name:
XML NAACCR ID:csSiteSpecificFactor10
PARENT XML ELEMENT:Tumor
Description
Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.
Rationale
Site-specific factors are used to record additional staging information needed by Collaborative Staging to derive TNM and/or SEER Summary Stage codes for particular site-histology schema.
Codes (The information recorded in CS Site-Specific Factor10 differs for each anatomic site. See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS SITE-SPECIFIC FACTOR11Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28653AJCC2010121346 - 1348
Alternate Name:
XML NAACCR ID:csSiteSpecificFactor11
PARENT XML ELEMENT:Tumor
Description
Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.
Rationale
Site-specific factors are used to record additional staging information needed by Collaborative Staging to derive TNM and/or SEER Summary Stage codes for particular site-histology schema.
Codes (The information recorded in CS Site-Specific Factor11 differs for each anatomic site. See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS SITE-SPECIFIC FACTOR12Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28663AJCC2010121349 - 1351
Alternate Name:
XML NAACCR ID:csSiteSpecificFactor12
PARENT XML ELEMENT:Tumor
Description
Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.
Rationale
Site-specific factors are used to record additional staging information needed by Collaborative Staging to derive TNM and/or SEER Summary Stage codes for particular site-histology schema.
Codes (The information recorded in CS Site-Specific Factor12 differs for each anatomic site. See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS SITE-SPECIFIC FACTOR13Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28673AJCC2010121352 - 1354
Alternate Name:
XML NAACCR ID:csSiteSpecificFactor13
PARENT XML ELEMENT:Tumor
Description
Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.
Rationale
Site-specific factors are used to record additional staging information needed by Collaborative Staging to derive TNM and/or SEER Summary Stage codes for particular site-histology schema.
Codes (The information recorded in CS Site-Specific Factor13 differs for each anatomic site. See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS SITE-SPECIFIC FACTOR14Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28683AJCC2010121355 - 1357
Alternate Name:
XML NAACCR ID:csSiteSpecificFactor14
PARENT XML ELEMENT:Tumor
Description
Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.
Rationale
Site-specific factors are used to record additional staging information needed by Collaborative Staging to derive TNM and/or SEER Summary Stage codes for particular site-histology schema.
Codes (The information recorded in CS Site-Specific Factor14 differs for each anatomic site. See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS SITE-SPECIFIC FACTOR15Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28693AJCC2010121358 - 1360
Alternate Name:
XML NAACCR ID:csSiteSpecificFactor15
PARENT XML ELEMENT:Tumor
Description
Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.
Rationale
Site-specific factors are used to record additional staging information needed by Collaborative Staging to derive TNM and/or SEER Summary Stage codes for particular site-histology schema.
Codes (The information recorded in CS Site-Specific Factor15 differs for each anatomic site. See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS SITE-SPECIFIC FACTOR16Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28703AJCC2010121361 - 1363
Alternate Name:
XML NAACCR ID:csSiteSpecificFactor16
PARENT XML ELEMENT:Tumor
Description
Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.
Rationale
Site-specific factors are used to record additional staging information needed by Collaborative Staging to derive TNM and/or SEER Summary Stage codes for particular site-histology schema.
Codes (The information recorded in CS Site-Specific Factor16 differs for each anatomic site. See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS SITE-SPECIFIC FACTOR17Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28713AJCC2010121364 - 1366
Alternate Name:
XML NAACCR ID:csSiteSpecificFactor17
PARENT XML ELEMENT:Tumor
Description
Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.
Rationale
Site-specific factors are used to record additional staging information needed by Collaborative Staging to derive TNM and/or SEER Summary Stage codes for particular site-histology schema.
Codes (The information recorded in CS Site-Specific Factor17 differs for each anatomic site. See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS SITE-SPECIFIC FACTOR18Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28723AJCC2010121367 - 1369
Alternate Name:
XML NAACCR ID:csSiteSpecificFactor18
PARENT XML ELEMENT:Tumor
Description
Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.
Rationale
Site-specific factors are used to record additional staging information needed by Collaborative Staging to derive TNM and/or SEER Summary Stage codes for particular site-histology schema.
Codes (The information recorded in CS Site-Specific Factor18 differs for each anatomic site. See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS SITE-SPECIFIC FACTOR19Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28733AJCC2010121370 - 1372
Alternate Name:
XML NAACCR ID:csSiteSpecificFactor19
PARENT XML ELEMENT:Tumor
Description
Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.
Rationale
Site-specific factors are used to record additional staging information needed by Collaborative Staging to derive TNM and/or SEER Summary Stage codes for particular site-histology schema.
Codes (The information recorded in CS Site-Specific Factor19 differs for each anatomic site. See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS SITE-SPECIFIC FACTOR20Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28743AJCC2010121373 - 1375
Alternate Name:
XML NAACCR ID:csSiteSpecificFactor20
PARENT XML ELEMENT:Tumor
Description
Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.
Rationale
Site-specific factors are used to record additional staging information needed by Collaborative Staging to derive TNM and/or SEER Summary Stage codes for particular site-histology schema.
Codes (The information recorded in CS Site-Specific Factor20 differs for each anatomic site. See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS SITE-SPECIFIC FACTOR21Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28753AJCC2010121376 - 1378
Alternate Name:
XML NAACCR ID:csSiteSpecificFactor21
PARENT XML ELEMENT:Tumor
Description
Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.
Rationale
Site-specific factors are used to record additional staging information needed by Collaborative Staging to derive TNM and/or SEER Summary Stage codes for particular site-histology schema.
Codes (The information recorded in CS Site-Specific Factor21 differs for each anatomic site. See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS SITE-SPECIFIC FACTOR22Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28763AJCC2010121379 - 1381
Alternate Name:
XML NAACCR ID:csSiteSpecificFactor22
PARENT XML ELEMENT:Tumor
Description
Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.
Rationale
Site-specific factors are used to record additional staging information needed by Collaborative Staging to derive TNM and/or SEER Summary Stage codes for particular site-histology schema.
Codes (The information recorded in CS Site-Specific Factor22 differs for each anatomic site. See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS SITE-SPECIFIC FACTOR23Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28773AJCC2010121382 - 1384
Alternate Name:
XML NAACCR ID:csSiteSpecificFactor23
PARENT XML ELEMENT:Tumor
Description
Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.
Rationale
Site-specific factors are used to record additional staging information needed by Collaborative Staging to derive TNM and/or SEER Summary Stage codes for particular site-histology schema.
Codes (The information recorded in CS Site-Specific Factor23 differs for each anatomic site. See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS SITE-SPECIFIC FACTOR24Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28783AJCC2010121385 - 1387
Alternate Name:
XML NAACCR ID:csSiteSpecificFactor24
PARENT XML ELEMENT:Tumor
Description
Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.
Rationale
Site-specific factors are used to record additional staging information needed by Collaborative Staging to derive TNM and/or SEER Summary Stage codes for particular site-histology schema.
Codes (The information recorded in CS Site-Specific Factor24 differs for each anatomic site. See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS SITE-SPECIFIC FACTOR25Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28793AJCC2010121388 - 1390
Alternate Name:
XML NAACCR ID:csSiteSpecificFactor25
PARENT XML ELEMENT:Tumor
Description
Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.
Rationale
CS Site-Specific Factor25 is used to discriminate between CS staging schema or between AJCC chapters where site and histology alone are insufficient to identify the tumor type or location to identify the applicable staging method.
Codes (The information recorded in CS Site-Specific Factor25 differs for each anatomic site. See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS TUMOR SIZERevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28003AJCC2003101298 - 1300
Alternate Name:
XML NAACCR ID:csTumorSize
PARENT XML ELEMENT:Tumor
Description
Records the largest dimension or diameter of the primary tumor in millimeters.
Rationale
Tumor size at diagnosis is an independent prognostic indicator for many tumors and it is used by Collaborative Staging to derive some TNM-T codes.
Codes (See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS TUMOR SIZE/EXT EVALRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28201AJCC2003101304 - 1304
Alternate Name:CS Tumor Size/Extension Evaluation
CS TS/Ext-Eval
XML NAACCR ID:csTumorSizeExtEval
PARENT XML ELEMENT:Tumor
Description
Records how the codes for the two items CS Tumor Size [2800] and CS Extension [2810] were determined, based on the diagnostic methods employed.
Rationale
This item is used by Collaborative Staging to describe whether the staging basis for the TNM-T code is clinical or pathological and to record applicable prefix and suffix descriptors used with TNM staging.
Codes (See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS VERSION DERIVEDRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
29366AJCC1514 - 1519
Alternate Name:CS Version Latest
XML NAACCR ID:csVersionDerived
PARENT XML ELEMENT:Tumor
Description
This data item is recorded the first time the CS output fields are derived and should be updated each time the CS Derived items are recomputed. The CS version number is returned as part of the output of the CS algorithm.
Rationale
The CS algorithm may be re-applied to compute the CS Derived items; for example, when the data are to be used for a special study, transmitted, or when an updated CS algorithm is produced. This item identifies the specific algorithm used to obtain the CS Derived values in the data record.
Codes (See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS Version Derived is a 6-digit code (e.g., 010100). The first two digits represent the major version number; the second two digits represent minor version changes; and, the last two digits represent even less significant changes, such as corrections of typographical errors that do not affect coding or derivation results.

This item should not be blank if the CS Derived items contain values. It should be blank if the CS Derived items are empty or the CS algorithm has not been applied.
CS VERSION INPUT CURRENTRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
29376AJCC2010121502 - 1507
Alternate Name:
XML NAACCR ID:csVersionInputCurrent
PARENT XML ELEMENT:Tumor
Description
This item indicates the version of CS input fields after they have been updated or recoded. This data item is recorded the first time the CS input fields are entered and should be updated each time the CS input fields are modified.
Rationale
Over time, the input codes and instructions for CS items may change. This item identifies the correct interpretation of input CS items.
Codes (See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS Version Input Current is a 6-digit code (e.g., 020100). The first two digits represent the major version number; the second two digits represent minor version changes; and, the last two digits represent even less significant changes, such as corrections of typographical errors that do not affect coding or derivation of results.
CS VERSION INPUT ORIGINALRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
29356AJCC1508 - 1513
Alternate Name:CS Version 1ST
XML NAACCR ID:csVersionInputOriginal
PARENT XML ELEMENT:Tumor
Description
This item indicates the number of the version initially used to code Collaborative Staging (CS) fields. The CS version number is returned as part of the output of the CS algorithm.
Rationale
Over time, the input codes and instructions for CS items may change. This item identifies the correct interpretation of input CS items.
Codes (See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS Version Input Original is a 6-digit code (e.g., 010100). The first two digits represent the major version number; the second two digits represent minor version changes; and, the last two digits represent even less significant changes, such as corrections of typographical errors that do not affect coding or derivation of results.
DATE 1ST CRS RX COCRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
12708CoC2104 - 2111
Alternate Name:Date Started (pre 96 CoC)
Date of First Course Treatment (CoC)
Date of 1st Crs RX--CoC
XML NAACCR ID:date1stCrsRxCoc
PARENT XML ELEMENT:Tumor
Description
Date of initiation of the first therapy for the cancer being reported, using the CoC definition of first course. The date of first treatment includes the date a decision was made not to treat the patient. See STORE for details. See Chapter V, Unresolved Issues for further discussion of the difference between SEER and CoC items. See Chapter X for date format. Use Date 1st Crs RX CoC Flag [1271] if there is no appropriate or known date for this item.
 
Formerly Date of 1st Crs RX--CoC.
Clarification of NPCR Required Status
Central registries funded by NPCR are required to collect either Date Initial RX SEER [1260] or Date 1st Crs RX CoC [1270].
DATE 1ST CRS RX COC FLAGRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
12712NAACCR2010122112 - 2113
Alternate Name:Date of 1st Crs Rx Flag
XML NAACCR ID:date1stCrsRxCocFlag
PARENT XML ELEMENT:Tumor
Description
This flag explains why no appropriate value is in the field, Date 1st Crs RX CoC [1270].
 
Formerly Date of 1st Crs Rx Flag.
Rationale
Before Version 12 (through 2009 diagnosis), date fields included codes that provided information other than dates. As part of an initiative to standardize date fields, new fields were introduced to accommodate non-date information that had previously been transmitted in date fields.
Codes (See Appendix H for the complete Flavors of Null table, which includes the NAACCR codes, HL7 codes and definitions.)
10No information whatsoever can be inferred from this exceptional value (e.g, unknown whether treatment was administered)
11No proper value is applicable in this context (Autopsy only)
12A proper value is applicable but not known (e.g., treatment administered but date is unknown)
BlankA valid date value is provided in item Date 1st Crs RX CoC [1270], or the date was not expected to have been transmitted
Comment: This is part of the initiative of the transformation from the old NAACCR date standards to interoperable dates.
DATE CASE COMPLETEDRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
20908NAACCR2648 - 2655
Alternate Name:
XML NAACCR ID:dateCaseCompleted
PARENT XML ELEMENT:Tumor
Description
The date that: (1) the abstractor decided that the tumor report was complete and (2) the case passed all edits that were applied. Definitions may vary among registries and software providers. This field is locally used by central registries. See Chapter X for date format. Standard edits check that no dates are later than the current date. These specifications will not necessarily be the same as those used for Date Case Completed--CoC [2092].
DATE CASE COMPLETED--COCRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
20928CoC2010122656 - 2663
Alternate Name:
XML NAACCR ID:dateCaseCompletedCoc
PARENT XML ELEMENT:Tumor
Description
Identifies the date that specified items are completed, based on the Class of Case, where those items pass the relevant edits. Follow-up information, including delayed treatment received elsewhere, may be coded after the Date Case Completed--CoC. See the current STORE for details. This item should be autocoded by the registry software; specifications may be obtained from NCDB. The CoC specifications will not necessarily be the same as those used for Date Case Completed [2090]. See Chapter X for date format.
DATE CASE INITIATEDRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
20858NAACCR2010122640 - 2647
Alternate Name:
XML NAACCR ID:dateCaseInitiated
PARENT XML ELEMENT:Tumor
Description
Date the electronic abstract is initiated in the reporting facility's cancer registry database. See Chapter X for date format. Standard edits check that no dates are later than the current date or the date completed.
Rationale
This item is used to assess and monitor the timeliness of reporting. Timeliness of abstracting (and reporting) is a concern for all standard-setting organizations and consequently, timeliness standards have been established. Examples of use are as follows:
  • This item can be used with the Date of 1stContact [580] to measure timeliness of abstracting by individual reporting facilities.
  • This item can be used with Date Case Report Exported [2110] to determine the "residency time" of a case report within a reporting facility's database prior to data transmission to a central cancer registry.
  • This item can be used with Date Case Report Received [2111] to monitor central registry timeliness in entering case reports (for case reports abstracted in-house from hardcopy provided by a reporting facility).
  • This item can be used with Date Case Completed [2090] to monitor timeliness of case report completion.
DATE CASE LAST CHANGEDRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
21008NAACCR2664 - 2671
Alternate Name:
XML NAACCR ID:dateCaseLastChanged
PARENT XML ELEMENT:Tumor
Description
Date the case was last changed or updated. See Chapter X for date format. Standard edits check that no dates are later than the current date.
DATE CASE REPORT EXPORTEDRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
21108NPCR2672 - 2679
Alternate Name:Date Case Transmitted (pre-98 NAACCR)
XML NAACCR ID:dateCaseReportExported
PARENT XML ELEMENT:Tumor
Description
Date the reporting facility exports the electronic abstract to a file for transmission to the central registry. See Chapter X for date format. Standard edits check that no dates are later than the current date. Definitions may vary among registries and software providers.
DATE CASE REPORT LOADEDRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
21128NPCR19975.12688 - 2695
Alternate Name:
XML NAACCR ID:dateCaseReportLoaded
PARENT XML ELEMENT:Tumor
Description
Date the tumor report is loaded into a central registry computerized processing file for initiation of quality control activities (e.g., visual editing, application of computerized edits, etc.). See Chapter X for date format.
DATE CASE REPORT RECEIVEDRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
21118NPCR19975.12680 - 2687
Alternate Name:
XML NAACCR ID:dateCaseReportReceived
PARENT XML ELEMENT:Tumor
Description
Date the abstract (or source record) is received by the central cancer registry for the respective tumor. If multiple reports are received from two or more sources and if a single date is needed, use the date the first abstract (or source record) was received from any source. See Chapter X for date format.
Rationale
This item is used to assess and monitor the timeliness of reporting. Timeliness of abstracting (and reporting) is a concern for all standard-setting organizations. This item can be used with the Date of 1st Contact [580] or the Path--Date of Specimen Collection [7320] to measure timeliness of reporting to central cancer registries by individual reporting facilities. This data item also can be used with the Date Tumor Record Availbl [2113] to measure timeliness of processing within the central cancer registry.
DATE CONCLUSIVE DXRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
4438SEER200611581 - 588
Alternate Name:Date of Conclusive Diagnosis
Date of Conclusive Terminology
Date of Conclusive DX
XML NAACCR ID:dateConclusiveDx
PARENT XML ELEMENT:Tumor
Description
Documents the date when a conclusive cancer diagnosis (definite statement of malignancy) is made following an initial diagnosis that was based only on ambiguous terminology. See Chapter X for date format. Use DATE CONCLUSIVE DX FLAG [448] if there is no appropriate or known date for this item.
 
Formerly Date of Conclusive DX.
Rationale
This date will allow analysis of the primary site locations and frequency of cases that were originally diagnosed by ambiguous terminology and later confirmed by other conclusive method.

This date will also allow for analysis of the time interval between cancer diagnosis based on ambiguous terminology and confirmation of the cancer diagnosis by conclusive means.
Codes (refer to http://seer.cancer.gov/tools/mphrules/index.html for additional instructions).
DATE CONCLUSIVE DX FLAGRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
4482NAACCR201012589 - 590
Alternate Name:
XML NAACCR ID:dateConclusiveDxFlag
PARENT XML ELEMENT:Tumor
Description
This flag explains why no appropriate value is in the field, Date Conclusive DX [443]. This data item was first available in Volume II Version 12.
Rationale
Before Version 12, date fields included codes that provided information other than dates. As part of an initiative to standardize date fields, new fields were introduced to accommodate non-date information that had previously been transmitted in date fields.
Codes (See Appendix H for the complete Flavors of Null table, which includes the NAACCR codes, HL7 codes and definitions.)
10No information whatsoever can be inferred from this exceptional (non-date) value. (e.g., unknown if the diagnosis was initially based on ambiguous terminology).
11No proper value is applicable in this context. (e.g., not applicable, initial diagnosis made by unambiguous terminology (Code 0 in data item Ambiguous Terminology DX [442]).
12A proper value is applicable but not known (e.g., the initial ambiguous diagnosis was followed by a conclusive term, but the date of the conclusive term is unknown).
15Information is not available at this time, but it is expected that it will be available later (e.g., accessioned based on ambiguous terminology only (Code 1 in data item Ambiguous Terminology DX [442]).
BlankA valid date value is provided in item Date Conclusive DX [443], or the date was not expected to have been transmitted.
Comment: This is part of the initiative of the transformation from the old NAACCR date standards to interoperable dates.
DATE INITIAL RX SEERRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
12608SEER2094 - 2101
Alternate Name:Date Therapy Initiated (SEER)
Date Started (SEER)
Date of Initial RX--SEER
XML NAACCR ID:dateInitialRxSeer
PARENT XML ELEMENT:Tumor
Description
Date of initiation of the first course therapy for the tumor being reported, using the SEER definition of first course. See also Date 1st Crs RX CoC [1270]. See Chapter V, Unresolved Issues, for further discussion of the difference between SEER and CoC items. See Chapter X for date format. Use Date Initial RX SEER Flag [1261] if there is no appropriate or known date for this item.
 
Formerly Date of Initial RX--SEER.
Clarification of NPCR Required Status
Central registries funded by NPCR are required to collect either Date Initial RX SEER [1260] or Date 1st Crs RX CoC [1270].
DATE INITIAL RX SEER FLAGRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
12612NAACCR2010122102 - 2103
Alternate Name:Date of Initial RX Flag
XML NAACCR ID:dateInitialRxSeerFlag
PARENT XML ELEMENT:Tumor
Description
This flag explains why no appropriate value is in the field, Date Initial RX SEER [1260].
 
Formerly Date of Initial RX Flag.
Rationale
Before Version 12 (through 2009 diagnosis), date fields included codes that provided information other than dates. As part of an initiative to standardize date fields, new fields were introduced to accommodate non-date information that had previously been transmitted in date fields.
Codes (See Appendix H for the complete Flavors of Null table, which includes the NAACCR codes, HL7 codes and definitions.)
10No information whatsoever can be inferred from this exceptional value (e.g, unknown if therapy was administered)
11No proper value is applicable in this context (e.g., therapy was not administered)
12A proper value is applicable but not known (e.g., therapy was administered and date is unknown)
BlankA valid date value is provided in item Date Initial RX SEER [1260], or the date was not expected to have been transmitted
Comment: This is part of the initiative of the transformation from the old NAACCR date standards to interoperable dates.
DATE OF 1ST CONTACTRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
5808CoC759 - 766
Alternate Name:Date of Adm/First Contact
XML NAACCR ID:dateOf1stContact
PARENT XML ELEMENT:Tumor
Description
Date of first patient contact, as inpatient or outpatient, with the reporting facility for the diagnosis and/or treatment of the tumor. The date may represent the date of an outpatient visit for a biopsy, x-ray, scan, or laboratory test. See Chapter X for date format.

When pathology-specimen-only tumors are collected (Class of Case 43, Type of Reporting Source 3), the date of specimen collection from the pathology report should be used as the Date of 1st Contact. If a pathology-specimen-only case is followed by patient contact with a facility for diagnosis and/or treatment of the respective tumor, ACoS coding rules require the hospital registry to change the Date of 1st Contact to reflect the date the patient first registered at that facility. Central registries, however, should retain the earlier date in their consolidated files, as that shows the patient’s first recorded contact with the healthcare system for this disease.

When death certificate only (Class of Case 49, Type of Reporting Source 7) tumors are collected, the date of death should be used as the Date of 1st Contact. When Autopsy Only (Class of Case 38, Type of Reporting Source 6) tumors are collected, the date of death should be used as the Date of 1st Contact.
Rationale
Timeliness of abstracting (and reporting) is a concern for all standard-setting organizations. Date of 1st Contact is one of several data items that can be used to measure timeliness of reporting to central cancer registries by individual facilities. For tumors that are not diagnosed at the reporting facility following its Reference Date (Class of Case 20-22, 30-37), the Date of 1st Contact [580] can be used in conjunction with the Date Case Report Received [2111] to measure timeliness of reporting by individual facilities.
Comment: To accurately measure the timeliness of data collection and submission of abstracts that are first diagnosed at autopsy (Class of Case 38, Type of Reporting Source 6) the date of death should be used as the Date of 1st Contact since the diagnosis was not determined until the autopsy was performed. Death Certificate Only cases (Class of Case 49, Type of Reporting Source 7) are created only by the central registry. For these cases, Date of 1st Contact should be filled with the date of death, and timeliness for DCO cases should be measured by different criteria.
DATE OF 1ST CONTACT FLAGRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
5812NAACCR201012767 - 768
Alternate Name:Date of First Contact Flag
XML NAACCR ID:dateOf1stContactFlag
PARENT XML ELEMENT:Tumor
Description
This flag explains why no appropriate value is in the field Date of 1st Contact [580]. This data item was first available in Volume II Version 12.
Rationale
Before Version 12 (through 2009 diagnosis), date fields included codes that provided information other than dates. As part of an initiative to standardize date fields, new fields were introduced to accommodate non-date information that had previously been transmitted in date fields.
Codes (See Appendix H for the complete Flavors of Null table, which includes the NAACCR codes, HL7 codes and definitions.)
12A proper value is applicable but not known (e.g., date of 1st contact is unknown)
BlankA valid date value is provided in item Date of 1st Contact [580], or the date was not expected to have been transmitted
Comment: This is part of the initiative of the transformation from the old NAACCR date standards to interoperable dates.
DATE OF 1ST POSITIVE BXRetired
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
1080201012
Alternate Name:
XML NAACCR ID:
PARENT XML ELEMENT:
Description
The NAACCR UDSC retired this data item in Version 12, as of January 1, 2010.
DATE OF BIRTHRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
2408SEER/CoC226 - 233
Alternate Name:Birth Date(SEER/CoC/CCCR)
XML NAACCR ID:dateOfBirth
PARENT XML ELEMENT:Patient
Description
Date of birth of the patient. See Chapter X for date format. If age at diagnosis and year of diagnosis are known, but year of birth is unknown, then year of birth should be calculated and so coded. Only the year should be entered, left-justified. Estimate date of birth when information is not available. It is better to estimate than to leave birth date unknown.
DATE OF BIRTH FLAGRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
2412NAACCR201012234 - 235
Alternate Name:
XML NAACCR ID:dateOfBirthFlag
PARENT XML ELEMENT:Patient
Description
This flag explains why no appropriate value is in the field, Date of Birth [240]. This data item was first available in Volume II Version 12.
Rationale
Before Version 12 (through 2009 diagnosis), date fields included codes that provided information other than dates. As part of an initiative to standardize date fields, new fields were introduced to accommodate non-date information that had previously been transmitted in date fields.
Codes (See Appendix H for the complete Flavors of Null table, which includes the NAACCR codes, HL7 codes and definitions. Use code 12 when date of birth is unknown.)
12A proper value is applicable but not known (i.e., birth date is unknown)
BlankA valid date value is provided in item Date of Birth [240], or the date was not expected to have been transmitted
Comment: This is part of the initiative of the transformation from the old NAACCR date standards to interoperable dates.
DATE OF CA CONFERENCERetired
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
660200611
Alternate Name:
XML NAACCR ID:
PARENT XML ELEMENT:
Description
The NAACCR UDSC retired this data item in Version 11, as of January 1, 2006.
DATE OF DEATH--CANADARevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
17558CCCR200911.32953 - 2960
Alternate Name:
XML NAACCR ID:dateOfDeathCanada
PARENT XML ELEMENT:Patient
Description
This field is used by the Canadian provinces/territories to record the patient's date of death. See Chapter X for date format.
DATE OF DEATH--CANADAFLAGRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
17562NAACCR2010122961 - 2962
Alternate Name:
XML NAACCR ID:dateOfDeathCanadaFlag
PARENT XML ELEMENT:Patient
Description
This flag explains why no appropriate value is in the field, Date of Death--Canada [1755]. This data item was first available in Volume II Version 12.
Rationale
Before Version 12 (through 2009 diagnosis), date fields included codes that provided information other than dates. As part of an initiative to standardize date fields, new fields were introduced to accommodate non-date information that had previously been transmitted in date fields.
Codes (See Appendix H for the complete Flavors of Null table, which includes the NAACCR codes, HL7 codes and definitions.)
10No information whatsoever can be inferred from this exceptional value (e.g, patient is not known to be deceased)
11No proper value is applicable in this context (e.g. patient is alive)
12A proper value is applicable but not known (e.g., date of death is unknown)
BlankA valid date value is provided in item Date of Death--Canada [1755], or the date was not expected to have been transmitted
Comment: This is part of the initiative of the transformation from the old NAACCR date standards to interoperable dates.
DATE OF DIAGNOSISRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
3908SEER/CoC544 - 551
Alternate Name:Date of Initial Diagnosis (CoC)
XML NAACCR ID:dateOfDiagnosis
PARENT XML ELEMENT:Tumor
Description
Date of initial diagnosis by a recognized medical practitioner for the tumor being reported whether clinically or microscopically confirmed. See Chapter X for date format.

For more discussion on determining date of diagnosis, consult the SEER Program Coding and Staging Manual or CoC STORE manual.
DATE OF DIAGNOSIS FLAGRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
3912NAACCR201012552 - 553
Alternate Name:
XML NAACCR ID:dateOfDiagnosisFlag
PARENT XML ELEMENT:Tumor
Description
This flag explains why no appropriate value in in the field, Date of Diagnosis [390]. This data item was first available in Volume II Version 12.
Rationale
Before Version 12 (through 2009 diagnosis), date fields included codes that provided information other than dates. As part of an initiative to standardize date fields, new fields were introduced to accommodate non-date information that had previously been transmitted in date fields.
Codes (See Appendix H for the complete Flavors of Null table, which includes the NAACCR codes, HL7 codes and definitions.)
12A proper value is applicable but not known. (e.g., date of diagnosis is unknown)
BlankA valid date value is provided in item Date of Diagnosis [390], or the date was not expected to have been transmitted
Comment: This is part of the initiative of the transformation from the old NAACCR date standards to interoperable dates.
DATE OF INPT ADMRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
5908NAACCR769 - 776
Alternate Name:Date of Inpatient Admission (CoC)
Date of Inpatient Adm
XML NAACCR ID:dateOfInptAdm
PARENT XML ELEMENT:Tumor
Description
Date of the inpatient admission to the reporting facility for the most definitive surgery. In the absence of surgery, use date of inpatient admission for any other therapy. In the absence of therapy, use date of inpatient admission for diagnostic evaluation. See Chapter X for date format. Use DATE OF INPT ADM FLAG [591] if there is no appropriate or known date for this item.
 
Formerly Date of Inpatient Adm.
Note: This data item is no longer supported by CoC (as of January 1, 2003).
DATE OF INPT ADM FLAGRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
5912NAACCR201012777 - 778
Alternate Name:
XML NAACCR ID:dateOfInptAdmFlag
PARENT XML ELEMENT:Tumor
Description
This flag explains why no appropriate value is in the field, Date of Inpt Adm [590]. 
Rationale
Before Version 12 (through 2009 diagnosis), date fields included codes that provided information other than dates. As part of an initiative to standardize date fields, new fields were introduced to accommodate non-date information that had previously been transmitted in date fields.
Codes (See Appendix H for the complete Flavors of Null table, which includes the NAACCR codes, HL7 codes and definitions.)
10No information whatsoever can be inferred from this exceptional value (e.g, unknown if patient was an inpatient).
11No proper value is applicable in this context (e.g., patient was never an inpatient at the reporting facility).
12A proper value is applicable but not known. This event occurred, but the date is unknown (e.g., the patient was an inpatient but the date is unknown).
BlankA valid date value is provided in item Date of Inpt Adm [590], or the date was not expected to have been transmitted.
Comment: This is part of the initiative of the transformation from the old NAACCR date standards to interoperable dates.
DATE OF INPT DISCHRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
6008NAACCR779 - 786
Alternate Name:Date of Inpatient Discharge (CoC)
Date of Inpatient Disch
XML NAACCR ID:dateOfInptDisch
PARENT XML ELEMENT:Tumor
Description
Date of the inpatient discharge from the reporting facility after the most definitive surgery. In the absence of surgery, use date of inpatient discharge for other therapy. In the absence of therapy, use date of inpatient discharge for diagnostic evaluation. This discharge date corresponds to the admission date described by Date of Inpt Adm [590]. See Chapter X for date format. Use DATE OF INPT DISCH FLAG [601] if there is no appropriate or known date for this item. Note: This item is not the same as the old NAACCR item, Date of Discharge, which has been deleted from the NAACCR layout.
 
Formerly Date of Inpatient Disch.
Note: This data item is no longer supported by CoC (as of January 1, 2003).
DATE OF INPT DISCH FLAGRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
6012NAACCR201012787 - 788
Alternate Name:
XML NAACCR ID:dateOfInptDischFlag
PARENT XML ELEMENT:Tumor
Description
This flag explains why no appropriate value is in the field, Date of Inpt Disch [600]. This data item was first available in Volume II Version 12.
Rationale
Before Version 12 (through 2009 diagnosis), date fields included codes that provided information other than dates. As part of an initiative to standardize date fields, new fields were introduced to accommodate non-date information that had previously been transmitted in date fields.
Codes (See Appendix H for the complete Flavors of Null table, which includes the NAACCR codes, HL7 codes and definitions.)
10No information whatsoever can be inferred from this exceptional value (e.g, unknown if patient was an inpatient).
11No proper value is applicable in this context (e.g., patient was never an inpatient at the reporting facility).
12A proper value is applicable but not known. This event occurred, but the date is unknown (e.g., the patient was an inpatient but the date is unknown).
BlankA valid date value is provided in item Date of Inpt Disch [600], or the date was not expected to have been transmitted.
Comment: This is part of the initiative of the transformation from the old NAACCR date standards to interoperable dates.
DATE OF LAST CANCER (TUMOR) STATUS New
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
17728CoC2018182788 - 2795
Alternate Name:
XML NAACCR ID:dateOfLastCancerStatus
PARENT XML ELEMENT:Tumor
Description
This data item documents the date of last cancer (tumor status) of the patient’s malignant or non-malignant tumor. Record in CCYYMMDD form, where blank spaces are used for unknown trailing portions of the date or where a date is not applicable. This data item is required for CoC-accredited facilities as of cases diagnosed 01/01/2018 and later.
Rationale
This information is used for patient follow-up and outcomes studies.
DATE OF LAST CANCER (TUMOR) STATUS FLAGNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
17732CoC2018182796 - 2797
Alternate Name:
XML NAACCR ID:dateOfLastCancerStatusFlag
PARENT XML ELEMENT:Tumor
Description
This flag explains why there is no appropriate value in the corresponding date field, Date of Last Cancer (tumor) Status [1772]. This data item is required for CoC-accredited facilities as of cases diagnosed 01/01/2018 and later.
Rationale
This information is used for patient follow-up and outcomes studies. As part of an initiative to standardize date fields, date flag fields were introduced to accommodate non-date information that had previously been transmitted in date fields.
Codes
12A proper value is applicable but not known. This event occurred, but the date is unknown (that is, the Date of Last Cancer (tumor) Status is unknown).
BlankA valid date value is provided in item Date of Last Cancer (tumor) Status [1772].
DATE OF LAST CONTACTRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
17508SEER/CoC2775 - 2782
Alternate Name:Date of Last Contact or Death (CoC)
Date of Last Follow-Up or of Death (SEER)
XML NAACCR ID:dateOfLastContact
PARENT XML ELEMENT:Patient
Description
Date of last contact with the patient, or date of death. If the patient has multiple tumors, Date of Last Contact should be the same for all tumors. See Chapter X for date format.
Rationale
Used for recording Date of Last Contact from active or passive follow-up. Used to record date of death and to calculate survival.
DATE OF LAST CONTACT FLAGRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
17512NAACCR2010122783 - 2784
Alternate Name:
XML NAACCR ID:dateOfLastContactFlag
PARENT XML ELEMENT:Patient
Description
This flag explains why no appropriate value is in the field, Date of Last Contact [1750].
Rationale
Before Version 12 (through 2009 diagnosis), date fields included codes that provided information other than dates. As part of an initiative to standardize date fields, new fields were introduced to accommodate non-date information that had previously been transmitted in date fields.
Codes (See Appendix H for the complete Flavors of Null table, which includes the NAACCR codes, HL7 codes and definitions.)
12A proper value is applicable but not known. This event occurred, but the date is unknown (e.g., date of last contact is unknown).
BlankA valid date value is provided in item Date of Last Contact [1750], or the date was not expected to have been transmitted.
Comment: This is part of the initiative of the transformation from the old NAACCR date standards to interoperable dates.
DATE OF MULT TUMORSRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
4458SEER200611593 - 600
Alternate Name:Date of Multiple Tumors
XML NAACCR ID:dateOfMultTumors
PARENT XML ELEMENT:Tumor
Description
This data item is used to identify the month, day and year the patient is diagnosed with multiple tumors reported as a single primary using the SEER, IARC, or Canadian Cancer Registry multiple primary rules. See Chapter X for date format. Use DATE OF MULT TUMORS FLAG [439] if there is no appropriate or known date for this item.
 
Formerly Date of Multiple Tumors.
Rationale
Patients with multiple tumors may have a worse prognosis or more extensive treatment than patients with a single tumor. This data item will make it possible to identify important information about these cases for data analysis. The Date of Multiple Tumors will allow separation of cases with multiple tumors present at the time of initial diagnosis from cases with subsequent tumors abstracted as the same primary. The date will allow tracking of the time interval between the date of original diagnosis and the first date of subsequent tumor(s) for specific primary sites and tumor histologies.
Codes (refer to http://seer.cancer.gov/tools/mphrules/index.html for additional instructions).
DATE OF MULT TUMORS FLAGRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
4392NAACCR201012601 - 602
Alternate Name:
XML NAACCR ID:dateOfMultTumorsFlag
PARENT XML ELEMENT:Tumor
Description
This flag explains why no appropriate value is in the field, Date of Mult Tumors [445]. This data item was first available in Volume II Version 12.
Rationale
Before Version 12 (through 2009 diagnosis), date fields included codes that provided information other than dates. As part of an initiative to standardize date fields, new fields were introduced to accommodate non-date information that had previously been transmitted in date fields.
Codes (See Appendix H for the complete Flavors of Null table, which includes the NAACCR codes, HL7 codes and definitions.)
11No proper value is applicable in this context (e.g., information on multiple tumors not collected/not applicable for this site).
12A proper value is applicable but not known. This event occurred, but the date is unknown (e.g., patient was diagnosed with multiple tumors and the date is unknown).
15Information is not available at this time, but it is expected that it will be available later (e.g., single tumor).
BlankA valid date value is provided in item Date of Mult Tumors [445], or the date was not expected to have been transmitted.
Comment: This is part of the initiative of the transformation from the old NAACCR date standards to interoperable dates.
DATE OF SENTINEL LYMPH NODE BIOPSYNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
8328CoC2018181016 - 1023
Alternate Name:
XML NAACCR ID:dateOfSentinelLymphNodeBiopsy
PARENT XML ELEMENT:Tumor
Description
Records the date of the sentinel lymph node(s) biopsy procedure. This data item is required for CoC-accredited facilities as of cases diagnosed 01/01/2018 and later. This data item is required for breast and melanoma cases only.
Rationale
It is a known fact that sentinel lymph node biopsies have been under-reported. Additionally, the timing and results of sentinel lymph node biopsy procedures are used in quality of care measures. This data item can be used to more accurately assess the date of the sentinel lymph node biopsy procedure separate from the date of a subsequent regional node dissection procedure, if performed.
DATE OF SENTINEL LYMPH NODE BIOPSY FLAGNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
8332CoC2018181024 - 1025
Alternate Name:
XML NAACCR ID:dateSentinelLymphNodeBiopsyFlag
PARENT XML ELEMENT:Tumor
Description
This flag explains why there is no appropriate value in the corresponding date data item, Date of Sentinel Lymph Node Biopsy [832]. This data item is required for CoC-accredited facilities as of cases diagnosed 01/01/2018 and later. This data item is required for breast and melanoma cases only.
Rationale
As part of an initiative to standardize date fields, date flag fields were introduced to accommodate non-date information that had previously been transmitted in date fields.
Codes
10No information whatsoever can be inferred from this exceptional value (that is, unknown if any sentinel lymph node biopsy was performed)
11No proper value is applicable in this context (for example, no sentinel lymph node biopsy performed; autopsy only cases)
12A proper value is applicable but not known. This event occurred, but the date is unknown (for example, sentinel lymph node biopsy performed but date is unknown)
BlankA valid date value is provided in item Date of Sentinel Lymph Node Biopsy [832]. Case was diagnosed prior to January 1, 2018.
DATE REGIONAL LYMPH NODE DISSECTIONNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
6828NAACCR2018181002 - 1009
Alternate Name:
XML NAACCR ID:dateRegionalLymphNodeDissection
PARENT XML ELEMENT:Tumor
Description
Records the date non-sentinel regional node dissection was performed. This data item is required for CoC-accredited facilities as of cases diagnosed 01/01/2018 and later. 
Rationale
It is a known fact that sentinel lymph node biopsies have been under-reported. Additionally, the timing and results of sentinel lymph node biopsy procedures are used in quality of care measures. This data item can be used to more accurately assess the date of regional node dissection separate from the date of sentinel lymph node biopsy if performed.
DATE REGIONAL LYMPH NODE DISSECTION FLAGNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
6832NAACCR2018181010 - 1011
Alternate Name:
XML NAACCR ID:dateRegionalLymphNodeDissectionFlag
PARENT XML ELEMENT:Tumor
Description
This flag explains why there is no appropriate value in the corresponding date data item, Date of Regional Lymph Node Dissection [682]. This data item is required for CoC-accredited facilities as of cases diagnosed 01/01/2018 and later.
Rationale
As part of an initiative to standardize date fields, date flag fields were introduced to accommodate non-date information that had previously been transmitted in date fields.
Codes
10No information whatsoever can be inferred from this exceptional value (that is, unknown if any regional lymph node dissection was performed)
11No proper value is applicable in this context (for example, no regional lymph node dissection was performed; autopsy only cases)
12A proper value is applicable but not known. This event occurred, but the date is unknown (for example, regional lymph node dissection was performed but date is unknown)
BlankA valid date value is provided in item Date of Regional Lymph Node Dissection [682]. Case was diagnosed prior to January 1, 2018.
DATE TUMOR RECORD AVAILBLRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
21138NPCR19975.12696 - 2703
Alternate Name:
XML NAACCR ID:dateTumorRecordAvailbl
PARENT XML ELEMENT:Tumor
Description
Date the demographic and tumor identification information on a primary/reportable neoplasm, compiled from one or more source records, from one or more facilities, is available in the central cancer registry database to be counted as an incident tumor. Cancer identification information includes, at a minimum, site, histology, laterality, behavior, and date of diagnosis. See Chapter X for date format.
Rationale
This item is used to assess and monitor the timeliness of reporting. Timeliness of abstracting (and reporting) is a concern for all standard-setting organizations. This data item can be used with the Date Case Report Received [2111] to measure timeliness of processing within the central cancer registry. This item also can be used with the Date of 1st Contact [580] or the Path--Date of Specimen Collection [7320] to measure overall timeliness.
DC STATERetired
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
237019986
Alternate Name:
XML NAACCR ID:
PARENT XML ELEMENT:
Description
The NAACCR UDSC retired this data item in Version 6, effective January 1, 1998. See Place of Death [1940].
DC STATE FILE NUMBERRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
23806State201112.24598 - 4603
Alternate Name:
XML NAACCR ID:dcStateFileNumber
PARENT XML ELEMENT:Patient
Description
Death certificate identification number as assigned by the vital statistics office in the place recorded in Place of Death [1940].
DERIVED AJCC-6 MRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
29802AJCC2003101397 - 1398
Alternate Name:Derived 6 M Storage Code
Derived AJCC M
XML NAACCR ID:derivedAjcc6M
PARENT XML ELEMENT:Tumor
Description
This data item belongs to the Collaborative Stage (CS) Data Collection System which is based on the AJCC Cancer Staging Manual, 6th and 7th editions. AJCC T, N, M plus descriptors and AJCC staging components are composed of combinations of characters, numbers, and/or special characters and can be of varying lengths. To more easily handle these components a numeric code was assigned to each unique category for each T, N, M plus descriptors and AJCC stage for 6th and 7th editions. This field contains the numeric representation for AJCC 6th edition “M” and is derived from CS coded fields using the CS algorithm. This numeric representation is referred to as the “storage” code and its associated label is referred to as the “display” code. Explanations of the “storage” codes and their corresponding “display” codes can be found in the most current version of the Collaborative Stage Data Collection System (https://cancerstaging.org/cstage/Pages/default.aspx).13 The display code should be used for display on the screen and in reports.
Rationale
The Collaborative Stage Data Collection System was designed by a joint task force including representatives from SEER, ACoS, CDC, NAACCR, NCRA, CCCR, CPAC, and AJCC, to provide a single uniform set of codes and rules for coding extent of disease (EOD) and stage information to meet the needs of all of the participating standard setters. When CS data items are coded, a computer algorithm provides the derivation of T, N, M, and stage-based on AJCC Cancer Staging Manual 6th & 7th Editions, SEER Summary Stage 1977, and SEER Summary Stage 2000. There are separate derived CS fields in the NAACCR record based on AJCC 6th Edition for 2004+ cases and AJCC 7th Edition for 2010+ cases.
Codes (See the most current version of the Collaborative Stage Data Collection System (https://cancerstaging.org/cstage/Pages/default.aspx),13 for rules and site-specific codes and coding structures.)
DERIVED AJCC-6 M DESCRIPTRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
29901AJCC1399 - 1399
Alternate Name:Derived AJCC M Descriptor
Derived 6 M Descriptor Storage Code
XML NAACCR ID:derivedAjcc6MDescript
PARENT XML ELEMENT:Tumor
Description
This data item belongs to the Collaborative Stage (CS) Data Collection System which is based on the AJCC Cancer Staging Manual, 6th and 7th editions. AJCC T, N, M plus descriptors and AJCC staging components are composed of combinations of characters, numbers, and/or special characters and can be of varying lengths. To more easily handle these components a numeric code was assigned to each unique category for each T, N, M plus descriptors and AJCC stage for 6th and 7th editions. This field contains the numeric representation for AJCC 6th edition “M Descriptor” and is derived from CS coded fields using the CS algorithm. This numeric representation is referred to as the “storage” code and its associated label is referred to as the “display” code. Explanations of the “storage” codes and their corresponding “display” codes can be found in the most current version of the Collaborative Stage Data Collection System (https://cancerstaging.org/cstage/Pages/default.aspx).13 The display code should be used for display on the screen and in reports.
Rationale
The Collaborative Stage Data Collection System was designed by a joint task force including representatives from SEER, ACoS, CDC, NAACCR, NCRA, CCCR, CPAC, and AJCC, to provide a single uniform set of codes and rules for coding extent of disease (EOD) and stage information to meet the needs of all of the participating standard setters. When CS data items are coded, a computer algorithm provides the derivation of T, N, M, and stage-based on AJCC Cancer Staging Manual 6th & 7th Editions, SEER Summary Stage 1977, and SEER Summary Stage 2000. There are separate derived CS fields in the NAACCR record based on AJCC 6th Edition for 2004+ cases and AJCC 7th Edition for 2010+ cases.
Codes (See the most current version of the Collaborative Stage Data Collection System (https://cancerstaging.org/cstage/Pages/default.aspx),13 for rules and site-specific codes and coding structures.)
DERIVED AJCC-6 NRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
29602AJCC2003101394 - 1395
Alternate Name:Derived 6 N Descriptor Storage Code
Derived AJCC N
XML NAACCR ID:derivedAjcc6N
PARENT XML ELEMENT:Tumor
Description
This data item belongs to the Collaborative Stage (CS) Data Collection System which is based on the AJCC Cancer Staging Manual, 6th and 7th editions. AJCC T, N, M plus descriptors and AJCC staging components are composed of combinations of characters, numbers, and/or special characters and can be of varying lengths. To more easily handle these components a numeric code was assigned to each unique category for each T, N, M plus descriptors and AJCC stage for 6th and 7th editions. This field contains the numeric representation for AJCC 6th edition “N” and is derived from CS coded fields using the CS algorithm. This numeric representation is referred to as the “storage” code and its associated label is referred to as the “display” code. Explanations of the “storage” codes and their corresponding “display” codes can be found in the most current version of the Collaborative Stage Data Collection System (https://cancerstaging.org/cstage/Pages/default.aspx).13 The display code should be used for display on the screen and in reports.
Rationale
The Collaborative Stage Data Collection System was designed by a joint task force including representatives from SEER, ACoS, CDC, NAACCR, NCRA, CCCR, CPAC, and AJCC, to provide a single uniform set of codes and rules for coding extent of disease (EOD) and stage information to meet the needs of all of the participating standard setters. When CS data items are coded, a computer algorithm provides the derivation of T, N, M, and stage-based on AJCC Cancer Staging Manual 6th & 7th Editions, SEER Summary Stage 1977, and SEER Summary Stage 2000. There are separate derived CS fields in the NAACCR record based on AJCC 6th Edition for 2004+ cases and AJCC 7th Edition for 2010+ cases.
Codes (See the most current version of the Collaborative Stage Data Collection System (https://cancerstaging.org/cstage/Pages/default.aspx),13 for rules and site-specific codes and coding structures.)
DERIVED AJCC-6 N DESCRIPTRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
29701AJCC2003101396 - 1396
Alternate Name:Derived AJCC N Descriptor
Derived 6 N Descriptor Storage Code
XML NAACCR ID:derivedAjcc6NDescript
PARENT XML ELEMENT:Tumor
Description
This data item belongs to the Collaborative Stage (CS) Data Collection System which is based on the AJCC Cancer Staging Manual, 6th and 7th editions. AJCC T, N, M plus descriptors and AJCC staging components are composed of combinations of characters, numbers, and/or special characters and can be of varying lengths. To more easily handle these components a numeric code was assigned to each unique category for each T, N, M plus descriptors and AJCC stage for 6th and 7th editions. This field contains the numeric representation for AJCC 6th edition “N Descriptor” and is derived from CS coded fields using the CS algorithm. This numeric representation is referred to as the “storage” code and its associated label is referred to as the “display” code. Explanations of the “storage” codes and their corresponding “display” codes can be found in the most current version of the Collaborative Stage Data Collection System (https://cancerstaging.org/cstage/Pages/default.aspx).13 The display code should be used for display on the screen and in reports.
Rationale
The Collaborative Stage Data Collection System was designed by a joint task force including representatives from SEER, ACoS, CDC, NAACCR, NCRA, CCCR, CPAC, and AJCC, to provide a single uniform set of codes and rules for coding extent of disease (EOD) and stage information to meet the needs of all of the participating standard setters. When CS data items are coded, a computer algorithm provides the derivation of T, N, M, and stage-based on AJCC Cancer Staging Manual 6th & 7th Editions, SEER Summary Stage 1977, and SEER Summary Stage 2000. There are separate derived CS fields in the NAACCR record based on AJCC 6th Edition for 2004+ cases and AJCC 7th Edition for 2010+ cases.
Codes (See the most current version of the Collaborative Stage Data Collection System (https://cancerstaging.org/cstage/Pages/default.aspx),13 for rules and site-specific codes and coding structures.)
DERIVED AJCC-6 STAGE GRPRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
30002AJCC2003101400 - 1401
Alternate Name:Derived 6 Stage Group Storage Code
Derived AJCC Stage Group
XML NAACCR ID:derivedAjcc6StageGrp
PARENT XML ELEMENT:Tumor
Description
This data item belongs to the Collaborative Stage (CS) Data Collection System which is based on the AJCC Cancer Staging Manual, 6th and 7th editions. AJCC T, N, M plus descriptors and AJCC staging components are composed of combinations of characters, numbers, and/or special characters and can be of varying lengths. To more easily handle these components a numeric code was assigned to each unique category for each T, N, M plus descriptors and AJCC stage for 6th and 7th editions. This field contains the numeric representation for the AJCC 6th edition “Stage Group” and is derived from CS coded fields using the CS algorithm. This numeric representation is referred to as the “storage” code and its associated label is referred to as the “display” code. Explanations of the “storage” codes and their corresponding “display” codes can be found in the most current version of the Collaborative Stage Data Collection System (https://cancerstaging.org/cstage/Pages/default.aspx).13 The display code should be used for display on the screen and in reports.
Rationale
The Collaborative Stage Data Collection System was designed by a joint task force including representatives from SEER, ACoS, CDC, NAACCR, NCRA, CCCR, CPAC, and AJCC, to provide a single uniform set of codes and rules for coding extent of disease (EOD) and stage information to meet the needs of all of the participating standard setters. When CS data items are coded, a computer algorithm provides the derivation of T, N, M, and stage-based on AJCC Cancer Staging Manual 6th & 7th Editions, SEER Summary Stage 1977, and SEER Summary Stage 2000. There are separate derived CS fields in the NAACCR record based on AJCC 6th Edition for 2004+ cases and AJCC 7th Edition for 2010+ cases.
Codes (See the most current version of the Collaborative Stage Data Collection System (https://cancerstaging.org/cstage/Pages/default.aspx),13 for rules and site-specific codes and coding structures.)
DERIVED AJCC-6 TRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
29402AJCC2003101391 - 1392
Alternate Name:Derived T
Derived AJCC T
XML NAACCR ID:derivedAjcc6T
PARENT XML ELEMENT:Tumor
Description
This data item belongs to the Collaborative Stage (CS) Data Collection System which is based on the AJCC Cancer Staging Manual, 6th and 7th editions. AJCC T, N, M plus descriptors and AJCC staging components are composed of combinations of characters, numbers, and/or special characters and can be of varying lengths. To more easily handle these components a numeric code was assigned to each unique category for each T, N, M plus descriptors and AJCC stage for 6th and 7th editions. This field contains the numeric representation for the AJCC 6th edition “T” and is derived from CS coded fields using the CS algorithm. This numeric representation is referred to as the “storage” code and its associated label is referred to as the “display” code. Explanations of the “storage” codes and their corresponding “display” codes can be found in the most current version of the Collaborative Stage Data Collection System (https://cancerstaging.org/cstage/Pages/default.aspx).13 The display code should be used for display on the screen and in reports.
Rationale
The Collaborative Stage Data Collection System was designed by a joint task force including representatives from SEER, ACoS, CDC, NAACCR, NCRA, CCCR, CPAC, and AJCC, to provide a single uniform set of codes and rules for coding extent of disease (EOD) and stage information to meet the needs of all of the participating standard setters. When CS data items are coded, a computer algorithm provides the derivation of T, N, M, and stage-based on AJCC Cancer Staging Manual 6th & 7th Editions, SEER Summary Stage 1977, and SEER Summary Stage 2000. There are separate derived CS fields in the NAACCR record based on AJCC 6th Edition for 2004+ cases and AJCC 7th Edition for 2010+ cases.
Codes (See the most current version of the Collaborative Stage Data Collection System (https://cancerstaging.org/cstage/Pages/default.aspx),13 for rules and site-specific codes and coding structures.)
DERIVED AJCC-6 T DESCRIPTRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
29501AJCC2003101393 - 1393
Alternate Name:Derived AJCC T Descriptor
Derived 6 T Descriptor Storage Code
XML NAACCR ID:derivedAjcc6TDescript
PARENT XML ELEMENT:Tumor
Description
This data item belongs to the Collaborative Stage (CS) Data Collection System which is based on the AJCC Cancer Staging Manual, 6th and 7th editions. AJCC T, N, M plus descriptors and AJCC staging components are composed of combinations of characters, numbers, and/or special characters and can be of varying lengths. To more easily handle these components a numeric code was assigned to each unique category for each T, N, M plus descriptors and AJCC stage for 6th and 7th editions. This field contains the numeric representation for the AJCC 6th edition “T Descriptor” and is derived from CS coded fields using the CS algorithm. This numeric representation is referred to as the “storage” code and its associated label is referred to as the “display” code. Explanations of the “storage” codes and their corresponding “display” codes can be found in the most current version of the Collaborative Stage Data Collection System (https://cancerstaging.org/cstage/Pages/default.aspx).13 The display code should be used for display on the screen and in reports.
Rationale
The Collaborative Stage Data Collection System was designed by a joint task force including representatives from SEER, ACoS, CDC, NAACCR, NCRA, CCCR, CPAC, and AJCC, to provide a single uniform set of codes and rules for coding extent of disease (EOD) and stage information to meet the needs of all of the participating standard setters. When CS data items are coded, a computer algorithm provides the derivation of T, N, M, and stage-based on AJCC Cancer Staging Manual 6th & 7th Editions, SEER Summary Stage 1977, and SEER Summary Stage 2000. There are separate derived CS fields in the NAACCR record based on AJCC 6th Edition for 2004+ cases and AJCC 7th Edition for 2010+ cases.
Codes (See the most current version of the Collaborative Stage Data Collection System (https://cancerstaging.org/cstage/Pages/default.aspx),13 for rules and site-specific codes and coding structures.)
DERIVED AJCC-7 MRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
34203AJCC2010121410 - 1412
Alternate Name:Derived 7 M Storage Code
XML NAACCR ID:derivedAjcc7M
PARENT XML ELEMENT:Tumor
Description
This item is the derived AJCC “M” staging element from coded fields using the CS algorithm. Effective for cases diagnosed 2010+.
Rationale
Derived AJCC-7 M can be used to evaluate disease spread at diagnosis, plan and track treatment patterns, and analyze outcomes.
Codes (See the most current version of the Collaborative Stage Data Collection System (https://cancerstaging.org/cstage/Pages/default.aspx),13 for rules and site-specific codes and coding structures.)
DERIVED AJCC-7 M DESCRIPTRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
34221AJCC2010121413 - 1413
Alternate Name:Derived 7 M Descript Storage Code
XML NAACCR ID:derivedAjcc7MDescript
PARENT XML ELEMENT:Tumor
Description
This item is the derived AJCC “M Descriptor” from coded fields using the CS algorithm. Effective for cases diagnosed 2010+.
Rationale
Derived AJCC-7 M Descript can be used in analysis to differentiate the timing of staging with respect to the treatment process.
Codes (See the most current version of the Collaborative Stage Data Collection System (https://cancerstaging.org/cstage/Pages/default.aspx),13 for rules and site-specific codes and coding structures.)
DERIVED AJCC-7 NRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
34103AJCC2010121406 - 1408
Alternate Name:Derived 7 N Storage Code
XML NAACCR ID:derivedAjcc7N
PARENT XML ELEMENT:Tumor
Description
This item is the derived AJCC “N” staging element from coded fields using the CS algorithm. Effective for cases diagnosed 2010+.
Rationale
The CS Derived AJCC-7 N can be used to evaluate disease spread at diagnosis, plan and track treatment patterns, and analyze outcomes.
Codes (See the most current version of the Collaborative Stage Data Collection System (https://cancerstaging.org/cstage/Pages/default.aspx),13 for rules and site-specific codes and coding structures.)
DERIVED AJCC-7 N DESCRIPTRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
34121AJCC2010121409 - 1409
Alternate Name:Derived 7 N Descript Storage Code
XML NAACCR ID:derivedAjcc7NDescript
PARENT XML ELEMENT:Tumor
Description
This item is the derived AJCC “N Descriptor” from coded fields using the CS algorithm. Effective for cases diagnosed 2010+.
Rationale
Derived AJCC-7 N Descript can be used in analysis to differentiate the timing of staging with respect to the treatment process.
Codes (See the most current version of the Collaborative Stage Data Collection System (https://cancerstaging.org/cstage/Pages/default.aspx),13 for rules and site-specific codes and coding structures.)
DERIVED AJCC-7 STAGE GRPRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
34303AJCC2010121414 - 1416
Alternate Name:Derived 7 Stage Grp Storage Code
XML NAACCR ID:derivedAjcc7StageGrp
PARENT XML ELEMENT:Tumor
Description
This item is the derived AJCC “Stage Group” from coded fields using the CS algorithm. Effective for cases diagnosed 2010+.
Rationale
The CS Derived AJCC-7 Stage Group can be used to evaluate disease spread at diagnosis, plan and track treatment patterns, and analyze outcomes.
Codes (See the most current version of the Collaborative Stage Data Collection System (https://cancerstaging.org/cstage/Pages/default.aspx),13 for rules and site-specific codes and coding structures.)
DERIVED AJCC-7 TRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
34003AJCC2010121402 - 1404
Alternate Name:Derived 7 T Storage Code
XML NAACCR ID:derivedAjcc7T
PARENT XML ELEMENT:Tumor
Description
This item is the derived AJCC “T” staging element from coded fields using the CS algorithm. Effective for cases diagnosed 2010+.
Rationale
Derived AJCC-7 T can be used to evaluate disease spread at diagnosis, plan and track treatment patterns, and analyze outcomes.
Codes (See the most current version of the Collaborative Stage Data Collection System (https://cancerstaging.org/cstage/Pages/default.aspx),13 for rules and site-specific codes and coding structures.)
DERIVED AJCC-7 T DESCRIPTRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
34021AJCC2010121405 - 1405
Alternate Name:Derived 7 T Descript Storage Code
XML NAACCR ID:derivedAjcc7TDescript
PARENT XML ELEMENT:Tumor
Description
This item is the derived AJCC “T Descriptor” from coded fields using the CS algorithm. Effective for cases diagnosed 2010+.
Rationale
Derived AJCC-7 T Descript can be used in analysis to differentiate the timing of staging with respect to the treatment process.
Codes (See the most current version of the Collaborative Stage Data Collection System (https://cancerstaging.org/cstage/Pages/default.aspx),13 for rules and site-specific codes and coding structures.)
DERIVED AJCC--FLAGRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
30301AJCC2003101446 - 1446
Alternate Name:AJCC Conversion Flag
XML NAACCR ID:derivedAjccFlag
PARENT XML ELEMENT:Tumor
Description
Flag to indicate whether the derived AJCC stage was derived from CS or EOD codes.
Codes
blankNot derived
1AJCC fields derived from Collaborative Stage
2AJCC fields derived from EOD (prior to 2004)
DERIVED EOD 2018 MNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
79515SEER201818956 - 970
Alternate Name:
XML NAACCR ID:derivedEod2018M
PARENT XML ELEMENT:Tumor
Description
This item stores the derived EOD 2018 M staging element from coded fields using the EOD algorithm. Effective for cases diagnosed 1/1/2018+.
Rationale
Derived EOD 2018 M can be used to evaluate disease spread at diagnosis, treatment patterns and outcomes over time.
 
Derived EOD 2018 M is only available at the central registry level.
Codes: See the most current version of EOD (https://staging.seer.cancer.gov/) for rules and site-specific codes and coding structures.
DERIVED EOD 2018 NNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
81515SEER201818941 - 955
Alternate Name:
XML NAACCR ID:derivedEod2018N
PARENT XML ELEMENT:Tumor
Description
This item stores the derived EOD 2018 N staging element from coded fields using the EOD algorithm. Effective for cases diagnosed 1/1/2018+.
Rationale
Derived EOD 2018 N can be used to evaluate disease spread at diagnosis, treatment patterns and outcomes over time.
 
Derived EOD 2018 N is only available at the central registry level.
Codes: See the most current version of EOD (https://staging.seer.cancer.gov/) for rules and site-specific codes and coding structures.
DERIVED EOD 2018 STAGE GROUPNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
81815SEER201818971 - 985
Alternate Name:
XML NAACCR ID:derivedEod2018StageGroup
PARENT XML ELEMENT:Tumor
Description
Derived EOD 2018 Stage Group is derived using the EOD data collection system (EOD Primary Tumor [772], EOD Regional Nodes [774] and EOD Mets [776]) algorithm. Other data items may be included in the derivation process. Effective for cases diagnosed 1/1/2018+.
Rationale
Derived EOD 2018 Stage Group can be used to evaluate disease spread at diagnosis, treatment patterns and outcomes over time.
 
Derived EOD 2018 Stage group is only available at the central registry level.
Codes: See the most current version of EOD (https://staging.seer.cancer.gov/) for rules and site-specific codes and coding structures.
DERIVED EOD 2018 TNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
78515SEER201818926 - 940
Alternate Name:
XML NAACCR ID:derivedEod2018T
PARENT XML ELEMENT:Tumor
Description
This item stores the derived EOD 2018 T value derived from coded fields using the EOD algorithm. Effective for cases diagnosed 1/1/2018+.
Rationale
Derived EOD 2018 T can be used to evaluate disease spread at diagnosis, treatment patterns and outcomes over time.
 
Derived EOD 2018 T is only available at the central registry level.
Codes: See the most current version of EOD (https://staging.seer.cancer.gov/) for rules and site-specific codes and coding structures.
DERIVED NEOADJUV RX FLAGRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
36001AJCC2010121445 - 1445
Alternate Name:
XML NAACCR ID:derivedNeoadjuvRxFlag
PARENT XML ELEMENT:Tumor
Description
This data item belongs to the Collaborative Stage (CS) Data Collection System which is based on the AJCC Cancer Staging Manual, 6th and 7th editions. This field indicates whether the patient received neoadjuvant therapy (systemic therapy or radiation therapy prior to first course surgical treatment) as part of first course of treatment.
Rationale
The Collaborative Stage Data Collection System was designed by a joint task force including representatives from SEER, ACoS, CDC, NAACCR, NCRA, CCCR, CPAC, and AJCC, to provide a single uniform set of codes and rules for coding extent of disease (EOD) and stage information to meet the needs of all of the participating standard setters. When CS data items are coded, a computer algorithm provides the derivation of T, N, M, and stage-based on AJCC Cancer Staging Manual 6th & 7th Editions, SEER Summary Stage 1977, and SEER Summary Stage 2000. There are separate derived CS fields in the NAACCR record based on AJCC 6th Edition for 2004+ cases and AJCC 7th Edition for 2010+ cases.
Codes (See the most current version of the Collaborative Stage Data Collection System (https://cancerstaging.org/cstage/Pages/default.aspx),13 for rules and site-specific codes and coding structures.)
0Neoadjuvant therapy was not administered as part of the first course of therapy
1Neoadjuvant therapy was administered as part of the first course of therapy
9Unknown
This data item will record whether neoadjuvant therapy was administered. This will be a derived field based on RX SUMM--SYTEMIC/SUR SEQ [1639] & RX SUMM--SURG/RAD SEQ [1380].

Comments:

1. This data field is used to record that neoadjuvant therapy was administered as part of the first course of treatment.
2. This item is derived based on whether systemic therapy and/or radiation therapy was administered prior to surgical treatment.
3. If the initial surgical therapy is not performed following the systemic therapy or radiation therapy, then this will be derived as 0, i.e., it is not considered neoadjuvant therapy.

DERIVED POSTRX-7 MRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
34902AJCC2010121438 - 1439
Alternate Name:Derived PostRX 7 M Storage Code
XML NAACCR ID:derivedPostrx7M
PARENT XML ELEMENT:Tumor
Description
This data item belongs to the Collaborative Stage (CS) Data Collection System which is based on the AJCC Cancer Staging Manual, 6th and 7th editions. AJCC T, N, M plus descriptors and AJCC staging components are composed of combinations of characters, numbers, and/or special characters and can be of varying lengths. To more easily handle these components a numeric code was assigned to each unique category for each T, N, M plus descriptors and AJCC stage for 6th and 7th editions. This field contains the numeric representation for the post-treatment AJCC 7th edition “M” and is derived from CS coded fields using the CS algorithm. This numeric representation is referred to as the “storage” code and its associated label is referred to as the “display” code. Explanations of the “storage” codes and their corresponding “display” codes can be found in the most current version of the Collaborative Stage Data Collection System (https://cancerstaging.org/cstage/Pages/default.aspx).13

The display code should be used for display on the screen and in reports.The implementation of this data item has been deferred indefinitely.
Rationale
The Collaborative Stage Data Collection System was designed by a joint task force including representatives from SEER, ACoS, CDC, NAACCR, NCRA, CCCR, CPAC, and AJCC, to provide a single uniform set of codes and rules for coding extent of disease (EOD) and stage information to meet the needs of all of the participating standard setters. When CS data items are coded, a computer algorithm provides the derivation of T, N, M, and stage-based on AJCC Cancer Staging Manual 6th & 7th Editions, SEER Summary Stage 1977, and SEER Summary Stage 2000. There are separate derived CS fields in the NAACCR record based on AJCC 6th Edition for 2004+ cases and AJCC 7th Edition for 2010+ cases.
Codes (See the most current version of the Collaborative Stage Data Collection System (https://cancerstaging.org/cstage/Pages/default.aspx),13 for rules and site-specific codes and coding structures.)
DERIVED POSTRX-7 NRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
34823AJCC2010121435 - 1437
Alternate Name:Derived PostRX 7 N Storage Code
XML NAACCR ID:derivedPostrx7N
PARENT XML ELEMENT:Tumor
Description
This data item belongs to the Collaborative Stage (CS) Data Collection System which is based on the AJCC Cancer Staging Manual, 6th and 7th editions. AJCC T, N, M plus descriptors and AJCC staging components are composed of combinations of characters, numbers, and/or special characters and can be of varying lengths. To more easily handle these components a numeric code was assigned to each unique category for each T, N, M plus descriptors and AJCC stage for 6th and 7th editions. This field contains the numeric representation for the post-treatment AJCC 7th edition “N” and is derived from CS coded fields using the CS algorithm. This numeric representation is referred to as the “storage” code and its associated label is referred to as the “display” code. Explanations of the “storage” codes and their corresponding “display” codes can be found in the most current version of the Collaborative Stage Data Collection System (https://cancerstaging.org/cstage/Pages/default.aspx).13

The display code should be used for display on the screen and in reports.The implementation of this data item has been deferred indefinitely.
Rationale
The Collaborative Stage Data Collection System was designed by a joint task force including representatives from SEER, ACoS, CDC, NAACCR, NCRA, CCCR, CPAC, and AJCC, to provide a single uniform set of codes and rules for coding extent of disease (EOD) and stage information to meet the needs of all of the participating standard setters. When CS data items are coded, a computer algorithm provides the derivation of T, N, M, and stage-based on AJCC Cancer Staging Manual 6th & 7th Editions, SEER Summary Stage 1977, and SEER Summary Stage 2000. There are separate derived CS fields in the NAACCR record based on AJCC 6th Edition for 2004+ cases and AJCC 7th Edition for 2010+ cases.
Codes (See the most current version of the Collaborative Stage Data Collection System (https://cancerstaging.org/cstage/Pages/default.aspx),13 for rules and site-specific codes and coding structures.)
DERIVED POSTRX-7 STGE GRPRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
34923AJCC2010121440 - 1442
Alternate Name:Derived PostRX 7 Stge Grp Storage Code
XML NAACCR ID:derivedPostrx7StgeGrp
PARENT XML ELEMENT:Tumor
Description
This data item belongs to the Collaborative Stage (CS) Data Collection System which is based on the AJCC Cancer Staging Manual, 6th and 7th editions. AJCC T, N, M plus descriptors and AJCC staging components are composed of combinations of characters, numbers, and/or special characters and can be of varying lengths. To more easily handle these components a numeric code was assigned to each unique category for each T, N, M plus descriptors and AJCC stage for 6th and 7th editions. This field contains the numeric representation for the post-treatment AJCC 7th edition “Stage Group”and is derived from CS coded fields using the CS algorithm. This numeric representation is referred to as the “storage” code and its associated label is referred to as the “display” code. Explanations of the “storage” codes and their corresponding “display” codes can be found in the most current version of the Collaborative Stage Data Collection System (https://cancerstaging.org/cstage/Pages/default.aspx).13

The display code should be used for display on the screen and in reports. The implementation of this data item has been deferred indefinitely.
Rationale
The Collaborative Stage Data Collection System was designed by a joint task force including representatives from SEER, ACoS, CDC, NAACCR, NCRA, CCCR, CPAC, and AJCC, to provide a single uniform set of codes and rules for coding extent of disease (EOD) and stage information to meet the needs of all of the participating standard setters. When CS data items are coded, a computer algorithm provides the derivation of T, N, M, and stage-based on AJCC Cancer Staging Manual 6th & 7th Editions, SEER Summary Stage 1977, and SEER Summary Stage 2000. There are separate derived CS fields in the NAACCR record based on AJCC 6th Edition for 2004+ cases and AJCC 7th Edition for 2010+ cases.
Codes (See the most current version of the Collaborative Stage Data Collection System (https://cancerstaging.org/cstage/Pages/default.aspx),13 for rules and site-specific codes and coding structures.)
DERIVED POSTRX-7 TRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
34803AJCC2010121432 - 1434
Alternate Name:Derived PostRX 7 T Storage Code
XML NAACCR ID:derivedPostrx7T
PARENT XML ELEMENT:Tumor
Description
This data item belongs to the Collaborative Stage (CS) Data Collection System which is based on the AJCC Cancer Staging Manual, 6th and 7th editions. AJCC T, N, M plus descriptors and AJCC staging components are composed of combinations of characters, numbers, and/or special characters and can be of varying lengths. To more easily handle these components a numeric code was assigned to each unique category for each T, N, M plus the post-treatment AJCC 7th edition “T” and is derived from CS coded fields using the CS algorithm. This numeric representation is referred to as the “storage” code and its associated label is referred to as the “display” code. Explanations of the “storage” codes and their corresponding “display” codes can be found in the most current version of the Collaborative Stage Data Collection System (https://cancerstaging.org/cstage/Pages/default.aspx).13

The display code should be used for display on the screen and in reports.The implementation of this data item has been deferred indefinitely.
Rationale
The Collaborative Stage Data Collection System was designed by a joint task force including representatives from SEER, ACoS, CDC, NAACCR, NCRA, CCCR, CPAC, and AJCC, to provide a single uniform set of codes and rules for coding extent of disease (EOD) and stage information to meet the needs of all of the participating standard setters. When CS data items are coded, a computer algorithm provides the derivation of T, N, M, and stage-based on AJCC Cancer Staging Manual 6th & 7th Editions, SEER Summary Stage 1977, and SEER Summary Stage 2000. There are separate derived CS fields in the NAACCR record based on AJCC 6th Edition for 2004+ cases and AJCC 7th Edition for 2010+ cases.
Codes (See the most current version of the Collaborative Stage Data Collection System (https://cancerstaging.org/cstage/Pages/default.aspx),13 for rules and site-specific codes and coding structures.)
DERIVED PRERX-7 MRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
34603AJCC2010121425 - 1427
Alternate Name:Derived PreRX 7 M Storage Code
XML NAACCR ID:derivedPrerx7M
PARENT XML ELEMENT:Tumor
Description
This data item belongs to the Collaborative Stage (CS) Data Collection System which is based on the AJCC Cancer Staging Manual, 6th and 7th editions. AJCC T, N, M plus descriptors and AJCC staging components are composed of combinations of characters, numbers, and/or special characters and can be of varying lengths. To more easily handle these components a numeric code was assigned to each unique category for each T, N, M plus descriptors and AJCC stage for 6th and 7th editions. This field contains the numeric representation for the pre-treatment AJCC 7th edition “M” and is derived from CS coded fields using the CS algorithm. This numeric representation is referred to as the “storage” code and its associated label is referred to as the “display” code. Explanations of the “storage” codes and their corresponding “display” codes can be found in the most current version of the Collaborative Stage Data Collection System (https://cancerstaging.org/cstage/Pages/default.aspx).13

The display code should be used for display on the screen and in reports. The implementation of this data item has been deferred indefinitely.
Rationale
The Collaborative Stage Data Collection System was designed by a joint task force including representatives from SEER, ACoS, CDC, NAACCR, NCRA, CCCR, CPAC, and AJCC, to provide a single uniform set of codes and rules for coding extent of disease (EOD) and stage information to meet the needs of all of the participating standard setters. When CS data items are coded, a computer algorithm provides the derivation of T, N, M, and stage-based on AJCC Cancer Staging Manual 6th & 7th Editions, SEER Summary Stage 1977, and SEER Summary Stage 2000. There are separate derived CS fields in the NAACCR record based on AJCC 6th Edition for 2004+ cases and AJCC 7th Edition for 2010+ cases.
Codes (See the most current version of the Collaborative Stage Data Collection System (https://cancerstaging.org/cstage/Pages/default.aspx),13 for rules and site-specific codes and coding structures.)
DERIVED PRERX-7 M DESCRIPRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
34621AJCC2010121428 - 1428
Alternate Name:Derived PreRX 7 M Descrip Storage Code
XML NAACCR ID:derivedPrerx7MDescrip
PARENT XML ELEMENT:Tumor
Description
This data item belongs to the Collaborative Stage (CS) Data Collection System which is based on the AJCC Cancer Staging Manual, 6th and 7th editions. AJCC T, N, M plus descriptors and AJCC staging components are composed of combinations of characters, numbers, and/or special characters and can be of varying lengths. To more easily handle these components a numeric code was assigned to each unique category for each T, N, M plus descriptors and AJCC stage for 6th and 7th editions. This field contains the numeric representation for pre-treatment AJCC 7th edition “M Descriptor” and is derived from CS coded fields using the CS algorithm. This numeric representation is referred to as the “storage” code and its associated label is referred to as the “display” code. Explanations of the “storage” codes and their corresponding “display” codes can be found in the most current version of the Collaborative Stage Data Collection System (https://cancerstaging.org/cstage/Pages/default.aspx).13

The display code should be used for display on the screen and in reports. The implementation of this data item has been deferred indefinitely.
Rationale
The Collaborative Stage Data Collection System was designed by a joint task force including representatives from SEER, ACoS, CDC, NAACCR, NCRA, CCCR, CPAC, and AJCC, to provide a single uniform set of codes and rules for coding extent of disease (EOD) and stage information to meet the needs of all of the participating standard setters. When CS data items are coded, a computer algorithm provides the derivation of T, N, M, and stage-based on AJCC Cancer Staging Manual 6th & 7th Editions, SEER Summary Stage 1977, and SEER Summary Stage 2000. There are separate derived CS fields in the NAACCR record based on AJCC 6th Edition for 2004+ cases and AJCC 7th Edition for 2010+ cases.
Codes (See the most current version of the Collaborative Stage Data Collection System (https://cancerstaging.org/cstage/Pages/default.aspx),13 for rules and site-specific codes and coding structures.)
DERIVED PRERX-7 NRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
34503AJCC2010121421 - 1423
Alternate Name:Derived PreRX 7 N Storage Code
XML NAACCR ID:derivedPrerx7N
PARENT XML ELEMENT:Tumor
Description
This data item belongs to the Collaborative Stage (CS) Data Collection System which is based on the AJCC Cancer Staging Manual, 6th and 7th editions. AJCC T, N, M plus descriptors and AJCC staging components are composed of combinations of characters, numbers, and/or special characters and can be of varying lengths. To more easily handle these components a numeric code was assigned to each unique category for each T, N, M plus descriptors and AJCC stage for 6th and 7th editions. This field contains the numeric representation for the pre-treatment AJCC 7th edition “N” and is derived from CS coded fields using the CS algorithm. This numeric representation is referred to as the “storage” code and its associated label is referred to as the “display” code. Explanations of the “storage” codes and their corresponding “display” codes can be found in the most current version of the Collaborative Stage Data Collection System (https://cancerstaging.org/cstage/Pages/default.aspx).13

The display code should be used for display on the screen and in reports. The implementation of this data item has been deferred indefinitely.
Rationale
The Collaborative Stage Data Collection System was designed by a joint task force including representatives from SEER, ACoS, CDC, NAACCR, NCRA, CCCR, CPAC, and AJCC, to provide a single uniform set of codes and rules for coding extent of disease (EOD) and stage information to meet the needs of all of the participating standard setters. When CS data items are coded, a computer algorithm provides the derivation of T, N, M, and stage-based on AJCC Cancer Staging Manual 6th & 7th Editions, SEER Summary Stage 1977, and SEER Summary Stage 2000. There are separate derived CS fields in the NAACCR record based on AJCC 6th Edition for 2004+ cases and AJCC 7th Edition for 2010+ cases.
Codes (See the most current version of the Collaborative Stage Data Collection System (https://cancerstaging.org/cstage/Pages/default.aspx),13 for rules and site-specific codes and coding structures.)
DERIVED PRERX-7 N DESCRIPRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
34521AJCC2010121424 - 1424
Alternate Name:Derived PreRX 7 N Descrip Storage Code
XML NAACCR ID:derivedPrerx7NDescrip
PARENT XML ELEMENT:Tumor
Description
This data item belongs to the Collaborative Stage (CS) Data Collection System which is based on the AJCC Cancer Staging Manual, 6th and 7th editions. AJCC T, N, M plus descriptors and AJCC staging components are composed of combinations of characters, numbers, and/or special characters and can be of varying lengths. To more easily handle these components a numeric code was assigned to each unique category for each T, N, M plus descriptors and AJCC stage for 6th and 7th editions. This field contains the numeric representation for the pre-treatment AJCC 7th edition “N Descriptor” and is derived from CS coded fields using the CS algorithm. This numeric representation is referred to as the “storage” code and its associated label is referred to as the “display” code. Explanations of the “storage” codes and their corresponding “display” codes can be found in the most current version of the Collaborative Stage Data Collection System (https://cancerstaging.org/cstage/Pages/default.aspx).13

The display code should be used for display on the screen and in reports. The implementation of this data item has been deferred indefinitely.
Rationale
The Collaborative Stage Data Collection System was designed by a joint task force including representatives from SEER, ACoS, CDC, NAACCR, NCRA, CCCR, CPAC, and AJCC, to provide a single uniform set of codes and rules for coding extent of disease (EOD) and stage information to meet the needs of all of the participating standard setters. When CS data items are coded, a computer algorithm provides the derivation of T, N, M, and stage-based on AJCC Cancer Staging Manual 6th & 7th Editions, SEER Summary Stage 1977, and SEER Summary Stage 2000. There are separate derived CS fields in the NAACCR record based on AJCC 6th Edition for 2004+ cases and AJCC 7th Edition for 2010+ cases.
Codes (See the most current version of the Collaborative Stage Data Collection System (https://cancerstaging.org/cstage/Pages/default.aspx),13 for rules and site-specific codes and coding structures.)
DERIVED PRERX-7 STAGE GRPRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
34703AJCC2010121429 - 1431
Alternate Name:Derived PreRX 7 Stge Grp Storage Code
XML NAACCR ID:derivedPrerx7StageGrp
PARENT XML ELEMENT:Tumor
Description
This data item belongs to the Collaborative Stage (CS) Data Collection System which is based on the AJCC Cancer Staging Manual, 6th and 7th editions. AJCC T, N, M plus descriptors and AJCC staging components are composed of combinations of characters, numbers, and/or special characters and can be of varying lengths. To more easily handle these components a numeric code was assigned to each unique category for each T, N, M plus descriptors and AJCC stage for 6th and 7th editions. This field contains the numeric representation for the pre-treatment AJCC 7th edition “Stage Group” and is derived from CS coded fields using the CS algorithm. This numeric representation is referred to as the “storage” code and its associated label is referred to as the “display” code. Explanations of the “storage” codes and their corresponding “display” codes can be found in the most current version of the Collaborative Stage Data Collection System (https://cancerstaging.org/cstage/Pages/default.aspx).13

The display code should be used for display on the screen and in reports. The implementation of this data item has been deferred indefinitely.
Rationale
The Collaborative Stage Data Collection System was designed by a joint task force including representatives from SEER, ACoS, CDC, NAACCR, NCRA, CCCR, CPAC, and AJCC, to provide a single uniform set of codes and rules for coding extent of disease (EOD) and stage information to meet the needs of all of the participating standard setters. When CS data items are coded, a computer algorithm provides the derivation of T, N, M, and stage-based on AJCC Cancer Staging Manual 6th & 7th Editions, SEER Summary Stage 1977, and SEER Summary Stage 2000. There are separate derived CS fields in the NAACCR record based on AJCC 6th Edition for 2004+ cases and AJCC 7th Edition for 2010+ cases.
Codes (See the most current version of the Collaborative Stage Data Collection System (https://cancerstaging.org/cstage/Pages/default.aspx),13 for rules and site-specific codes and coding structures.)
DERIVED PRERX-7 TRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
34403AJCC2010121417 - 1419
Alternate Name:Derived PreRX 7 T Storage Code
XML NAACCR ID:derivedPrerx7T
PARENT XML ELEMENT:Tumor
Description
This data item belongs to the Collaborative Stage (CS) Data Collection System which is based on the AJCC Cancer Staging Manual, 6th and 7th editions. AJCC T, N, M plus descriptors and AJCC staging components are composed of combinations of characters, numbers, and/or special characters and can be of varying lengths. To more easily handle these components a numeric code was assigned to each unique category for each T, N, M plus descriptors and AJCC stage for 6th and 7th editions. This field contains the numeric representation for the pre-treatment AJCC 7th edition “T” and is derived from CS coded fields using the CS algorithm. This numeric representation is referred to as the “storage” code and its associated label is referred to as the “display” code. Explanations of the “storage” codes and their corresponding “display” codes can be found in the the most current version of the Collaborative Stage Data Collection System (https://cancerstaging.org/cstage/Pages/default.aspx).13

The display code should be used for display on the screen and in reports. The implementation of this data item has been deferred indefinitely.
Rationale
The Collaborative Stage Data Collection System was designed by a joint task force including representatives from SEER, ACoS, CDC, NAACCR, NCRA, CCCR, CPAC, and AJCC, to provide a single uniform set of codes and rules for coding extent of disease (EOD) and stage information to meet the needs of all of the participating standard setters. When CS data items are coded, a computer algorithm provides the derivation of T, N, M, and stage-based on AJCC Cancer Staging Manual 6th & 7th Editions, SEER Summary Stage 1977, and SEER Summary Stage 2000. There are separate derived CS fields in the NAACCR record based on AJCC 6th Edition for 2004+ cases and AJCC 7th Edition for 2010+ cases.
Codes (See the most current version of the Collaborative Stage Data Collection System (https://cancerstaging.org/cstage/Pages/default.aspx),13 for rules and site-specific codes and coding structures.)
DERIVED PRERX-7 T DESCRIPRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
34421AJCC2010121420 - 1420
Alternate Name:Derived PreRX 7 T Descrip Storage Code
XML NAACCR ID:derivedPrerx7TDescrip
PARENT XML ELEMENT:Tumor
Description
This data item belongs to the Collaborative Stage (CS) Data Collection System which is based on the AJCC Cancer Staging Manual, 6th and 7th editions. AJCC T, N, M plus descriptors and AJCC staging components are composed of combinations of characters, numbers, and/or special characters and can be of varying lengths. To more easily handle these components a numeric code was assigned to each unique category for each T, N, M plus descriptors and AJCC stage for 6th and 7th editions. This field contains the numeric representation for the pre-treatment AJCC 7th edition “T Descriptor” and is derived from CS coded fields using the CS algorithm. This numeric representation is referred to as the “storage” code and its associated label is referred to as the “display” code. Explanations of the “storage” codes and their corresponding “display” codes can be found in the most current version of the Collaborative Stage Data Collection System (https://cancerstaging.org/cstage/Pages/default.aspx).13

The display code should be used for display on the screen and in reports. The implementation of this data item has been deferred indefinitely.
Rationale
The Collaborative Stage Data Collection System was designed by a joint task force including representatives from SEER, ACoS, CDC, NAACCR, NCRA, CCCR, CPAC, and AJCC, to provide a single uniform set of codes and rules for coding extent of disease (EOD) and stage information to meet the needs of all of the participating standard setters. When CS data items are coded, a computer algorithm provides the derivation of T, N, M, and stage-based on AJCC Cancer Staging Manual 6th & 7th Editions, SEER Summary Stage 1977, and SEER Summary Stage 2000. There are separate derived CS fields in the NAACCR record based on AJCC 6th Edition for 2004+ cases and AJCC 7th Edition for 2010+ cases.
Codes (See the most current version of the Collaborative Stage Data Collection System (https://cancerstaging.org/cstage/Pages/default.aspx),13 for rules and site-specific codes and coding structures.)
DERIVED SEER CLIN STG GRPRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
36105SEER201616890 - 894
Alternate Name:
XML NAACCR ID:derivedSeerClinStgGrp
PARENT XML ELEMENT:Tumor
Description
This data item is needed to store the results of the derived algorithmic calculation of Derived SEER Clinical Stage Group.
Rationale
The SEER Program is developing an algorithm to calculate clinical and pathologic stage group based on their T, N, and M components and additional information as needed to calculate stage. For example, for thyroid, additional information is needed on histology and age to calculate stage. Once the T, N, and M are known an algorithm can assign the stage group instead of a registrar having to look up the stage. There are also provisions for a separate field for directly assigned stage group if the registrar prefers entering it.
  Codes
0Stage 0
0AStage 0A
01SStage 0is
1Stage I
1AStage IA
1A1Stage IA1
1A2Stage IA2
1BStage IB
1B1Stage IB1
1CStage IC
1SStage IS
2Stage 2
2AStage 2A
2A1Stage 2A1
2A2Stage 2A2
2BStage 2B
2CStage 2C
3Stage 3
3AStage 3A
3BStage 3B
3CStage 3C
3C1Stage 3C1
3C2Stage 3C2
4Stage 4
4AStage 4A
4A1Stage 4A1
4A2Stage 4A2
4BStage 4B
4CStage 4C
OCStage OC
88Not applicable
99Unknown
BlankThe algorithm has not been run
DERIVED SEER CMB M SRCRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
36261SEER201616917 - 917
Alternate Name:Derived SEER Combined M Source
XML NAACCR ID:derivedSeerCmbMSrc
PARENT XML ELEMENT:Tumor
Description
This item is needed to store the results of the source information selected for the derived algorithmic calculation of Derived SEER Combined M [3620].
Codes
1Clinical
2Pathologic
3Clinical and pathologic information used
9Unknown
DERIVED SEER CMB N SRCRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
36241SEER916 - 916
Alternate Name:Derived SEER Combined N Source
XML NAACCR ID:derivedSeerCmbNSrc
PARENT XML ELEMENT:Tumor
Description
This item is needed to store the results of the source information selected for the derived algorithmic calculation of Derived SEER Combined N [3618].
Codes
1Clinical
2Pathologic
3Clinical and pathologic information used
9Unknown
DERIVED SEER CMB STG GRPRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
36145SEER201616895 - 899
Alternate Name:
XML NAACCR ID:derivedSeerCmbStgGrp
PARENT XML ELEMENT:Tumor
Description
This data item is needed to store the results of the derived algorithmic calculation of Derived SEER Clinical Stage Group.
Rationale
Rationale for change proposal (potential benefits of change): The SEER Program is developing an algorithm to calculate clinical and pathologic stage group based on their T, N, and M components and additional information as needed to calculate stage. For example, for thyroid, additional information is needed on histology and age to calculate stage. Once the T, N, and M are known an algorithm can assign the stage group instead of a registrar having to look up the stage. There are also provisions for a separate field for directly assigned stage group if the registrar prefers entering it.
Codes
0AStage 0
0ISStage 0is
1Stage I
1AStage IA
1A2Stage IA2
1BStage IB
1B1Stage IB1
1B2Stage IB2
1CStage IC
1SStage IS
2Stage 2
2AStage 2A
2A1Stage
2A2Stage IIA2
2BStage IIB
2CStage IIC
3Stage III
3AStage IIIA
3BStage IIIB
3CStage IIIC
3C1Stage IIIC1
3C2Stage IIIC2
4Stage IV
4AStage IVA
4A1Stage IVA1
4A2Stage IV42
4BStage IVB
4CStage IV4C
OCOccult
88Not applicable
99Unknown
BlankThe algorithm has not been run
DERIVED SEER CMB T SRCRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
36221SEER201616915 - 915
Alternate Name:Derived SEER Combined T Source
XML NAACCR ID:derivedSeerCmbTSrc
PARENT XML ELEMENT:Tumor
Description
This item is needed to store the results of the source information selected for the derived algorithmic calculation of Derived SEER Combined T [3616].
Codes
1Clinical
2Pathologic
3Clinical and pathologic information used
9Unknown
DERIVED SEER COMBINED MRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
36205SEER201616910 - 914
Alternate Name:
XML NAACCR ID:derivedSeerCombinedM
PARENT XML ELEMENT:Tumor
Description
This item is used to store the results of the source information selected for the derived algorithmic calculation of Combined T, N, and M.
Rationale
The SEER Program has collected data from 2004 on AJCC 6th T, N, M and stage and from 2010 on AJCC 7th T, N, M and stage based on algorithmic derivation from Collaborative Stage (CS) data. These data were based on combining information from both the clinical and pathologic into a combined (or ‘best’) derived T, N, M and stage group. SEER would like to continue to be able to derive a combined T, N, M and stage group in order to evaluate time trends in cancer incidence by stage. SEER is designing an algorithm to combine the clinical and pathologic information for T, N, and M into a derived combined T, N and M and then the combined T, N, and M and additional information as needed are used to derive a combined stage. These derived combined T, N, M and stage items need to be new data items.
Codes (See the most recent versions of the AJCC Cancer Staging Manual and STORE manual)
88Not applicable
BlankNot derived
DERIVED SEER COMBINED NRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
36185SEER905 - 909
Alternate Name:
XML NAACCR ID:derivedSeerCombinedN
PARENT XML ELEMENT:Tumor
Description
This item is used to store the results of the source information selected for the derived algorithmic calculation of Combined T, N, and M.
Rationale
The SEER Program has collected data from 2004 on AJCC 6th T, N, M and stage and from 2010 on AJCC 7th T, N, M and stage based on algorithmic derivation from Collaborative Stage (CS) data. These data were based on combining information from both the clinical and pathologic into a combined (or ‘best’) derived T, N, M and stage group. SEER would like to continue to be able to derive a combined T, N, M and stage group in order to evaluate time trends in cancer incidence by stage. SEER is designing an algorithm to combine the clinical and pathologic information for T, N, and M into a derived combined T, N and M and then the combined T, N, and M and additional information as needed are used to derive a combined stage. These derived combined T, N, M and stage items need to be new data items.
Codes (See the most recent versions of the AJCC Cancer Staging Manual and STORE manual)
88Not applicable
BlankNot derived
DERIVED SEER COMBINED TRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
36165SEER900 - 904
Alternate Name:
XML NAACCR ID:derivedSeerCombinedT
PARENT XML ELEMENT:Tumor
Description
This new data item is needed to store the results of the derived algorithmic calculation of Derived SEER Combined T.
Rationale
The SEER Program has collected data from 2004 on AJCC 6th T, N, M and stage and from 2010 on AJCC 7th T, N, M and stage based on algorithmic derivation from Collaborative Stage (CS) data. These data were based on combining information from both the clinical and pathologic into a combined (or ‘best’) derived T, N, M and stage group. SEER would like to continue to be able to derive a combined T, N, M and stage group in order to evaluate time trends in cancer incidence by stage. SEER is designing an algorithm to combine the clinical and pathologic information for T, N, and M into a derived combined T, N and M and then the combined T, N, and M and additional information as needed are used to derive a combined stage.
Codes (See the most recent versions of the AJCC Cancer Staging Manual and STORE manual)
88Not applicable
BlankNot derived
DERIVED SEER PATH STG GRPRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
36055SEER885 - 889
Alternate Name:
XML NAACCR ID:derivedSeerPathStgGrp
PARENT XML ELEMENT:Tumor
Description
This data item is needed to store the results of the derived algorithmic calculation of Derived SEER Pathologic Stage Group.
Rationale
The SEER Program is developing an algorithm to calculate clinical and pathologic stage group based on their T, N, and M components and additional information as needed to calculate stage. For example, for thyroid, additional information is needed on histology and age to calculate stage. Once the T, N, and M are known an algorithm can assign the stage group instead of a registrar having to look up the stage. There are also provisions for a separate field for directly assigned stage group if the registrar prefers entering it.
Codes
0Stage 0
0AStage 0A
0ISStage 0is
1Stage I
1AStage IA
1A1Stage IA1
1A2Stage IA2
1BStage IB
1B1Stage IB1
1B2Stage IB2
1CStage IC
1SStage IS
2Stage II
2AStage IIA
2A1Stage IIA1
2A2Stage IIA2
2BStage IIB
2CStage IIC
3Stage III
3AStage IIIA
3BStage IIIB
3CStage IIIC
3C1Stage IIIC1
3C2Stage IIIC2
4Stage IV
4AStage IVA
4A1Stage IVA1
4A2Stage IVA2
4BStage IVB
4CStage IVC
OCOccult
88Not applicable
99Unknown
BlankAlgorithm has not been run
DERIVED SS1977Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
30101AJCC2003101443 - 1443
Alternate Name:Derived SEER Summary Stage 1977
XML NAACCR ID:derivedSs1977
PARENT XML ELEMENT:Tumor
Description
This item is the derived “SEER Summary Stage 1977” from the CS algorithm (or EOD codes) effective with 2004 diagnosis.
Rationale
The Collaborative Stage Data Collection System was designed by a joint task force including representatives from SEER, ACoS, CDC, NAACCR, NCRA, CCCR, CPAC, and AJCC, to provide a single uniform set of codes and rules for coding extent of disease (EOD) and stage information to meet the needs of all of the participating standard setters. When CS data items are coded, a computer algorithm provides the derivation of T, N, M, and stage-based on AJCC Cancer Staging Manual 6th & 7th Editions, SEER Summary Stage 1977, and SEER Summary Stage 2000. There are separate derived CS fields in the NAACCR record based on AJCC 6th Edition for 2004+ cases and AJCC 7th Edition for 2010+ cases.
Codes (See the most current version of the Collaborative Stage Data Collection System (https://cancerstaging.org/cstage/Pages/default.aspx),13 for rules and site-specific codes and coding structures.)
DERIVED SS1977--FLAGRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
30401AJCC2003101447 - 1447
Alternate Name:SS1977 Conversion Flag
XML NAACCR ID:derivedSs1977Flag
PARENT XML ELEMENT:Tumor
Description
Flag to indicate whether the derived SEER Summary Stage 1977 was derived from CS or EOD codes.
Rationale
The Collaborative Stage Data Collection System was designed by a joint task force including representatives from SEER, ACoS, CDC, NAACCR, NCRA, CCCR, CPAC, and AJCC, to provide a single uniform set of codes and rules for coding extent of disease (EOD) and stage information to meet the needs of all of the participating standard setters. When CS data items are coded, a computer algorithm provides the derivation of T, N, M, and stage-based on AJCC Cancer Staging Manual 6th & 7th Editions, SEER Summary Stage 1977, and SEER Summary Stage 2000. There are separate derived CS fields in the NAACCR record based on AJCC 6th Edition for 2004+ cases and AJCC 7th Edition for 2010+ cases.
Codes (See the most current version of the Collaborative Stage Data Collection System (https://cancerstaging.org/cstage/Pages/default.aspx),13 for rules and site-specific codes and coding structures.)
BlankNot derived
1SS1977 derived from Collaborative Stage
2SS1977 derived from EOD (prior to 2004)
DERIVED SS2000Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
30201AJCC2003101444 - 1444
Alternate Name:Derived SEER Summary Stage 2000
XML NAACCR ID:derivedSs2000
PARENT XML ELEMENT:Tumor
Description
This item is the derived “SEER Summary Stage 2000” from the CS algorithm (or EOD codes) effective with 2004 diagnosis.
Rationale
The Collaborative Stage Data Collection System was designed by a joint task force including representatives from SEER, ACoS, CDC, NAACCR, NCRA, CCCR, CPAC, and AJCC, to provide a single uniform set of codes and rules for coding extent of disease (EOD) and stage information to meet the needs of all of the participating standard setters. When CS data items are coded, a computer algorithm provides the derivation of T, N, M, and stage-based on AJCC Cancer Staging Manual 6th & 7th Editions, SEER Summary Stage 1977, and SEER Summary Stage 2000. There are separate derived CS fields in the NAACCR record based on AJCC 6th Edition for 2004+ cases and AJCC 7th Edition for 2010+ cases.
Codes (See the most current version of the Collaborative Stage Data Collection System (https://cancerstaging.org/cstage/Pages/default.aspx),13 for rules and site-specific codes and coding structures.)
DERIVED SS2000--FLAGRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
30501AJCC2003101448 - 1448
Alternate Name:SS2000 Conversion Flag
XML NAACCR ID:derivedSs2000Flag
PARENT XML ELEMENT:Tumor
Description
Flag to indicate whether the derived SEER Summary Stage 2000 was derived from CS or EOD codes.
Rationale
The Collaborative Stage Data Collection System was designed by a joint task force including representatives from SEER, ACoS, CDC, NAACCR, NCRA, CCCR, CPAC, and AJCC, to provide a single uniform set of codes and rules for coding extent of disease (EOD) and stage information to meet the needs of all of the participating standard setters. When CS data items are coded, a computer algorithm provides the derivation of T, N, M, and stage-based on AJCC Cancer Staging Manual 6th & 7th Editions, SEER Summary Stage 1977, and SEER Summary Stage 2000. There are separate derived CS fields in the NAACCR record based on AJCC 6th Edition for 2004+ cases and AJCC 7th Edition for 2010+ cases.
Codes (See the most current version of the Collaborative Stage Data Collection System (https://cancerstaging.org/cstage/Pages/default.aspx),13 for rules and site-specific codes and coding structures.)
1SS2000 derived from Collaborative Stage
2SS2000 derived from EOD (prior to 2004)
BlankNot derived
DERIVED SUMMARY STAGE 2018Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
7621SEER201816986 - 986
Alternate Name:Derived SS2018
XML NAACCR ID:derivedSummaryStage2018
PARENT XML ELEMENT:Tumor
Description
Derived Summary Stage 2018 is derived using the EOD data collection system (EOD Primary Tumor [772], EOD Regional Nodes [774] and EOD Mets [776]) algorithm. Other data items may be included in the derivation process. Effective for cases diagnosed 1/1/2018+.
Rationale
The SEER program has collected staging information on cases since its inception in 1973. Summary Stage groups cases into broad categories of in situ, local, regional, and distant. Summary Stage can be used to evaluate disease spread at diagnosis, treatment patterns and outcomes over time.
 
Derived Summary Stage 2018 [762] is only available at the central registry level.
Note: This data item was included in Standards Volume II, Version 16; however, it was not implemented until 2018.
Codes
0In situ
1Localized
2Regional, direct extension only
3Regional, regional lymph nodes only
4Regional, direct extension and regional lymph nodes
7Distant
8Benign, borderline
9Unknown if extension or metastasis (unstaged, unknown, or unspecified)
Death certificate only case
DIAGNOSTIC CONFIRMATIONRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
4901SEER/CoC576 - 576
Alternate Name:
XML NAACCR ID:diagnosticConfirmation
PARENT XML ELEMENT:Tumor
Description
Code for the best method of diagnostic confirmation of the cancer being reported at any time in the patient’s history.
Rationale
Diagnostic confirmation is useful to calculate rates based on microscopically confirmed cancers. Full incidence calculations must also include tumors that are only confirmed clinically. The percentage of tumors that not micropscopically confirmed is an indication of whether case finding is including sources outside of pathology reports.
Codes
1Positive histology
2Positive cytology
3Positive histology PLUS - positive immunophenotyping AND/OR positive genetic studies (Used only for hematopoietic and lymphoid neoplasms M-9590/3-9992/3)
4Positive microscopic confirmation, method not specified
5Positive laboratory test/marker study
6Direct visualization without microscopic confirmation
7Radiography and/or other imaging techniques without microscopic confirmation
8Clinical diagnosis only (other than 5, 6, or 7)
9Unknown whether or not microscopically confirmed; death certificate only
Note: Code 3 (used only for hematopoietic and lymphoid neoplasms M-9590/3-9992/3) was adopted for use effective with 2010 diagnoses.
DIAGNOSTIC PROC 73-87Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
22002SEER199552638 - 2639
Alternate Name:Diagnostic Procedures (1973-87 SEER)
XML NAACCR ID:diagnosticProc7387
PARENT XML ELEMENT:Tumor
Description
Data item required by SEER for tumors of certain sites for the years 1973-87. This item is no longer collected. See Appendix D of the SEER Program Code Manual for details.
EHR REPORTINGNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
25081000NAACCR2018185105 - 6104
Alternate Name:
XML NAACCR ID:ehrReporting
PARENT XML ELEMENT:Tumor
Description
Cancer case reports transmitted from electronic health records (EHR) in the HL7 CDA (Clinical Document Architecture) format must adhere to specifications and requirements as defined by the Implementation Guide (IG) which has been adopted by the Office of the National Coordinator of for Health Information Technology. The IG specifies collection and transmission of cancer diagnosis fields including (but not limited to) primary site, histology, behavior, diagnosis date, and staging elements. The IG also specifies transmission of other data documented in the EHR as part of the care of the patient which are also standardized, but are not routinely collected by cancer registries in the same way or as discrete items. Examples of these are procedures, medications, smoking, and vital signs (i.e., height, weight, BMI). Currently, software tools such as CDC’s eMaRC Plus parse some EHR elements and map or translate these fields to NAACCR items. However, some data are not able to be mapped to discrete items. This new proposed field will allow central cancer registries to collect information from the EHR and map these data in the NAACCR record layout so that they can be included in the central registry database and be available to enhance surveillance data.
Rationale
Central cancer registries may wish to integrate EHR data, which are not already in the NAACCR record layout, into their databases. The EHR Reporting Field will allow central cancer registries to capture data that are received from EHR systems as discrete items. Collection of these data in this field will allow central cancer registries to assess ways in which the EHR data can be standardized in the NAACCR record layout in the future.
Examples of data to be collected in this field:
Family history
Practice OID
Smoking Status
Tobacco Use
Vital sign: height
Vital sign: weight
Vital sign: BMI
Provider First Name
Provider Last Name
Provider Specialty
Medication name, code
Cancer-direct Procedures name, code, code system, date of procedure
Care Plan: planned encounter
EHR Vendor name, software and version
EOD METSRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
7762SEER201816924 - 925
Alternate Name:SEER Mets
XML NAACCR ID:eodMets
PARENT XML ELEMENT:Tumor
Description
EOD Mets is part of the EOD 2018 data collection system and is used to classify the distant site(s) of metastatic involvement at time of diagnosis. See also EOD Primary Tumor [772] and EOD Regional Nodes [774]. Effective for cases diagnosed 1/1/2018+.
Rationale
EOD Mets is used to calculate Derived EOD 2018 M [795] (when applicable) and Derived Summary Stage 2018 [762]. Derivation will occur at the level of the central registry.
Note: This data item was included in Standards Volume II, Version 16; however, it was not implemented until 2018.
Codes (in addition to valid schema-specific codes)
00None
No distant metastasis
Unknown if distant metastasis
88Not applicable: Information not collected for this schema
Use for these sites only: HemeRetic;
Ill Defined Other (includes unknown primary site);
Kaposi Sarcoma;
Lymphoma;
Lymphoma-CLL/SLL;
Myeloma Plasma Cell Disorder
99Death certificate only (DCO)
Note: See the most current version of EOD (https://staging.seer.cancer.gov/) for rules and site-specific codes and coding structures.
EOD PRIMARY TUMORRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
7723SEER201816918 - 920
Alternate Name:SEER Primary Tumor
XML NAACCR ID:eodPrimaryTumor
PARENT XML ELEMENT:Tumor
Description
EOD Primary Tumor is part of the EOD 2018 data collection system and is used to classify contiguous growth (extension) of the primary tumor within the organ of origin or its direct extension into neighboring organs. See also EOD Regional Nodes [774] and EOD Mets [776]. Effective for cases diagnosed 1/1/2018+.
Rationale
EOD Primary Tumor is used to calculate Derived EOD 2018 T [785] (when applicable) and Derived Summary Stage 2018 [762]. Derivation will occur at the level of the central registry.
Note: This data item was included in Standards Volume II, Version 16; however, it was not implemented until 2018.
Codes (In addition to schema-specific codes where needed)
000In situ, intraepithelial, noninvasive
800No evidence of primary tumor
999Unknown; primary tumor not stated
Primary tumor cannot be assessed
Not documented in patient record
Death certificate only (DCO)
Note: (See the most current version of EOD (https://staging.seer.cancer.gov/) for rules and site-specific codes and coding structures.)
EOD REGIONAL NODESRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
7743SEER201816921 - 923
Alternate Name:SEER Regional Nodes
XML NAACCR ID:eodRegionalNodes
PARENT XML ELEMENT:Tumor
Description
EOD Regional Nodes is part of the EOD 2018 data collection system and is used to classify the regional lymph nodes involved with cancer at the time of diagnosis. See also EOD Primary Tumor [772] and EOD Mets [776]. Effective for cases diagnosed 1/1/2018+.
Rationale
EOD Regional Nodes is used to calculate Derived EOD 2018 N [815] (when applicable) and Derived Summary Stage 2018 [762]. Derivation will occur at the level of the central registry.
Note: This data item was included in Standards Volume II, Version 16; however, it was not implemented until 2018.
Codes (in addition to valid schema-specific codes)
000None
800Regional lymph node(s), NOS
Lymph node(s), NOS
888Not applicable–e.g., CNS, hematopoietic
999Unknown
Note: See the most current version of EOD (https://staging.seer.cancer.gov/) for rules and site-specific codes and coding structures.
EOD--EXTENSIONRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
7902SEER993 - 994
Alternate Name:Extension (SEER EOD) (96 CoC)
Extension (pre-96 SEER/CoC)
XML NAACCR ID:eodExtension
PARENT XML ELEMENT:Tumor
Description
Part of the 10-digit EOD [779]. Detailed site-specific codes for anatomic EOD used by SEER for tumors diagnosed from January 1, 1988, through December 31, 2003.

Codes were revised effective January 1, 1998, to reflect changes in the AJCC Cancer Staging Manual, Fifth Edition.
Rationale
Site-specific EOD codes provide extensive detail describing disease extent. The EOD codes can be grouped into different stage categories for analysis (e.g., historical summary stage categories consistent with those used in published SEER data since 1973, or more recently, AJCC stage groupings). The codes are updated as needed, but updates are usually backward compatible with old categories. See Comparative Staging Guide for Cancer6.
Codes (See SEER Extent of Disease, 1988: Codes and Coding Instructions, Third Edition8 for site-specific codes and coding rules for all EOD fields.)
EOD--EXTENSION PROST PATHRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
8002SEER19954995 - 996
Alternate Name:
XML NAACCR ID:eodExtensionProstPath
PARENT XML ELEMENT:Tumor
Description
Part of the 10-digit EOD [779]. Detailed site-specific codes for anatomic EOD used by SEER for tumors diagnosed from January 1, 1988, through December 31, 2003.

Codes were revised effective January 1, 1998, to reflect changes in the AJCC Cancer Staging Manual, Fifth Edition.
Rationale
Site-specific EOD codes provide extensive detail describing disease extent. The EOD codes can be grouped into different stage categories for analysis (e.g., historical summary stage categories consistent with those used in published SEER data since 1973, or more recently, AJCC stage groupings). The codes are updated as needed, but updates are usually backward compatible with old categories. See Comparative Staging Guide for Cancer.

EOD--Extension Prost Path is an additional field for prostate cancer only to reflect information from radical prostatectomy, effective for January 1, 1995, through December 31, 2003, diagnoses. The field is left blank for all other primaries.
Codes (See SEER Extent of Disease, 1988: Codes and Coding Instructions, Third Edition8 for site-specific codes and coding rules for all EOD fields.)
EOD--LYMPH NODE INVOLVRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
8101SEER997 - 997
Alternate Name:Lymph Nodes (pre 96-SEER/CoC)
Lymph Nodes (SEER EOD) (96 CoC)
XML NAACCR ID:eodLymphNodeInvolv
PARENT XML ELEMENT:Tumor
Description
Part of the 10-digit EOD [779]. Detailed site-specific codes for anatomic EOD used by SEER for tumors diagnosed from January 1, 1988, through December 31, 2003.

Codes were revised effective January 1, 1998, to reflect changes in the AJCC Cancer Staging Manual, Fifth Edition.
Rationale
Site-specific EOD codes provide extensive detail describing disease extent. The EOD codes can be grouped into different stage categories for analysis (e.g., historical summary stage categories consistent with those used in published SEER data since 1973, or more recently, AJCC stage groupings). The codes are updated as needed, but updates are usually backward compatible with old categories. See Comparative Staging Guide for Cancer.
Codes (See SEER Extent of Disease, 1988: Codes and Coding Instructions, Third Edition8 for site-specific codes and coding rules for all EOD fields.)
EOD--OLD 13 DIGITRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
84013SEER1026 - 1038
Alternate Name:SEER EEOD (SEER)
13-Digit (Expanded) Site-Specific Extent of Disease (SEER)
XML NAACCR ID:eodOld13Digit
PARENT XML ELEMENT:Tumor
Description
Detailed site-specific codes for EOD used by SEER for selected sites of cancer for tumors diagnosed 1973-1982, except death-certificate-only cases.
Codes (See Extent of Disease: Codes and Coding Instructions (SEER 1977)10 for codes.)
EOD--OLD 2 DIGITRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
8502SEER1039 - 1040
Alternate Name:2-Digit Nonspecific and 2-Digit Site-Specific Extent of Disease (1973-1982 SEER)
XML NAACCR ID:eodOld2Digit
PARENT XML ELEMENT:Tumor
Description
Site-specific codes for EOD used by SEER for tumors diagnosed from January 1, 1973, to December 31, 1982, for cancer sites that did not have a 13-digit scheme see EOD--Old 13 Digit [840].
Codes (See Extent of Disease: Codes and Coding Instructions (SEER 1977)10 for codes.)
EOD--OLD 4 DIGITRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
8604SEER1041 - 1044
Alternate Name:4-Digit Extent of Disease (1983-1987 SEER)
XML NAACCR ID:eodOld4Digit
PARENT XML ELEMENT:Tumor
Description
Codes for site-specific EOD used by SEER for tumors diagnosed from January 1, 1983, to December 31, 1987, for all cancer sites.
Codes (See SEER Extent of Disease: New 4-Digit Schemes: Codes and Coding Instructions9 for codes.)
EOD--TUMOR SIZERevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
7803SEER/CoC990 - 992
Alternate Name:Size of Primary Tumor (SEER)
Size of Tumor (CoC)
XML NAACCR ID:eodTumorSize
PARENT XML ELEMENT:Tumor
Description
Part of the 10-digit EOD [779]. Detailed site-specific codes for anatomic EOD used by SEER for tumors diagnosed from January 1, 1988, through December 31, 2003.

This field was included in the CoC dataset, separate from EOD.

Codes were revised effective January 1, 1998, to reflect changes in the AJCC Cancer Staging Manual, Fifth Edition.
Rationale
Site-specific EOD codes provide extensive detail describing disease extent. The EOD codes can be grouped into different stage categories for analysis (e.g., historical summary stage categories consistent with those used in published SEER data since 1973, or more recently, AJCC stage groupings). The codes are updated as needed, but updates are usually backward compatible with old categories. See Comparative Staging Guide for Cancer.6
Codes (See SEER Extent of Disease, 1988: Codes and Coding Instructions, Third Edition, for site-specific codes and coding rules for all EOD fields. The CoC codes for Tumor Size are in the STORE manual.)

Note: See Chapter V, Unresolved Issues, for a discussion of coding differences between CoC and SEER.

ESOPHAGUS AND EGJ TUMOR EPICENTERNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
38291NAACCR2018181814 - 1814
Alternate Name:
XML NAACCR ID:esophagusAndEgjTumorEpicenter
PARENT XML ELEMENT:Tumor
Description
Esophagus and Esophagogastric Junction (EGJ), Squamous Cell (including adenosquamous), Tumor Location refers to the position of the epicenter of the tumor in the esophagus.
Rationale
This data item is required for prognostic stage grouping for squamous and adenosquamous carcinoma in AJCC 8th edition, Chapter 16 Esophagus and Esophagogastric Junction. It is a new data item for cases diagnosed 1/1/2018+.
Codes
0U: Upper (Cervical/Proximal esophagus to lower border of azygos vein)
1M: Middle (Lower border of azygos vein to lower border of inferior pulmonary vein)
2L: Lower (Lower border of inferior pulmonary vein to stomach, including gastroesophageal junction)
9X: Esophagus, NOS
Specific location of epicenter not documented in medical record
Specific location of epicenter not assessed or unknown if assessed
Each Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.
ESTROGEN RECEPTOR PERCENT POSITIVE OR RANGE New
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
38263NAACCR2018181752 - 1754
Alternate Name:
XML NAACCR ID:estrogenReceptorPercentPositiveOrRange
PARENT XML ELEMENT:Tumor
Description
Estrogen Receptor, Percent Positive Range is the percent of cells staining estrogen receptor positive by IHC.
Rationale
Estrogen Receptor, Percent Positive Range is a Registry Data Collection Variable in AJCC. It is a new data item for cases diagnosed 1/1/2018+.
Codes
000ER negative, or stated as less than 1%
001-1001-100 percent
R10Stated as 1-10%
R20Stated as 11-20%
R30Stated as 21-30%
R40Stated as 31-40%
R50Stated as 41-50%
R60Stated as 51-60%
R70Stated as 61-70%
R80Stated as 71-80%
R90Stated as 81-90%
R99Stated as 91-100%
XX8Not applicable: Information not collected for this case
(If this item is required by your standard setter, use of code XX8 will result in an edit error.)
XX9Not documented in medical record
Estrogen Receptor, Percent Positive Range not assessed or unknown if assessed
Each Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.
ESTROGEN RECEPTOR SUMMARYNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
38271NAACCR2018181743 - 1743
Alternate Name:
XML NAACCR ID:estrogenReceptorSummary
PARENT XML ELEMENT:Tumor
Description
ER (Estrogen Receptor) Summary is a summary of results of the estrogen receptor (ER) assay.
Rationale
This data item is required for prognostic stage grouping in AJCC 8th edition, Chapter 48, Breast. It was previously collected as Breast CS SSF # 1.
Codes
0ER negative
1ER positive
7Test ordered, results not in chart
9Not documented in medical record
Cannot be determined (indeterminate)
ER (Estrogen Receptor) Summary status not assessed or unknown if assessed
Each Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.
ESTROGEN RECEPTOR TOTAL ALLRED SCORE New
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
38282NAACCR2018181755 - 1756
Alternate Name:
XML NAACCR ID:estrogenReceptorTotalAllredScore
PARENT XML ELEMENT:Tumor
Description
Estrogen Receptor, Total Allred Score is based on the percentage of cells that stain positive by IHC for estrogen receptor (ER) and the intensity of that staining.
Rationale
Estrogen Receptor, Total Allred Score is a Registry Data Collection Variable in AJCC. It is a new data item for cases diagnosed 1/1/2018+.
Codes
00Total ER Allred score of 0
01Total ER Allred score of 1
02Total ER Allred score of 2
03Total ER Allred score of 3
04Total ER Allred score of 4
05Total ER Allred score of 5
06Total ER Allred score of 6
07Total ER Allred score of 7
08Total ER Allred score of 8
X8Not applicable: Information not collected for this case
(If this item is required by your standard setter, use of code X8 will result in an edit error.)
X9Not documented in medical record
Estrogen Receptor, Total Allred Score not assessed, or unknown if assessed
Each Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.
EXTENT OF DISEASE 10-DIGRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
77912990 - 1001
Alternate Name:
XML NAACCR ID:extentOfDisease10Dig
PARENT XML ELEMENT:Tumor
Description
The name for a group of subfields that contain detailed site-specific codes for the anatomic EOD. SEER uses the subfields for tumors diagnosed from January 1, 1988, through December 31, 2003.

Group names appear only in the data dictionary and in Appendix E.

Subfields

EOD--Tumor Size [780]
EOD--Extension [790]
EOD--Extension Prost Path [800]
EOD--Lymph Node Involv [810]
Regional Nodes Positive [820]
Regional Nodes Examined [830]
EXTRANODAL EXTENSION CLIN (NON-HEAD AND NECK)New
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
38301NAACCR2018181922 - 1922
Alternate Name:
XML NAACCR ID:extranodalExtensionClin
PARENT XML ELEMENT:Tumor
Description
Extranodal Extension (ENE) Clinical is defined as "the extension of a nodal metastasis through the lymph node capsule into adjacent tissue" during the diagnostic workup. This data item defines clinical ENE for sites other than Head and Neck.
Rationale
Extranodal Extension Clinical (non-Head and Neck) is a Registry Data Collection Variable for AJCC. This data item was previously collected for Penis, SSF# 17.
Codes
0Regional lymph nodes involved, ENE not present/not identified during diagnostic workup
1Regional lymph nodes involved, ENE present/identified during diagnostic workup, based on physical exam and/or imaging
2Regional lymph nodes involved, ENE present/identified during diagnostic workup, based on microscopic confirmation
7No lymph node involvement during diagnostic workup (cN0)
8Not applicable: Information not collected for this case
(If this information is required by your standard setter, use of code 8 may result in an edit error)
9Not documented in medical record
Clinical ENE not assessed or unknown if assessed during diagnostic workup
Clinical assessment of lymph nodes not done, or unknown if done
Each Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.
EXTRANODAL EXTENSION HEAD AND NECK CLINICALNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
38311NAACCR2018181818 - 1818
Alternate Name:
XML NAACCR ID:extranodalExtensionHeadAndNeckClinical
PARENT XML ELEMENT:Tumor
Description
Extranodal extension (ENE) is defined as "the extension of a nodal metastasis through the lymph node capsule into adjacent tissue" and is a prognostic factor for most head and neck tumors. This data item pertains to clinical staging extension.
Rationale
Extranodal Extension Head and Neck Clinical is a Registry Data Collection Variable in AJCC. It was previously collected as Head and Neck SSF# 8 (Common SSF).
Codes
0Regional lymph nodes involved, ENE not present/not identified during diagnostic workup
1Regional lymph nodes involved, ENE present/identified during diagnostic workup, based on physical exam WITH or WITHOUT imaging
2Regional lymph nodes involved, ENE present/identified during diagnostic workup, based on microscopic confirmation
7No lymph node involvement during diagnostic workup (cN0)
8Not applicable: Information not collected for this case
(If this information is required by your standard setter, use of code 8 may result in an edit error)
9Not documented in medical record
ENE not assessed during diagnostic workup, or unknown if assessed
Clinical assessment of lymph nodes not done, or unknown if done
Each Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.
EXTRANODAL EXTENSION HEAD AND NECK PATHOLOGICALNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
38323NAACCR2018181819 - 1821
Alternate Name:
XML NAACCR ID:extranodalExtensionHeadAndNeckPathological
PARENT XML ELEMENT:Tumor
Description
Extranodal extension (ENE) is defined as "the extension of a nodal metastasis through the lymph node capsule into adjacent tissue" and is a prognostic factor for most head and neck tumors. This data item pertains to pathological staging extension.
Rationale
Extranodal Extension Head and Neck Pathological is a Registry Data Collection Variable in AJCC. It was previously collected as Head and Neck SSF# 9 (Common SSF).
Codes
0.0Lymph nodes positive for cancer but ENE not identified or negative
0.1-9.9ENE 0.1 to 9.9 mm
X.1ENE 10 mm or greater
X.2ENE microscopic, size unknown
Stated as ENE (mi)
X.3ENE major, size unknown
Stated as ENE (ma)
X.4ENE present, microscopic or major unknown, size unknown
X.7Surgically resected regional lymph nodes negative for cancer (pN0)
X.8Not applicable: Information not collected for this case
(If this information is required by your standard setter, use of code X.8 may result in an edit error)
X.9Not documented in medical record
No surgical resection of regional lymph nodes
ENE not assessed pathologically, or unknown if assessed
Pathological assessment of lymph nodes not done, or unknown if done
Each Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.
EXTRANODAL EXTENSION PATH (NON-HEAD AND NECK)New
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
38331NAACCR2018181923 - 1923
Alternate Name:
XML NAACCR ID:extranodalExtensionPath
PARENT XML ELEMENT:Tumor
Description
Extranodal Extension Pathological is defined as "the extension of a nodal metastasis through the lymph node capsule into adjacent tissue" identified as part of the surgical resection. This data item defines pathological ENE for sites other than Head and Neck.
Rationale
Extranodal Extension Pathological (non-Head and Neck) is a Registry Data Collection Variable for AJCC. This data item was previously collected for Penis, SSF# 17.
Codes
0Regional lymph nodes involved, ENE not present/not identified from surgical resection
1Regional lymph nodes involved, ENE present/identified from surgical resection
7No lymph node involvement from surgical resection (pN0)
8Not applicable: Information not collected for this case
(If this information is required by your standard setter, use of code 8 may result in an edit error)
9Not documented in medical record
No surgical resection of regional lymph nodes
Cannot be determined
Pathological assessment of lymph nodes not done, or unknown if done
Extranodal Extension Pathological not assessed or unknown if assessed
Each Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.
EXTRAVASCULAR MATRIX PATTERNS New
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
38341NAACCR2018181876 - 1876
Alternate Name:
XML NAACCR ID:extravascularMatrixPatterns
PARENT XML ELEMENT:Tumor
Description
Extravascular Matrix Patterns, the presence of loops and networks in extracellular matrix patterns, is a prognostic factor for uveal melanoma.
Rationale
Extravascular Matrix Pattern is a Registry Data Collection Variable in AJCC 8. This data item was previously collected as Uveal Melanoma, CS SSF #11 and CS SSF# 12. These two data items were combined and simplified into one data for cases diagnosed 1/1/2018+.
Codes
0Extravascular matrix pattern not present/not identified
1Extravascular matrix pattern present/identified
8Not applicable: Information not collected for this case
(If this information is required by your standard setter, use of code 8 may result in an edit error.)
9Not documented in medical record
Extravascular Matrix Pattern not assessed or unknown if assessed
Each Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.
FAMILY HISTORY OF CANCERRetired
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
360201012
Alternate Name:
XML NAACCR ID:
PARENT XML ELEMENT:
Description
The NAACCR UDSC retired this data item in Version 12, as of January 1, 2010.
FIBROSIS SCORENew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
38351NAACCR2018181862 - 1862
Alternate Name:
XML NAACCR ID:fibrosisScore
PARENT XML ELEMENT:Tumor
Description
Fibrosis Score, the degree of fibrosis of the liver based on pathological examination, is a prognostic factor for liver cancer.
Rationale
Fibrosis Score is a Registry Data Collection Variable in AJCC. This data item was previously collected for Liver, CS SSF# 2.
Codes
0Ishak fibrosis score 0-4

No to moderate fibrosis
METAVIR score F0-F3
Batt-Ludwig score 0-3
1Ishak fibrosis score 5-6

Advanced/severe fibrosis
METAVIR score F4
Batt-Ludwig score 4
Developing cirrhosis
Incomplete cirrhosis
Transition to cirrhosis
Cirrhosis, probable or definite
Cirrhosis, NOS
7Clinical statement of advanced/severe fibrosis or cirrhosis, AND
Not histologically confirmed or unknown if histologically confirmed
8Not applicable: Information not collected for this case
(If this item is required by your standard setter, use of code 8 will result in an edit error.)
9Not documented in medical record
Stated in medical record that patient does not have advanced cirrhosis/advanced fibrosis, not histologically confirmed or unknown if histologically confirmed
Fibrosis score stated but cannot be assigned to codes 0 or 1
Fibrosis score stated but scoring system not recorded
Fibrosis Score not assessed or unknown if assessed
Each Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.
FIGO STAGENew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
38362NAACCR2018181816 - 1817
Alternate Name:
XML NAACCR ID:figoStage
PARENT XML ELEMENT:Tumor
Description
Federation Internationale de Gynecologie et d'Obstetrique (FIGO) is a staging system for female reproductive cancers.
Rationale
FIGO stage is a Registry Data Collection Variable in AJCC for the female genital cancers. This data item was previously collected for the female genital cancers as: Vulva SSF #10, Vagina SSF #1, Cervix SSF #1, Corpus Carcinoma SSF #1, Corpus Sarcoma SSF #1, Ovary SSF #2, Fallopian Tube SSF #1, Peritoneum Female Genital SSF #1, and Placenta SSF #2.
Codes
01FIGO Stage I
02FIGO Stage IA
03FIGO Stage IA1
04FIGO Stage IA2
05FIGO Stage IB
06FIGO Stage IB1
07FIGO Stage IB2
08FIGO Stage IC
09FIGO Stage IC1
10FIGO Stage IC2
11FIGO Stage IC3
20FIGO Stage II
21FIGO Stage IIA
22FIGO Stage IIA1
23FIGO Stage IIA2
24FIGO Stage IIB
30FIGO Stage III
31FIGO Stage IIIA
32FIGO Stage IIIA1
33FIGO Stage IIIAi
34FIGO Stage IIIAii
35FIGO Stage IIIA2
36FIGO Stage IIIB
37FIGO Stage IIIC
38FIGO Stage IIIC1
39FIGO Stage III2
40FIGO Stage IV
41FIGO Stage IVA
42FIGO Stage IVB
97Not applicable: Carcinoma in situ (intraepithelial, noninvasive, preinvasive)
98Not applicable: Information not collected for this case
(If this item is required by your standard setter, use of code 98 will result in an edit error.)
99Not documented in medical record
FIGO stage unknown, not assessed or unknown if assessed
Each Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.
FIN CODING SYSTEMRetired
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
3520017201212.2
Alternate Name:
XML NAACCR ID:
PARENT XML ELEMENT:
Description
The NAACCR UDSC retired this data item in Version 12.2, as of January 1, 2012.
FIRST COURSE CALC METHODRetired
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
1500201313
Alternate Name:
XML NAACCR ID:
PARENT XML ELEMENT:
Description
The NAACCR UDSC retired this data item in Version 13, as of January 1, 2013.
FOLLOWING REGISTRYRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
244010CoC4915 - 4924
Alternate Name:
XML NAACCR ID:followingRegistry
PARENT XML ELEMENT:Tumor
Description
Records the FIN of the registry responsible for following the patient.
Rationale
The number is essential to NCDB for monitoring data submissions, ensuring the accuracy of data, and identifying areas for special studies.
 
Instructions for Coding
CoC maintains the codes, including those for non-hospital sources of reporting.

For facilities with 7-digit FINs, consisting of a constant “6” followed by 6-digit facility-specific codes in the range of 6020009-6953290 that were assigned by CoC before January 1, 2001: Enter all FIN codes of this type as 3 zeroes, followed by the constant “6” and the 6-digit facility-specific codes.

For facilities with FINs greater than or equal to 10000000 that were assigned by CoC after January 1, 2001: Enter FIN codes of this type as 2 zeroes followed by the full 8-digit code. These sometimes are called CoC FIN 10-digit codes.  
Note: This item is not supported by CoC as of January 1, 2010, (the respective NPI item is required).
Codes (in addition to CoC assigned codes)
0000000000Case not reported by a facility
0099999999Case reported, but facility number is unknown
FOLLOW-UP CONTACT--CITYRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
184250SEER19975.12879 - 2928
Alternate Name:
XML NAACCR ID:followUpContactCity
PARENT XML ELEMENT:Tumor
Description
Name of the city of the follow-up contact’s current usual residence. If the patient has multiple tumors, the follow-up contact city of residence should be the same for all tumors.
Rationale
Sometimes registries carry out follow-up by contacting the patient and other contacts by a letter or phone call to ascertain their vital status. When a patient's current address is unknown or the patient is for some reason not to be contacted (e.g., patient is a minor child), the most current name, address and phone number of another contact, such as a relative or neighbor are needed. This information may also be useful for conducting research studies.
FOLLOWUP CONTACT--COUNTRYRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
18473NAACCR201313475 - 477
Alternate Name:
XML NAACCR ID:followupContactCountry
PARENT XML ELEMENT:Tumor
Description
Country code for the address of follow-up contact’s current usual residence. If the patient has multiple tumors, the country of follow-up contact residence should be the same for all tumors. This data item became part of the NAACCR transmission record effective with Volume II, Version 13 in order to include country and state for each geographic item and to use interoperable codes. It supplements the item FOLLOW UP CONTACT--STATE [1844].
Rationale
Country of patient’s residence at follow-up is an important element of patient’s residential history profile and is useful for understanding risk factors, assessment of patient prognosis, and chances for survival.
Codes
Use the International Standards Organization (ISO) 3166-1 Country Three Character Codes, whenever possible, augmented by custom codes. See Appendix B for complete list of country names and corresponding three character alpha codes.
Custom codes for historic use only
ZZNNorth America NOS
ZZCCentral America NOS
ZZSSouth America NOS
ZZPPacific NOS
ZZEEurope NOS
ZZFAfrica NOS
ZZAAsia NOS
ZZXNon-US NOS
ZZUUnknown
Custom codes for historic use only
XNINorth American Islands
XCBOther Caribbean Islands
XENEngland, Channel Islands, Isle of Man
XSCScandinavia
XGRGermanic Countries
XSLSlavic Countries
CSKCzechoslovakia (former)
YUGYugoslavia (former)
XUMUkraine and Moldova
XNFNorth Africa
XSDSudanese Countries
XWFWest Africa
XSFSouth Africa
XEFEast Africa
XIFAfrican Islands
XETEthiopia and Eritrea
XAPArabian Peninsula
XISIsrael and Palestine
XCRCaucasian Republics of former USSR
XOROther Asian Republics of former USSR
XSESoutheast Asia
XMSMalaysia, Singapore, Brunei
XCHChina, NOS
XMLMelanesian Islands
XMCMicronesian Islands
XPLPolynesian Islands
FOLLOW-UP CONTACT--NAMERevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
239460SEER19975.14604 - 4663
Alternate Name:
XML NAACCR ID:followUpContactName
PARENT XML ELEMENT:Tumor
Description
First and last name, in natural order, of a person, other than the patient or a physician, who can be contacted to obtain follow-up information for the patient. If the patient has multiple tumors, Follow-up Contact-Name should be the same for all tumors.
Rationale
Sometimes registries carry out follow-up by contacting the patient and other contacts by a letter or phone call to ascertain their vital status. When a patient's current address is unknown or the patient is for some reason not to be contacted (e.g., patient is a minor child), the most current name, address and phone number of another contact, such as a relative or neighbor are needed. This information may also be useful for conducting research studies.
FOLLOW-UP CONTACT--NO&STRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
239260SEER19975.14664 - 4723
Alternate Name:
XML NAACCR ID:followUpContactNost
PARENT XML ELEMENT:Tumor
Description
The number and street address or the rural mailing address of the follow-up contact’s current usual residence. This can be used to generate a follow-up inquiry, and must correspond to the other fields in the follow-up contact address. If the patient has multiple tumors, Follow-Up Contact--No&St should be the same for all tumors.

U.S. addresses should conform to the USPS Postal Addressing Standards. These standards are referenced in USPS Pub. 28, November 2000, Postal Addressing Standards. The current USPS Pub. 28 may be found and downloaded from the following website: http://pe.usps.gov/cpim/ftp/pubs/Pub28/pub28.pdf.

Canadian addresses should conform to the Canada Postal Guide. The current Canadian Postal Address standards may be found at the following website: http://www.canadapost.ca.
Rationale
Sometimes registries carry out follow-up by contacting the patient and other contacts by a letter or phone call to ascertain their vital status. When a patient's current address is unknown or the patient is for some reason not to be contacted (e.g., patient is a minor child), the most current name, address and phone number of another contact, such as a relative or neighbor are needed. This information may also be useful for conducting research studies.
Note: Prior to Version 5, Follow-Up Contact fields may have been used for patient current address in the NAACCR record layout.
FOLLOW-UP CONTACT--POSTALRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
18469SEER19975.12931 - 2939
Alternate Name:
XML NAACCR ID:followUpContactPostal
PARENT XML ELEMENT:Tumor
Description
Postal code for the address of the follow-up contact’s current usual residence. If the patient has multiple tumors, the Follow-up Contact-Postal should be the same for all tumors. For U.S. residents, use either the 5-digit or the extended 9-digit ZIP code. Blanks follow the 5-digit code. For Canadian residents, use the 6-character, alphanumeric postal code. Blanks follow the 6-character code. When available, enter postal code for other countries.
Rationale
Sometimes registries carry out follow-up by contacting the patient and other contacts by a letter or phone call to ascertain their vital status. When a patient's current address is unknown or the patient is for some reason not to be contacted (e.g., patient is a minor child), the most current name, address and phone number of another contact, such as a relative or neighbor are needed. This information may also be useful for conducting research studies.
Codes (in addition to U.S., Canadian, and foreign postal codes)
888888888Resident of country other than the United States (including its possessions, etc.) or Canada, and postal code unknown
999999999Resident of the United States (including its possessions, etc.) or Canada, and postal code unknown
FOLLOW-UP CONTACT--STATERevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
18442SEER19975.12929 - 2930
Alternate Name:
XML NAACCR ID:followUpContactState
PARENT XML ELEMENT:Tumor
Description
USPS abbreviation for the state (including U.S. territories, commonwealths, or possessions), or Canada Post abbreviation for the Canadian province/territory of the follow-up contact’s current usual residence. If the patient has multiple tumors, the follow-up contact state should be the same for all tumors. Effective with NAACCR Volume II, Version 13, a new data item, FollowUp Contact--Country [1847] was added to the standard transmission record layout. The UDS Committee expects the new item to supplement the use of Follow-Up Contact--State [1844].
Rationale
Sometimes registries carry out follow-up by contacting the patient and other contacts by a letter or phone call to ascertain their vital status. When a patient's current address is unknown or the patient is for some reason not to be contacted (e.g., patient is a minor child), the most current name, address and phone number of another contact, such as a relative or neighbor are needed. This information may also be useful for conducting research studies.
Codes (in addition to USPS and Canadian Postal Service abbreviations)
CDResident of Canada, NOS (province/territory unknown)
USResident of United States, NOS (state/commonwealth/territory/possession unknown)
XXResident of country other than the United States (including its territories, commonwealths, or possessions) or Canada, and country is known
YYResident of country other than the United States (including its territories, commonwealths, or possessions) or Canada, and country is unknown
ZZResidence unknown
FOLLOW-UP CONTACT--SUPPLRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
239360SEER2003104724 - 4783
Alternate Name:
XML NAACCR ID:followUpContactSuppl
PARENT XML ELEMENT:Tumor
Description
This data item provides the ability to store additional address information such as the name of a place or facility, a nursing home, or the name of an apartment complex. It can be used to generate a follow-up inquiry, and must correspond to the other fields in the follow-up contact address. If the patient has multiple tumors, Follow-Up Contact--Suppl should be the same for all tumors.
Rationale
Sometimes registries carry out follow-up by contacting the patient and other contacts by a letter or phone call to ascertain their vital status. When a patient's current address is unknown or the patient is for some reason not to be contacted (e.g., patient is a minor child), the most current name, address and phone number of another contact, such as a relative or neighbor are needed. This information may also be useful for conducting research studies.
FOLLOW-UP SOURCERevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
17901CoC2801 - 2801
Alternate Name:Follow-Up Method (pre-96 CoC)
XML NAACCR ID:followUpSource
PARENT XML ELEMENT:Tumor
Description
Records the source from which the latest follow-up information was obtained.
Rationale
For registries performing follow-up, this field helps evaluate the success rates of various methods of follow-up. It also can be used to report to institutions the source of follow-up information that is sent to them. When there is a conflict in follow-up information, knowing the source can help resolve the inconsistency.
Codes
0Reported hospitalization
1Readmission
2Physician
3Patient
4Department of Motor Vehicles
5Medicare/Medicaid file
7Death certificate
8Other
9Unknown, not stated in patient record
FOLLOW-UP SOURCE CENTRALRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
17912NAACCR2006112951 - 2952
Alternate Name:
XML NAACCR ID:followUpSourceCentral
PARENT XML ELEMENT:Tumor
Description
This field is created by the central registry. It records the source from which the consolidated information was obtained on a patient's vital status and date of last contact. Follow-up Source Central would be updated when new or more reliable information becomes available. However, when the existing date of last contact/vital status is deemed to be more reliable than newly obtained information, then neither the date of last contact/vital status nor the follow-up source central would be changed.
Rationale
For central registries performing follow-up, this field could help evaluate the success rates of various methods of follow-up. When new follow-up information conflicts with the existing information, knowing the follow-up source can help resolve any discrepancies.
 Codes
00Follow-up not performed for this patient
(01-29)File Linkages
01Medicare/Medicaid File
02Center for Medicare and Medicaid Services (CMS, formerly HCFA)
03Department of Motor Vehicle Registration
04National Death Index (NDI)
05State Death Tape/Death Certificate File
06County/Municipality Death Tape/ Death Certificate File
07Social Security Administration Death Master File
08Hospital Discharge Data
09Health Maintenance Organization (HMO) file
10Social Security Epidemiological Vital Status Data
11Voter Registration File
12Research/Study Related Linkage
29Linkages, NOS
(30-39)Hospitals and Treatment Facilities
30Hospital in-patient/outpatient
31Casefinding
32Hospital cancer registry
33Radiation treatment center
34Oncology clinic
35Ambulatory surgical center
39Clinic/facility, NOS
(40-49)Physicians
40Attending physician
41Medical oncologist
42Radiation oncologist
43Surgeon
48Other specialist
49Physician, NOS
(50-59)Patient
50Patient contact
51Relative contact
59Patient, NOS
(60-98)Other
60Central or Regional cancer registry
61Internet sources
62Hospice
63Nursing homes
64Obituary
65Other research/study related sources
98Other, NOS
99Unknown source
FUTURE USE TIMELINESS 1Retired
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
211419986200410.1
Alternate Name:
XML NAACCR ID:
PARENT XML ELEMENT:
Description
Reserved for future use for storing date of a central registry processing milestone. No standards have been adopted for this item. The NAACCR UDSC retired this data item in Version 10.1, as of January 1, 2004.
FUTURE USE TIMELINESS 2Retired
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
211519986200410.1
Alternate Name:
XML NAACCR ID:
PARENT XML ELEMENT:
Description
Reserved for future use for storing date of a central registry processing milestone. No standards have been adopted for this item. The NAACCR UDSC retired this data item in Version 10.1, as of January 1, 2004.
GEOLOCATIONID - 1970/80/90New
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
35112NAACCR201818153 - 164
Alternate Name:
XML NAACCR ID:geolocationid19708090
PARENT XML ELEMENT:Tumor
Description
This is a 12 character concatenation of state, county, tract and block group. This data item may be used for epidemiological purposes. For example, to measure cancer incidence in a particular geographic area. Components of this code are used to derive area-based social measures such as poverty or urban/rural codes at the county or tract-level. The codes are primarily derived through the geocoding process.
 
Subfields
State at DX Geocode 1970/80/90 [81]
County at DX Geocode 1970/80/90 [94]
Census Tract 1970/80/90 [110]
Census Block Grp 1970/80/90 [368]
Rationale
The concatenation of these variables into the full 12 character code is primarily a bookkeeping improvement over collecting the components separately. This format aligns with how the U.S census describes geographic entities in its many files and will enable direct linkage with census data over time. This format is also compatible with how the NAACCR geocoder returns information and will remove problems related to the leading zeros in census tracts. And because geocoded county codes are embedded in this field, it is less likely they will be confused with the NAACCR Item [90], County at DX Reported, which is often not associated with the geocoded census tract resulting in an edit failure for county-tract accuracy.

Instructions for coding
A 12 character string, with a maximum of one leading zero, left aligned. The code is generated by geocoding. Only numbers or blanks allowed. No decimal points or other characters allowed.

The codes, with the exception of four 2-character alpha character codes for the State, are the Census Bureau ANSI/FIPS codes. Lists of geographic FIPS codes in census products can be found on the ANSI/FIPS Codes page.

ANSI/FIPS codes follow census boundaries and are only unique when the smallest census boundary code is associated with the larger boundaries. For example, county at diagnosis is essential for investigating epidemiologic pattern at both the county and the census tract level. Census tracts are nested within counties and designated with a 6-digit number code. A given census tract code is commonly repeated within a state in different counties, making census tract numbers unique only when paired with the state and the county. Example from Massachusetts: Rural Franklin County contains a tract 040600 with 2010 population 4,612 people, and urban Suffolk County contains a tract 040600 with 2,444 people.
GEOLOCATIONID - 2000New
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
35212NAACCR201818167 - 178
Alternate Name:
XML NAACCR ID:geolocationid2000
PARENT XML ELEMENT:Tumor
Description
This is a 12 character concatenation of state, county, tract and block group. This data item may be used for epidemiological purposes. For example, to measure cancer incidence in a particular geographic area. Components of this code are used to derive area-based social measures such as poverty or urban/rural codes at the county or tract-level. The codes are primarily derived through the geocoding process.
 
Subfields
State at DX Geocode 2000 [82]
County at DX Geocode2000 [95]
Census Tract 2000 [130]
Census Block Group 2000 [362]
Rationale
The concatenation of these variables into the full 12 character code is primarily a bookkeeping improvement over collecting the components separately. This format aligns with how the U.S census describes geographic entities in its many files and will enable direct linkage with census data over time. This format is also compatible with how the NAACCR geocoder returns information and will remove problems related to the leading zeros in census tracts. And because geocoded county codes are embedded in this field, it is less likely they will be confused with the NAACCR Item [90], County at DX Reported, which is often not associated with the geocoded census tract resulting in an edit failure for county-tract accuracy.

Instructions for coding
A 12 character string, with a maximum of one leading zero, left aligned. The code is generated by geocoding. Only numbers or blanks allowed. No decimal points or other characters allowed.

The codes, with the exception of four 2-character alpha character codes for the State, are the Census Bureau ANSI/FIPS codes. Lists of geographic FIPS codes in census products can be found on the ANSI/FIPS Codes page.

ANSI/FIPS codes follow census boundaries and are only unique when the smallest census boundary code is associated with the larger boundaries. For example, county at diagnosis is essential for investigating epidemiologic pattern at both the county and the census tract level. Census tracts are nested within counties and designated with a 6-digit number code. A given census tract code is commonly repeated within a state in different counties, making census tract numbers unique only when paired with the state and the county. Example from Massachusetts: Rural Franklin County contains a tract 040600 with 2010 population 4,612 people, and urban Suffolk County contains a tract 040600 with 2,444 people.
GEOLOCATIONID - 2010New
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
35312NAACCR201818180 - 191
Alternate Name:
XML NAACCR ID:geolocationid2010
PARENT XML ELEMENT:Tumor
Description
This is a 12 character concatenation of state, county, tract and block group. This data item may be used for epidemiological purposes. For example, to measure cancer incidence in a particular geographic area. Components of this code are used to derive area-based social measures such as poverty or urban/rural codes at the county or tract-level. The codes are primarily derived through the geocoding process.

Subfields
State at DX Geocode 2010 [83]
County at DX Geocode2010 [96]
Census Tract 2010 [135]
Census Block Group 2010 [363]
Rationale
The concatenation of these variables into the full 12 character code is primarily a bookkeeping improvement over collecting the components separately. This format aligns with how the U.S census describes geographic entities in its many files and will enable direct linkage with census data over time. This format is also compatible with how the NAACCR geocoder returns information and will remove problems related to the leading zeros in census tracts. And because geocoded county codes are embedded in this field, it is less likely they will be confused with the NAACCR Item [90], County at DX Reported, which is often not associated with the geocoded census tract resulting in an edit failure for county-tract accuracy.

Instructions for coding
A 12 character string, with a maximum of one leading zero, left aligned. The code is generated by geocoding. Only numbers or blanks allowed. No decimal points or other characters allowed.

The codes, with the exception of four 2-character alpha character codes for the State, are the Census Bureau ANSI/FIPS codes. Lists of geographic FIPS codes in census products can be found on the ANSI/FIPS Codes page.

ANSI/FIPS codes follow census boundaries and are only unique when the smallest census boundary code is associated with the larger boundaries. For example, county at diagnosis is essential for investigating epidemiologic pattern at both the county and the census tract level. Census tracts are nested within counties and designated with a 6-digit number code. A given census tract code is commonly repeated within a state in different counties, making census tract numbers unique only when paired with the state and the county. Example from Massachusetts: Rural Franklin County contains a tract 040600 with 2010 population 4,612 people, and urban Suffolk County contains a tract 040600 with 2,444 people.
Codes:
GEOLOCATIONID - 2020New
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
35412NAACCR201818193 - 204
Alternate Name:
XML NAACCR ID:geolocationid2020
PARENT XML ELEMENT:Tumor
Description
This is a 12 character concatenation of state, county, tract and block group. This data item may be used for epidemiological purposes. For example, to measure cancer incidence in a particular geographic area. Components of this code are used to derive area-based social measures such as poverty or urban/rural codes at the county or tract-level. The codes are primarily derived through the geocoding process.

Subfields
State at DX Geocode 2020 [84]
County at DX Geocode2020 [97]
Census Tract 2020 [125]
Census Block Group 2020 [361]
Rationale
The concatenation of these variables into the full 12 character code is primarily a bookkeeping improvement over collecting the components separately. This format aligns with how the U.S census describes geographic entities in its many files and will enable direct linkage with census data over time. This format is also compatible with how the NAACCR geocoder returns information and will remove problems related to the leading zeros in census tracts. And because geocoded county codes are embedded in this field, it is less likely they will be confused with the NAACCR Item [90], County at DX Reported, which is often not associated with the geocoded census tract resulting in an edit failure for county-tract accuracy.

Instructions for coding
A 12 character string, with a maximum of one leading zero, left aligned. The code is generated by geocoding. Only numbers or blanks allowed. No decimal points or other characters allowed.

The codes, with the exception of four 2-character alpha character codes for the State, are the Census Bureau ANSI/FIPS codes. Lists of geographic FIPS codes in census products can be found on the ANSI/FIPS Codes page.

ANSI/FIPS codes follow census boundaries and are only unique when the smallest census boundary code is associated with the larger boundaries. For example, county at diagnosis is essential for investigating epidemiologic pattern at both the county and the census tract level. Census tracts are nested within counties and designated with a 6-digit number code. A given census tract code is commonly repeated within a state in different counties, making census tract numbers unique only when paired with the state and the county. Example from Massachusetts: Rural Franklin County contains a tract 040600 with 2010 population 4,612 people, and urban Suffolk County contains a tract 040600 with 2,444 people.
GESTATIONAL TROPHOBLASTIC PROGNOSTIC SCORING INDEXNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
38372NAACCR2018181924 - 1925
Alternate Name:
XML NAACCR ID:gestationalTrophoblasticPrognosticScoringIndex
PARENT XML ELEMENT:Tumor
Description
Gestational Trophoblastic Prognostic Scoring Index, a score based on the FIGO-modified World Health Organization (WHO) Prognostic Scoring Index, is used to stratify women with gestational trophoblastic neoplasia in addition to the anatomical stage group. The risk score is appended to the anatomic stage.
Rationale
This data item is required for prognostic stage grouping in AJCC 8th edition, Chapter 56 Gestational Trophoblastic Neoplasms. It was previously collected as Placenta, CS SSF # 1.
Codes
00-25Risk factor score
X9Not documented in medical record
Prognostic scoring index not assessed, or unknown if assessed
Each Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.
GIS COORDINATE QUALITYRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
3662NAACCR36611452 - 453
Alternate Name:
XML NAACCR ID:gisCoordinateQuality
PARENT XML ELEMENT:Tumor
Description
Code indicating the basis of assignment of latitude and longitude coordinates for an individual record from an address. This data item is helpful in identifying cases that were assigned coordinates based on incomplete information, post office boxes, or rural routes. This item is coded at the central registry, not by the reporting facility. Most of the time, this information is provided by geocoding software. Alternatively, a central registry staff member manually assigns the code. Codes are hierarchical, with lower numbers having priority.
Rationale
Spatial analysis of cancer data often requires identifying data records with a high degree of geographic precision. Researchers can use this code as a basis for selecting records with a degree of precision that is appropriate to the study.
Codes
00Coordinates derived from local government-maintained address points, which are based on property parcel locations, not interpolation over a street segment's address range
01Coordinates assigned by Global Positioning System (GPS)
02Coordinates are match of house number and street, and based on property parcel location
03Coordinates are match of house number and street, interpolated over the matching street segment's address range
04Coordinates are street intersections
05Coordinates are at mid-point of street segment (missing or invalid building number)
06Coordinates are address ZIP code+4 centroid
07Coordinates are address ZIP code+2 centroid
08Coordinates were obtained manually by looking up a location on a paper or electronic map
09Coordinates are address 5-digit ZIP code centroid
10Coordinates are point ZIP code of Post Office Box or Rural Route
11Coordinates are centroid of address city (when address ZIP code is unknown or invalid, and there are multiple ZIP codes for the city)
12Coordinates are centroid of county
98Latitude and longitude are assigned, but coordinate quality is unknown
99Latitude and longitude are not assigned, but geocoding was attempted; unable to assign coordinates based on available information
BlankGIS Coordinate Quality not coded
Instructions for Coding: Where multiple codes are applicable, use the lower code value. Note: This data item is similar in function to Census Tract Certainty 1970/80/90 [364] and Census Tract Certainty 2000 [365]. The codes for this data item and the two census tract data items all describe how location information was assigned based on the patient's resident address at the time of diagnosis.

This data item must be populated if Latitude [2352] and Longitude [2354] are also populated.
GLEASON PATTERNS CLINICALNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
38382NAACCR2018181927 - 1928
Alternate Name:
XML NAACCR ID:gleasonPatternsClinical
PARENT XML ELEMENT:Tumor
Description
Prostate cancers are graded using Gleason score or pattern. This data item represents the Gleason primary and secondary patterns from needle core biopsy or TURP.
Rationale
Gleason Patterns Clinical is a Registry Data Collection Variable for Clinical Stage for AJCC. This data item was previously collected as Prostate, CS SSF# 7.
Codes
11Primary pattern 1, secondary pattern 1
12Primary pattern 1, secondary pattern 2
13Primary pattern 1, secondary pattern 3
14Primary pattern 1, secondary pattern 4
15Primary pattern 1, secondary pattern 5
19Primary pattern 1, secondary pattern unknown
21Primary pattern 2, secondary pattern 1
22Primary pattern 2, secondary pattern 2
23Primary pattern 2, secondary pattern 3
24Primary pattern 2, secondary pattern 4
25Primary pattern 2, secondary pattern 5
29Primary pattern 2, secondary pattern unknown
31Primary pattern 3, secondary pattern 1
32Primary pattern 3, secondary pattern 2
33Primary pattern 3, secondary pattern 3
34Primary pattern 3, secondary pattern 4
35Primary pattern 3, secondary pattern 5
39Primary pattern 3, secondary pattern unknown
41Primary pattern 4, secondary pattern 1
42Primary pattern 4, secondary pattern 2
43Primary pattern 4, secondary pattern 3
44Primary pattern 4, secondary pattern 4
45Primary pattern 4, secondary pattern 5
49Primary pattern 4, secondary pattern unknown
51Primary pattern 5, secondary pattern 1
52Primary pattern 5, secondary pattern 2
53Primary pattern 5, secondary pattern 3
54Primary pattern 5, secondary pattern 4
55Primary pattern 5, secondary pattern 5
59Primary pattern 5, secondary pattern unknown
X6Primary pattern unknown, secondary pattern unknown
X7No needle core biopsy/TURP performed
X8Not applicable: Information not collected for this case
(If this information is required by your standard setter, use of code X8 may result in an edit error.)
X9Not documented in medical record
Gleason Patterns Clinical not assessed or unknown if assessed
Each Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.
GLEASON PATTERNS PATHOLOGICALNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
38392NAACCR2018181929 - 1930
Alternate Name:
XML NAACCR ID:gleasonPatternsPathological
PARENT XML ELEMENT:Tumor
Description
Prostate cancers are graded using Gleason score or pattern. This data item represents the Gleason primary and secondary patterns from prostatectomy or autopsy.
Rationale
Gleason Patterns Pathological is a Registry Data Collection Variable for AJCC. This data item was previously collected as Prostate, CS SSF# 9.
Codes
11Primary pattern 1, secondary pattern 1
12Primary pattern 1, secondary pattern 2
13Primary pattern 1, secondary pattern 3
14Primary pattern 1, secondary pattern 4
15Primary pattern 1, secondary pattern 5
19Primary pattern 1, secondary pattern unknown
21Primary pattern 2, secondary pattern 1
22Primary pattern 2, secondary pattern 2
23Primary pattern 2, secondary pattern 3
24Primary pattern 2, secondary pattern 4
25Primary pattern 2, secondary pattern 5
29Primary pattern 2, secondary pattern unknown
31Primary pattern 3, secondary pattern 1
32Primary pattern 3, secondary pattern 2
33Primary pattern 3, secondary pattern 3
34Primary pattern 3, secondary pattern 4
35Primary pattern 3, secondary pattern 5
39Primary pattern 3, secondary pattern unknown
41Primary pattern 4, secondary pattern 1
42Primary pattern 4, secondary pattern 2
43Primary pattern 4, secondary pattern 3
44Primary pattern 4, secondary pattern 4
45Primary pattern 4, secondary pattern 5
49Primary pattern 4, secondary pattern unknown
51Primary pattern 5, secondary pattern 1
52Primary pattern 5, secondary pattern 2
53Primary pattern 5, secondary pattern 3
54Primary pattern 5, secondary pattern 4
55Primary pattern 5, secondary pattern 5
59Primary pattern 5, secondary pattern unknown
X6Primary pattern unknown, secondary pattern unknown
X7No prostatectomy/autopsy performed
X8Not applicable: Information not collected for this case
(If this information is required by your standard setter, use of code X8 may result in an edit error.)
X9Not documented in medical record
Gleason Patterns Pathological not assessed or unknown if assessed
Each Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.
GLEASON SCORE CLINICALNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
38402NAACCR2018181931 - 1932
Alternate Name:
XML NAACCR ID:gleasonScoreClinical
PARENT XML ELEMENT:Tumor
Description
This data item records the Gleason score based on adding the values for primary and secondary patterns in Needle Core Biopsy or TURP.
Rationale
Gleason Score Clinical is a Registry Data Collection Variable for AJCC. This data item was previously collected as Prostate, CS SSF# 8.
Codes
02Gleason score 2
03Gleason score 3
04Gleason score 4
05Gleason score 5
06Gleason score 6
07Gleason score 7
08Gleason score 8
09Gleason score 9
10Gleason score 10
X7No needle core biopsy/TURP performed
X8Not applicable: Information not collected for this case
(If this information is required by your standard setter, use of code X8 may result in an edit error.)
X9Not documented in medical record
Gleason Score Clinical not assessed or unknown if assessed
Each Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.
GLEASON SCORE PATHOLOGICALNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
38412NAACCR2018181933 - 1934
Alternate Name:
XML NAACCR ID:gleasonScorePathological
PARENT XML ELEMENT:Tumor
Description
This data item records the Gleason score based on adding the values for primary and secondary patterns from prostatectomy or autopsy.
Rationale
Gleason Score Pathological is a Registry Data Collection Variable for AJCC. This data item was previously collected as Prostate, CS SSF# 10.
Codes
02Gleason score 2
03Gleason score 3
04Gleason score 4
05Gleason score 5
06Gleason score 6
07Gleason score 7
08Gleason score 8
09Gleason score 9
10Gleason score 10
X7No prostatectomy done
X8Not applicable: Information not collected for this case
(If this information is required by your standard setter, use of code X8 may result in an edit error.)
X9Not documented in medical record
Gleason Score Pathological not assessed or unknown if assessed
Each Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.
GLEASON TERTIARY PATTERNNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
38422NAACCR2018181935 - 1936
Alternate Name:
XML NAACCR ID:gleasonTertiaryPattern
PARENT XML ELEMENT:Tumor
Description
Prostate cancers are graded using Gleason score or pattern. This data item represents the tertiary pattern value from prostatectomy or autopsy.
Rationale
Tertiary Gleason pattern on prostatectomy is a Registry Data Collection Variable for AJCC. This data item was previously collected as Prostate, CS SSF# 11.
Codes
10Tertiary pattern 1
20Tertiary pattern 2
30Tertiary pattern 3
40Tertiary pattern 4
50Tertiary pattern 5
X7No prostatectomy/autopsy performed
X8Not applicable: Information not collected for this case
(If this information is required by your standard setter, use of code X8 may result in an edit error.)
X9Not documented in medical record
Gleason Tertiary Pattern not assessed or unknown if assessed
Each Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.
GRADERevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
4401SEER/CoC569 - 569
Alternate Name:Grade, Differentiation, or Cell Lineage Indicator (SEER/CCCR)
Grade/Differentiation (CoC)
XML NAACCR ID:grade
PARENT XML ELEMENT:Tumor
Description
Code for the grade or degree of differentiation of the reportable tumor. For lymphomas and leukemias, field also is used to indicate T-, B-, Null-, or NK-cell origin.

Note: Code 8 was adopted for use with lymphoma cases diagnosed in 1995 and later.
Codes  

See the grade tables on page 67 of ICD-O-3.16 See also the most recent CoC STORE manual and SEER Program Code Manual, for site specific coding rules and conversions.

1Grade I
2Grade II
3Grade III
4Grade IV
5T-cell
6B-cell
7Null cell
8NK (natural killer) cell
9Grade/differentiation unknown, not stated, or not applicable
Comment: Use the most recent Hematopoietic and Lymphoid rules for assigning grades 5-8.
GRADE (73-91) ICD-O-1Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
19731SEER2605 - 2605
Alternate Name:
XML NAACCR ID:gradeIcdO1
PARENT XML ELEMENT:Tumor
Description
Area for retaining the grade portion (1 digit) of the ICD-O-1 or field trial grade code entered before a conversion to ICD-O-2. See grouped data item Morph (73-91) ICD-O-1 [1970] in Appendix E. The item name includes years 1973-91. However, some states may have used the codes for cases before 1973.

Codes
For cases diagnosed before 1992, contains the ICD-O-1 or field trial 1-digit grade code as originally coded, if available.18, 19

 

GRADE CLINICALNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
38431NAACCR2018181286 - 1286
Alternate Name:
XML NAACCR ID:gradeClinical
PARENT XML ELEMENT:Tumor
Description
This data item records the grade of a solid primary tumor before any treatment (surgical resection or initiation of any treatment including neoadjuvant).

For cases diagnosed January 1, 2018, and later, this data item, along with Grade Pathological and Grade Post-Neoadjuvant, replaces NAACCR Data Item Grade [440] as well as SSF’s for cancer sites with alternative grading systems (e.g., breast [Bloom-Richardson], prostate [Gleason]).
Rationale
Grade is a measure of the aggressiveness of the tumor. Grade and cell type are important prognostic indicators for many cancers. For some sites, grade is required to assign the clinical stage group.

For those cases that are eligible AJCC staging, the recommended grading system is specified in the AJCC Chapter. The AJCC Chapter-specific grading systems (codes 1-5) take priority over the generic grade definitions (codes A-E, L, H, 9). For those cases that are not eligible for AJCC staging, if the recommended grading system is not documented, the generic grade definitions would apply.
Codes (Refer to the most recent version of the SSDI Manual for additional site-specific instructions)
Each Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank. Leave blank for cases diagnosed prior to 2018.
GRADE PATH SYSTEMRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
4491AJCC201012571 - 571
Alternate Name:
XML NAACCR ID:gradePathSystem
PARENT XML ELEMENT:Tumor
Description
Indicates whether a two, three or four grade system is used.
Rationale
This item is used to show whether a two, three or four grade system is used. This is the grade system stated in the path report; it is not converted. This item is used in conjunction with Grade Path Value [441] and is abstracted in addition to Grade Differentiation [440].
Codes (Refer to the most recent version of STORE for additional instructions.)
2Two-Grade System
3Three-Grade System
4Four-Grade System
BlankNot a two, three or four grade system; unknown
GRADE PATH VALUERevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
4411</