NAACCR

Description

An alphanumeric code assigned by the reporting facility that identifies the individual abstracting the case.

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.

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)

UNKNOWN

City at diagnosis unknown

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.


ZZN	North America NOS
ZZC	Central America NOS
ZZS	South America NOS
ZZP	Pacific NOS
ZZE	Europe NOS
ZZF	Africa NOS
ZZA	Asia NOS
ZZX	Non-US NOS
ZZU	Unknown
Custom codes for historic use only
XNI	North American Islands
XCB	Other Caribbean Islands
XEN	England, Channel islands, Isle of Man
XSC	Scandinavia
XGR	Germanic Countries
XSL	Slavic Countries
CSK	Czechoslovakia (former)
YUG	Yugoslavia
XUM	Ukraine and Moldova
XNF	North Africa
XSD	Sudanese Countries
XWF	West Africa
XSF	South Africa
XEF	East Africa
XIF	African Islands
XET	Ethiopia and Eritrea
XAP	Arabian Peninsula
XIS	Israel and Palestine
XCR	Caucasian Republics of former USSR
XOR	Other Asian Republics of former USSR
XSE	Southeast Asia
XMS	Malaysia, Singapore, Brunei
XCH	China, NOS
XML	Melanesian Islands
XMC	Micronesian Islands
XPL	Polynesian Islands

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 the latest STORE 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)

UNKNOWN

Patient's address is unknown

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)

888888888	Resident of country other than the United States, U.S. possessions or territories, or Canada and the postal code is unknown
999999999	Resident of the United States (including its possessions, etc.) and the postal code is unknown
999999	Resident of Canada and postal code is unknown

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)

CD	Resident of Canada, NOS (province/territory unknown)
US	Resident of United States, NOS (state/commonwealth/territory/possession unknown)
XX	Resident of country other than the United States (including its territories, commonwealths, or possessions) or Canada, and country is known
YY	Resident of country other than the United States (including its territories, commonwealths, or possessions) or Canada, and country is unknown
ZZ	Residence unknown

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.

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.

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
ZZN	North America NOS
ZZC	Central America NOS
ZZS	South America NOS
ZZP	Pacific NOS
ZZE	Europe NOS
ZZF	Africa NOS
ZZA	Asia NOS
ZZX	Non-US NOS
ZZU	Unknown
Custom codes for historic use only
XNI	North American Islands
SCB	Other Caribbean Islands
XEN	England, Channel Island, Isle of Man
XSC	Scandinavia
XGR	Germanic Countries
XSL	Slavic Countries
CSK	Czechoslovakia (former)
YUG	Yugoslavia (former)
XUM	Ukraine and Moldova
XNF	North Africa
XSD	Sudanese Countries
XWF	West Africa
XSF	South Africa
XEF	East Africa
XIF	African Islands
XET	Ethiopia and Eritrea
XAP	Arabian Peninsula
XIS	Israel and Palestine
XCR	Caucasian Republics of former USSR
XOR	Other Asian Republics of former USSR
XSE	Southeast Asia
XMS	Malaysia, Singapore, Brunei
XCH	China, NOS
XML	Melanesian Islands
XMC	Micronesian Islands
XPL	Polynesian Islands

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

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)

999999	Resident of Canada and postal code unknown
888888888	Resident of country other than the United States (including its possessions, etc.) or Canada, and postal code unknown
999999999	Resident of the United States (including its possessions, etc.) and postal code unknown

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)

CD	Resident of Canada, NOS (province/territory unknown)
US	Resident of United States, NOS (state/commonwealth/territory/possession unknown)
XX	Resident of country other than the United States (including its territories, commonwealths, or possessions) or Canada, and country is known
YY	Resident of country other than the United States (including its territories, commonwealths, or possessions) or Canada, and country is unknown
ZZ	Residence unknown

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.

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.0	0.0 to 100.0 percent basaloid pattern
XXX.5	Basaloid pattern present, percentage not stated
XXX.8	Not 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.9	Not 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.

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.

Codes

0	Adenopathy not identified/not present No lymph nodes >1.5 cm Physician states Rai Stage 0
1	Adenopathy present Presence of lymph nodes >1.5 cm Physician stated Rai Stage I
5	Not applicable: Primary site is not C421
9	Not documented in medical record Adenopathy not assessed or unknown if assessed No Rai stage is documented in the record and there is no documentation of adenopathy Physician states Rai stage II-IV and there is no documentation of adenopathy

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.

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.0	0.0 nanograms/milliliter (ng/mL)
0.1-99999.9	0.1–99,999.9 ng/mL
XXXXX.1	100,000 ng/mL or greater
XXXXX.7	Test ordered, results not in chart
XXXXX.8	Not 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.9	Not 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.

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

0	Within normal limits
1	Above normal and less than 1,000 nanograms/milliliter (ng/mL)
2	1,000 -10,000 ng/mL
3	Greater than 10,000 ng/mL
4	Post-Orchiectomy alpha fetoprotein (AFP) stated to be elevated
5	Post-Orchiectomy alpha fetoprotein (AFP) unknown or not done but pre-orchiectomy AFP was normal
7	Test ordered, results not in chart
8	Not 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.)
9	Not 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.

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.0	0.0 nanograms/milliliter (ng/mL)
0.1-99999.9	0.1–99,999.9 ng/mL
XXXXX.1	100,000 ng/mL or greater
XXXXX.7	Test ordered, results not in chart
XXXXX.8	Not 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.9	Not 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.

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

0	Within normal limits
1	Above normal and less than 1,000 nanograms/milliliter (ng/mL)
2	1,000 -10,000 ng/mL
3	Greater than 10,000 ng/mL
4	Pre-Orchiectomy alpha fetoprotein (AFP) stated to be elevated
7	Test ordered, results not in chart
8	Not 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.)
9	Not 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.

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

0	Negative/normal; within normal limits
1	Positive/elevated
2	Borderline; undetermined if positive or negative
7	Test ordered, results not in chart
8	Not 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.)
9	Not 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.

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.0	0.0 nanograms/milliliter (ng/ml); not detected
0.1-9999.9	0.1-9999.9 ng/ml (Exact value to nearest tenth of ng/ml)
XXXX.1	10,000.0 ng/ml or greater
XXXX.7	Test ordered, results not in chart
XXXX.8	Not 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.9	Not 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.

Description

Age of the patient at diagnosis in complete years. Different tumors for the same patient may have different values.

Codes

000	Less than 1 year old; diagnosed in utero
001	1 year old, but less than 2 years
002	2 years old
...
101	101 years old
...
120	120 years old
999	Unknown age

Description

This item indicates the version of the AJCC TNM API incorporated into the cancer registry software that created the record with TNM staging data in the 8th and later versions. It should be recorded the first time the AJCC Release ID (including a value of 08.01.00) is determined and should be updated each time the related input fields listed below are modified. If the registry software incorporates the AJCC API directly, the value is obtained from AJCC’s API. If the software instead incorporates AJCC’s Cancer Surveillance API, the value can be returned from there. The value indicates the most recent time at least one of the related input items listed below was modified.

A valid value is required for all cases diagnosed 2018 or later that have values entered in the AJCC or related data items. Cases abstracted prior to implementation of this data item will be assigned a value of 08.XX.XX during the conversion to v21.

Rationale

Over time the definitions and other content contained in the AJCC’s API may change. This value indicates the most recent release used to modify at least one of the related input items listed below.

Codes

Note: This data item will be generated by registry software. Blank is allowable in the case that no AJCC or related input items are coded.

Description

This item indicates the version of the AJCC API incorporated into the cancer registry software that created the record with TNM stage data in the 8^th and later versions. It should be recorded the first time the AJCC ID (including a value of 8) is determined. If the registry software incorporates the APCC API directly, the value is obtained from AJCC’s API. If the software instead incorporates AJCC’s Cancer Surveillance API, the value can be returned from there.

A valid value is required for all cases diagnosed 2018 or later that have values entered in the AJCC or related data items. Cases abstracted prior to implementation of this data item will be assigned a value of 08.XX.XX during the conversion to v21.

Rationale

Over time the definitions and other content contained in the AJCC’s API may change. This item identifies the original API content used to code the TNM data.

Codes

Blank is allowable in the case that no AJCC or related input items are coded.

Description

This item indicates the most recently accessed version of the Cancer Surveillance .dll incorporated into the cancer registry software that created the record with stage data diagnosed 2018 and later. AJCC Cancer Surveillance DLL Version Current [2158] will be assigned based on the version of the AJCC Cancer Surveillance .dll in use in the registry software system. It must be updated every time a new version is incorporated into your system and all relevant cases should be updated to reflect the same value.

For cases diagnosed prior to 2018, this field should remain blank.
For cases diagnosed in 2018-2020, this field should be set to the AJCC Cancer Surveillance .dll version in use at the time of implementation.
For cases diagnosed in 2018 and later abstracted after implementation, use the AJCC Cancer Surveillance .dll version in use at the time the case is being abstracted.

The value is obtained from the .dll.

Formerly: AJCC Cancer Surveillance API Version Current

Rationale

Over time, the definitions and other content contained in the .dll may change. This item identifies the current .dll content used to code the items.

This data item will be generated by registry software.

The AJCC Cancer Surveillance API contains contents to support collection of AJCC's TNM, EOD, SSDIs, and directly entered Summary Stage 2018. The underlying contents are loaded from AJCC's API and SEER's web service. The API is versioned independently from the imported contents.

The value indicates the version of the Cancer Surveillance API used most recently to code the items listed below and is obtained from the API. It should be recorded the first time the AJCC ID (including a value of XX) and/or Schema ID is determined and should be updated each time an updated AJCC Cancer Surveillance API is implemented.

Related Input Fields
AJCC TNM Clin T (also Path and Post Therapy T) [1001, 1011, 1021]
AJCC TNM Clin N (also Path and Post Therapy N) [1002, 1012, 1022]
AJCC TNM Clin M (also Path and Post Therapy M) [1003, 1013, 1023]
AJCC TNM Clin Stage Group (also Path and Post Therapy Stage Group [1004, 1014, 1024])

Summary Stage 2018 [764]

EOD Primary Tumor [772]
EOD Regional Nodes [774]
EOD Mets [776]

All SSDIs (see SSDI manual for complete list).

Codes

Description

This item indicates the version of the AJCC Cancer Surveillance .dll incorporated into the cancer registry software that created the record with stage data diagnosed 2018 and later. It should be recorded the first time the AJCC ID (including a value of XX) and/or Schema ID are determined using the .dll. The value is obtained from the .dll.

Formerly: AJCC Cancer Surveillance API Version Original

Rationale

Over time, the definitions and other content contained in the .dll may change. This item identifies the original content used to code the items.

This data item will be generated by registry software.

The AJCC Cancer Surveillance API contains contents to support collection of AJCC’s TNM, EOD, and directly entered Summary Stage 2018. The underlying contents are loaded from AJCC’s API and SEER’s web service. The API is versioned independently from the imported contents.

The value indicates the version of the AJCC Cancer Surveillance API originally used to code the items listed below and is obtained from the API. It should be recorded the first time the AJCC ID (including a value of XX) and/or Schema ID is determined and should not be updated each time the related input fields are modified. However, if changes made to the diagnosis and/or date of diagnosis result in a different AJCC ID and/or Schema ID, the value for AJCC Cancer Surveillance DLL Version Original should be reset.

Related Input Fields
AJCC TNM Clin T (also Path and Post Therapy T) [1001, 1011, 1021]
AJCC TNM Clin N (also Path and Post Therapy N) [1002, 1012, 1022]
AJCC TNM Clin M (also Path and Post Therapy M) [1003, 1013, 1023]
AJCC TNM Clin Stage Group (also Path and Post Therapy Stage Group [1004, 1014, 1024])

Summary Stage 2018 [764]

EOD Primary Tumor [772]
EOD Regional Nodes [774]
EOD Mets [776]

All SSDIs (see SSDI manual for complete list).

Codes

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.

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)

88	Not applicable, no code assigned for this case in the current AJCC Staging Manual.
Blank	Information 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.

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)

88	Not applicable, no code assigned for this case in the current AJCC Staging Manual.
Blank	Information 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.

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
Blank	No suffix needed or appropriate; not recorded

Note: Refer to the current AJCC Cancer Staging Manual for staging rules.

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)

88	Not applicable, no code assigned for this case in the current AJCC Staging Manual.
99	Unknown, 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.

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)

88	Not applicable, no code assigned for this case in the current AJCC Staging Manual.
Blank	Information 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.

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
Blank	No information available; not recorded

Note: Refer to the current AJCC Cancer Staging Manual for staging rules.

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)

88	Not applicable, no code assigned for this case in the current AJCC Staging Manual.
Blank	Information 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.

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)

88	Not applicable, no code assigned for this case in the current AJCC Staging Manual.
Blank	Information 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.

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 only
Blank	No suffix needed or appropriate; not recorded

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)

88	Not applicable, no code assigned for this case in the current AJCC Staging Manual.
99	Unknown, 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.

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)

88	Not applicable, no code assigned for this case in the current AJCC Staging Manual.
Blank	Information 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.

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
Blank	No information available; not recorded

Note: Refer to the current AJCC Cancer Staging Manual for staging rules.

Description

Detailed site-specific codes for the post therapy clinical (yc) metastases (M) as defined by AJCC.

Clinical, pathological, and post therapy yc and yp stage data are given four 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 post neoadjuvant therapy staging remains the same as that assigned in the clinical stage before initiation of neoadjuvant therapy or primary systemic/radiation therapy, cM or pM.

Codes (in addition to those published in the AJCC Cancer Staging Manual)

88	Not applicable, no code assigned for this case in the current AJCC Staging Manual.
Blank	This 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.

Description

Detailed site-specific codes for the post therapy clinical (yc) nodes (N) as defined by AJCC.

Clinical, pathological, and post therapy yc and yp stage data are given four 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 following the completion of neoadjuvant therapy (satisfying the definition for that disease site) before planned surgical resection or primary treatment consisting of systemic and/or radiation therapy.

Codes (in addition to those published in the AJCC Cancer Staging Manual)

88	Not applicable, no code assigned for this case in the current AJCC Staging Manual.
Blank	This 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.

Description

Detailed site-specific codes for the post therapy clinical (yc) N category suffix as defined by AJCC.

Clinical, pathological, and post therapy yc and yp stage data are given four 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
Blank	No suffix needed or appropriate; not recorded

Description

Detailed site-specific codes for the post therapy clinical (yc) stage group as defined by AJCC.

Clinical, pathological, and post therapy yc and yp stage data are given four 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) before planned surgical resection or primary treatment consisting of systemic and/or radiation therapy, and the M status defined during the diagnostic workup.

Codes (in addition to those published in the AJCC Cancer Staging Manual)

88	Not applicable, no code assigned for this case in the current AJCC Staging Manual.
99	Unknown, 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.

Description

Detailed site-specific codes for the post therapy clinical (yc) tumor (T) as defined by AJCC.

Clinical, pathological, and post therapy yc and yp stage data are given four 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) before planned surgical resection or primary treatment consisting of systemic and/or radiation therapy.

Codes (in addition to those published in the AJCC Cancer Staging Manual)

88	Not applicable, no code assigned for this case in the current AJCC Staging Manual.
Blank	This 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.

Description

Detailed site-specific codes for the post therapy clinical (yc) tumor T category suffix as defined by AJCC.

Clinical, pathological, and post therapy yc and yp stage data are given four 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
Blank	No information available; not recorded

Note: Refer to the current AJCC Cancer Staging Manual for staging rules.

Description

Detailed site-specific codes for the postneoadjuvant therapy category metastases (M) as defined by AJCC.

Clinical, pathological, and post therapy yc and yp stage data are given four 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)

88	Not applicable, no code assigned for this case in the current AJCC Staging Manual.
Blank	This 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.

Description

Detailed site-specific codes for the postneoadjuvant therapy Path nodes (N) as defined by AJCC.

Clinical, pathological, and post therapy yc and yp stage data are given four 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)

88	Not applicable, no code assigned for this case in the current AJCC Staging Manual.
Blank	This 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.

Description

Detailed site-specific codes for the postneoadjuvant therapy Path N category suffix as defined by AJCC.

Clinical, pathological, and post therapy yc and yp stage data are given four 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 only
Blank	No suffix needed or appropriate; not recorded

Description

Detailed site-specific codes for the postneoadjuvant therapy Path stage group as defined by AJCC.

Clinical, pathological, and post therapy yc and yp stage data are given four 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)

88	Not applicable, no code assigned for this case in the current AJCC Staging Manual.
99	Unknown, 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.

Description

Detailed site-specific codes for the postneoadjuvant therapy Path tumor (T) as defined by AJCC.

Clinical, pathological, and post therapy yc and yp stage data are given four 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)

88	Not applicable, no code assigned for this case in the current AJCC Staging Manual.
Blank	This 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.

Description

Detailed site-specific codes for the postneoadjuvant therapy Path T category suffix as defined by AJCC.

Clinical, pathological, and post therapy yc and yp stage data are given four 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
Blank	No information available; not recorded

Note: Refer to the current AJCC Cancer Staging Manual for staging rules.

Description

The NAACCR UDSC retired this data item in Version 12, as of January 1, 2010.

Description

Testing for ALK rearrangement is performed for patients with advanced non-small cell lung cancer (NSCLC) to identify tumors which are sensitive to small-molecule ALK kinase inhibitors.

Rationale

ALK rearrangement is recommended by treatment guidelines for patients with advanced lung cancer as a prognostic marker and factor in determining appropriate therapy. It is a new data item for cases diagnosed 01/01/2021+.

Codes

0	Normal ALK negative Negative for rearrangement, no rearrangement identified, no mutations (somatic) identified, not present, not detected
1	Abnormal Rearrangement identified/detected: EML4-ALK, KIF5B-ALK, TFG-ALK, and/or KLC1-ALK
2	Rearrangement identified/detected: Other ALK Rearrangement not listed in code 1
4	Rearrangement, NOS
7	Test ordered, results not in chart
8	Not 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.
9	Not documented in medical record ALK Rearrangement not assessed or unknown if assessed
Blank	Diagnosis year is prior to 2021

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.

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

0	Conclusive term
1	Ambiguous term only
2	Ambiguous term followed by conclusive term
9	Unknown term

Refer to Table 2 in Chapter III for a list of ambiguous terms.

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.

Codes

0	Anemia not present Hgb >=11.0 g/dL Physician states Rai Stage 0-II
1	Anemia present Hgb <11.0 g/dL
5	Not applicable: Primary site is not C421
6	Lab value unknown, physician states patient is anemic Physician states Rai Stage III
7	Test ordered, results not in chart
9	Not documented in medical record Anemia not assessed or unknown if assessed No Rai stage is documented in the record and there is no documentation of anemia Physician states Rai stage IV and there is no documentation of anemia

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.

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.

Description

Code indicating whether or not an autopsy was performed.

Codes

0	Not applicable; patient alive
1	Autopsy performed
2	No autopsy performed
9	Patient expired, unknown if autopsy performed
This data item is no longer supported by CoC (As of January 1, 2003).

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

0	No B symptoms (asymptomatic) Classified as "A" by physician when asymptomatic
1	Any 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
8	Not 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.)
9	Not 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.

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.

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,¹⁵ page 22, for behavior codes and definitions.

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,¹⁴page 66, for behavior codes and definitions.

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.0	0.0 milligram/deciliter (mg/dL) 0.0 micromole/liter (umol/L)
0.1-999.9	0.1-999.9 milligram/deciliter (mg/dL) 0.1-999.9 micromole/liter (umol/L)
XXX.1	1000 milligram/deciliter (mg/dL) or greater 1000 micromole/liter (umol/L) or greater
XXX.7	Test ordered, results not in chart
XXX.8	Not 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.9	Not 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.

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

1	Milligrams per deciliter (mg/dL)
2	Micromoles/liter (umol/L)
7	Test ordered, results not in chart
8	Not 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.)
9	Not 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.

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

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
ZZN	North America NOS
ZZC	Central American NOS
ZZS	South America NOS
ZZP	Pacific NOS
ZZE	Europe NOS
ZZF	Africa NOS
ZZA	Asia NOS
ZZX	Non-US NOS
ZZU	Unknown
Custom codes for historic use only
XNI	North American Islands
XCB	Other Caribbean Islands
XEN	England, Channel Islands, Isle of Man
XSC	Scandinavia
XGR	Germanic Countries
XSL	Slavic Countries
CSK	Czechoslovakia (former)
YUG	Yugoslavia (former)
XUM	Ukraine and Moldova
XNF	North Africa
XSD	Sudanese Countries
XWF	West Africa
XSF	South Africa
XEF	East Africa
XIF	African Islands
XET	Ethiopia and Eritrea
XAP	Arabian Peninsula
XIS	Israel and Palestine
XCR	Caucasian Republics of former USSR
XOR	Other Asian Republics of former USSR
XSE	Southeast Asia
XMS	Malaysia, Singapore, Brunei
XCH	China, NOS
XML	Melanesian Islands
XMC	Micronesian Islands
XPL	Polynesian 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).

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

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

0	Bone invasion not present/not identified on imaging
1	Bone invasion present/identified on imaging
8	Not 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.)
9	Not 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.

Description

The BRAF oncoprotein is involved in transmitting cell growth and proliferation signals from KRAS and NRAS. The BRAF V600E mutation is associated with poorer prognosis and predicts lack of response to anti-EGFR therapies.

Rationale

BRAF mutational analysis is recommended in clinical guidelines for patients with advanced colorectal cancer as a prognostic marker and factor in determining appropriate therapy. It is a new data item for cases diagnosed 1/1/2021+.

Codes

0	Normal BRAF negative, BRAF wild type Negative for (somatic) mutations, no alterations, no (somatic) mutations identified, not present, not detected
1	Abnormal (mutated)/detected: BRAF V600E (c.1799T>A) mutation
2	Abnormal (mutated)/detected, but not BRAF V600E (c.1799T>A) mutation
4	Abnormal (mutated), NOS
7	Test ordered, results not in chart
8	Not 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.)
9	Not documented in medical record BRAF not assessed or unknown if assessed
Blank	Diagnosis year is prior to 2021

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.

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

01	Diffuse astrocytoma, IDH-mutant (9400/3)
02	Diffuse astrocytoma, IDH-wildtype (9400/3)
03	Anaplastic astrocytoma, IDH-mutant (9401/3)
04	Anaplastic astrocytoma, IDH-wildtype (9401/3)
05	Glioblastoma, IDH-wildtype (9440/3)
06	Oligodendroglioma, IDH-mutant and 1 p/19q co-deleted (9450/3)
07	Anaplastic oligodendroglioma, IDH-mutant and 1 p/19q co-deleted (9451/3)
08	Medulloblastoma, SHH-activated and TP53-wildtype (9471/3)
09	Embryonal tumor with multilayered rosettes, C19MC-altered (9478/3)
85	Not applicable: Histology not 9400/3, 9401/3, 9440/3, 9450/3, 9451/3, 9471/3, 9478/3
86	Benign or borderline tumor
87	Test ordered, results not in chart
88	Not 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.)
99	Not 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.

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.0	No mass/tumor found
0.1	Greater than 0.0 and less than or equal to 0.1
0.2-99.9	0.2 - 99.9 millimeters
XX.1	100 millimeters or larger
A0.1-A9.9	Stated as "at least" some measured value of 0.1 to 9.9
AX.0	Stated as greater than 9.9 mm
XX.8	Not 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.9	Not 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.

Description

Carbohydrate Antigen (CA) 19-9 Pretreatment Lab Value records the CA 19-9 value prior to treatment. CA 19-9 is a tumor marker that has prognostic significance for pancreatic cancer.

Rationale

CA 19-9 Pretreatment Lab Value is a strong predictor of resectability in the absence of metastatic disease. It is a new data item for cases diagnosed 01/01/2021+.

Codes

0.0	0.0 Units/milliliter (U/ml) exactly
0.1-9999.9	0.1-9999.9 U/ml Exact value to nearest tenth in U/ml)
XXXX.1	10,000 U/ml or greater
XXXX.2	Lab value not available, physician states CA 19-9 is negative/normal
XXXX.3	Lab value not available, physician states CA 19-9 is positive/elevated/high
XXXX.7	Test ordered, results not in chart
XXXX.8	Not 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.9	Not documented in medical record CA (Carbohydrate Antigen) 19-9 Pretreatment Lab Value not assessed or unknown if assessed
Blank	Diagnosis year is prior to 2021

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.

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

0	Negative/normal; within normal limits
1	Positive/elevated
2	Stated as borderline; undetermined whether positive or negative
7	Test ordered, results not in chart
8	Not 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)
9	Not 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.

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

1	No evidence of this tumor
2	Evidence of this tumor
9	Unknown, indeterminate whether this tumor is present, not stated in patient record

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

10	Reporting Hospital, NOS
20	Pathology Department Review (surgical pathology reports, autopsies, or cytology reports)
21	Daily Discharge Review (daily screening of charts of discharged patients in the medical records department)
22	Disease Index Review (review of disease index in the medical records department)
23	Radiation Therapy Department/Center
24	Laboratory Reports (other than pathology reports, code 20)
25	Outpatient Chemotherapy
26	Diagnostic Imaging/Radiology (other than radiation therapy, codes 23; includes nuclear medicine)
27	Tumor Board
28	Hospital Rehabilitation Service or Clinic
29	Other Hospital Source (including clinic, NOS or outpatient department, NOS)
30	Physician-Initiated Case
40	Consultation-only or Pathology-only Report (not abstracted by reporting hospital)
50	Independent (non-hospital) Pathology-Laboratory Report
60	Nursing Home-Initiated Case
70	Coroner's Office Records Review
75	Managed Care Organization (MCO) or Insurance Records
80	Death Certificate (case identified through death clearance)
85	Out-of-State Case Sharing
90	Other Non-Reporting Hospital Source
95	Quality Control Review (case initially identified through quality control activities such as casefinding audit of a regional or central registry)
99	Unknown

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

0000	Patient alive at last contact
7777	State death certificate not available
7797	State death certificate available but underlying cause of death is not coded

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

0	CEA negative/normal; within normal limits
1	CEA positive/elevated
2	Borderline
3	Undetermined if positive or negative (normal values not available) AND no MD interpretation
7	Test ordered, results not in chart
8	Not 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.)
9	Not 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.

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.0	0.0 nanograms/milliliter (ng/m) exactly
0.1-9999.9	0.1-9999.9 ng/ml (Exact value to nearest tenth in ng/ml)
XXXX.1	10,000 ng/ml or greater
XXXX.7	Test ordered, results not in chart
XXXX.8	Not 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.9	Not 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.

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

0	Census block group assignment was attempted, but the value could not be determined
1-9	Census block group values as defined by the Census Bureau
Blank	Census Block Group 2000 not coded

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

0	Census block group assignment was attempted, but the value could not be determined
1-9	Census block group values as defined by the Census Bureau
Blank	Census Block Group 2010 not coded

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-9	Census block group values as defined by the Census Bureau
Blank	Census 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.

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

0	Census block group assignment was attempted, but the value could not be determined
1-9	Census block group values as defined by the Census Bureau
Blank	Census Block Grp 1970/80/90 [368] not coded

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

0	Not tracted
1	1970 Census Tract Definitions
2	1980 Census Tract Definitions
3	1990 Census Tract Definitions
Blank	Census 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.

Description

Code for the patient’s usual industry, using U.S. Census Bureau codes (2000 Census²⁶ is preferable) according to coding procedures recommended for death certificates.²⁵ 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.²⁶ The 1990 Census codes are recommended for tumors diagnosed before January 1, 2003.²⁴ 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 [email protected] 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.

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:
9880	Retired
9890	Housewife, homemaker, volunteers, student, child or infant, patient, disabled, inmate, or individual who did not work
9990	Blank text, unknown, don't know, not applicable, refused, or information is inadequate to select a code
Blank	Coding 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. See the following website for the NIOSH Industry and Occupation Computerized Coding System (NIOCCS) to look up a single industry and occupation code, crosswalk a single record, or create an account to perform batch processing: https://www.cdc.gov/niosh/topics/coding/code.html.
For more information related to the U.S. Census Bureau codes, see the following websites:

Overview: https://www.census.gov/topics/employment/industry-occupation/guidance.html

Crosswalk: https://www.census.gov/topics/employment/industry-occupation/guidance/code-lists.html

Index: https://www.census.gov/topics/employment/industry-occupation/guidance/indexes.html

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.²² 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.²⁴^{, 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 [email protected] 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.

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
9020	Volunteers
9050	Student
9060	Retired
9100	Child or infant, patient, disabled, inmate, or individual who did not work
9900	Blank text, unknown, don't know, not applicable, refused or information is inadequate to select a code
Blank	Coding 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 [email protected] or (513) 841-4467.

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

Overview: https://www.census.gov/topics/employment/industry-occupation/guidance.html

Crosswalk: https://www.census.gov/topics/employment/industry-occupation/guidance/code-lists.html. 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: https://www.census.gov/topics/employment/industry-occupation/guidance/indexes.html

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

1	1970 Census
2	1980 Census
3	1990 Census
4	2000 Census
5	2010 Census
7	Other coding system
9	Unknown coding system
Blank	Not collected

Note: 2000 Census codes for occupation and industry are recommended for tumors diagnosed on or after January 1, 2003.²⁶The 1990 Census codes are recommended for tumors diagnosed before January 1, 2003.²⁴For more information, see the U.S. Bureau of the Census website at: at: https://www.census.gov/topics/employment/industry-occupation/guidance.html.

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

1	Census tract/BNA based on complete and valid street address of residence
2	Census tract/BNA based on residence ZIP + 4
3	Census tract/BNA based on residence ZIP + 2
4	Census tract/BNA based on residence ZIP code only
5	Census tract/BNA based on ZIP code of P.O. Box
6	Census 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
9	Not assigned, geocoding attempted
Blank	Not 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.

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

1	Census tract based on complete and valid street address of residence
2	Census tract based on residence ZIP + 4
3	Census tract based on residence ZIP + 2
4	Census tract based on residence ZIP code only
5	Census tract based on ZIP code of P.O. Box
6	Census 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
9	Not assigned, geocoding attempted
Blank	Not 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.

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

1	Census tract based on complete and valid street address of residence
2	Census tract based on residence ZIP + 4
3	Census tract based on residence ZIP + 2
4	Census tract based on residence ZIP code only
5	Census tract based on ZIP code of P.O. Box
6	Census 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
9	Not assigned, geocoding attempted
Blank	Not 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.

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

1	0% - <5% poverty
2	5% - <10% poverty
3	10% - <20% poverty
4	20% - 100% poverty
9	Unknown or not applicable

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-999998	Valid FIPS Codes
000000	Area not census-tracted
999999	Area census-tracted, but census tract is not available
Blank	Census 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.

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-999998	Valid FIPS code
000000	Area not census tracted
999999	Area census-tracted, but census tract is not available
Blank	Census 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.

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-999998	Valid FIPS code
000000	Area not census tracted
999999	Area census tracted, but census tract is not available
Blank	Census 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.

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

000000	Area not census tracted
000100-999998	Valid FIPS code
999999	Area census tracted, but census tract is not available
Blank	Census 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.

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

1	Census tract based on complete and valid street address of residence
2	Census tract based on residence ZIP + 4
3	Census tract based on residence ZIP + 2
4	Census tract based on residence ZIP code only
5	Census tract based on ZIP code of P.O. Box
6	Census 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
9	Not assigned, geocoding attempted
Blank	Not 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.

Description

This data item was retired for Version 10 because Census Tract--2000 [130] is expected to contain only Census 2000 codes.

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.

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.

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.

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.

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

0	Chromosome 19q deletion/LOH not identified/not present
1	Chromosome 19q deletion/LOH present
6	Benign or borderline tumor
7	Test ordered, results not in chart
8	Not 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.)
9	Not 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.

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

0	Chromosome 1p deletion/LOH not identified/not present
1	Chromosome 1p deletion/LOH identified/present
6	Benign or borderline tumor
7	Test ordered, results not in chart
8	Not 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.)
9	Not 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.

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

0	No loss of chromosome 3
1	Partial loss of chromosome 3
2	Complete loss of chromosome 3
3	Loss of chromosome 3, NOS
7	Test ordered, results not in chart
8	Not 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.)
9	Not 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.

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

0	No gain in chromosome 8q
1	Gain in chromosome 8q
7	Test ordered, results not in chart
8	Not 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.)
9	Not 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.

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.0	Circumferential resection margin (CRM) positive Margin IS involved with tumor Described as "less than 1 millimeter (mm)"
0.1-99.9	Distance of tumor from margin: 0.1- 99.9 millimeters (mm) (Exact size to nearest tenth of millimeter)
XX.0	100 mm or greater
XX.1	Margins clear, distance from tumor not stated Circumferential or radial resection margin negative, NOS No residual tumor identified on specimen
XX.2	Margins cannot be assessed
XX.3	Described as "at least" 1 mm
XX.4	Described as "at least" 2 mm
XX.5	Described as "at least" 3 mm
XX.6	Described as "greater than" 3 mm
XX.7	No 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.8	Not 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.9	Not 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.

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
11	Initial diagnosis in staff physician's office AND PART of first course treatment was done at the reporting facility
12	Initial 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
34	Type 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
35	Case diagnosed before program's Reference Date AND initial diagnosis AND PART OR ALL of first course treatment by reporting facility
36	Type 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
37	Case 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
40	Diagnosis AND all first course treatment given at the same staff physician's office
41	Diagnosis and all first course treatment given in two or more different staff physician offices
42	Non-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

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. The flag also allows cases to be stratified during analyses to identify those never seen at a CoC-accredited facility; e.g., percentage of all cases seen in at least one CoC-accredited facility, evaluation of outcomes by facility status. NPCR will use this flag for facility status stratification.

Codes

0	Abstract prepared at a facility WITHOUT CoC accreditation of its cancer program
1	ANALYTIC abstract prepared at facility WITH CoC accreditation of its cancer program (Includes Class of Case codes 10-22)
2	NON-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)
Blank	Not applicable; DCO

Description

Code the ACoS CoC coding system currently used in the record. CoC codes may be converted from an earlier version.

This item is no longer required by CoC.

Codes

00	No CoC coding system used
01	Pre-1988 (Cancer Program Manual Supplement)
02	1988 Data Acquisition Manual
03	1989 Data Acquisition Manual Revisions
04	1990 Data Acquisition Manual Revisions
05	1994 Data Acquisition Manual (Interim/Revised)
06	ROADS (effective with cases diagnosed 1996-1997)
07	ROADS and 1998 Supplement (effective with cases diagnosed 1998-2002)
08	FORDS (effective with cases diagnosed 2003-2017)
09	STORE (effective with cases diagnosed 2018-2020)
99	Unknown coding system

Description

Code for the ACoS CoC coding system originally used to code the record.

This item is no longer required by CoC.

Codes

00	No CoC coding system used
01	Pre-1988 (Cancer Program Manual Supplement)
02	1988 Data Acquisition Manual
03	1989 Data Acquisition Manual Revisions
04	1990 Data Acquisition Manual Revisions
05	1994 Data Acquisition Manual (Interim/Revised)
06	ROADS (effective with cases diagnosed 1996-1997)
07	ROADS and 1998 Supplement (effective with cases diagnosed 1998-2002)
08	FORDS (effective with cases diagnosed 2003-2017)
09	STORE (effective with cases diagnosed 2018-2020)
99	Original CoC coding system is not known

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

0	2-Digit Nonspecific Extent of Disease (1973-82)
1	2-Digit Site-Specific Extent of Disease (1973-82)
2	13-Digit (expanded) Site-Specific Extent of Disease (1973-1982)
3	4-Digit Extent of Disease (1983-87)
4	10-Digit Extent of Disease, 1988 (1988-2003)
Blank	Cases diagnosed 2004+; or the item is not collected

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.

00000

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

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.

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.

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.

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.

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.

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.

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.

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.

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.

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

0	No match was run (for 1994 and later tumors)
1	Non-Hispanic last name and non-Hispanic maiden name
2	Non-Hispanic last name, did not check maiden name or patient was male
3	Non-Hispanic last name, missing maiden name
4	Hispanic last name, non-Hispanic maiden name
5	Hispanic last name, did not check maiden name or patient was male
6	Hispanic last name, missing maiden name
7	Hispanic Maiden name (females only) (regardless of last name)
Blank	1993 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.

Description

Code identifying the method used to determine ethnicity as recorded in Computed Ethnicity [200].

Codes

0	No match was run, for 1994 and later tumors
1	Census Bureau list of Spanish surnames, NOS
2	1980 Census Bureau list of Spanish surnames
3	1990 Census Bureau list of Spanish surnames
4	GUESS Program
5	Combination list including South Florida names
6	Combination of Census and other locally generated list
7	Combination of Census and GUESS, with or without other lists
8	Other type of match
9	Unknown type of match
Blank	1993 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.

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 PRCDA, or historically 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 2010. 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 2010. 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-997	Valid FIPS code
998	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 for Canadian residents.
999	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.

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 PRCDA, or historically 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 STORE 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-997	County at diagnosis. Valid FIPS code
998	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.
999	County 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.

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 PRCDA, or historically 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-997	County at diagnosis. Valid FIPS code.
998	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.
999	County 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.

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 PRCDA, or historically 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-997	County at diagnosis. Valid FIPS code.
998	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.
999	County 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.

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 PRCDA, or historically 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-997	County at diagnosis. Valid FIPS code.
998	Outside 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.
999	County 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.

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-997	Valid FIPS code
998	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.
999	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.

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)

998	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)
999	County unknown

Note: This data item is no longer supported by CoC (as of January 1, 2003).

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.

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.0	0.0 milligram/deciliter (mg/dl) 0.0 micromole/liter (umol/L)
0.1-99.9	0.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.1	100 mg/dl or greater 100 umol/L or greater
XX.7	Test ordered, results not in chart
XX.8	Not 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.9	Not 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.

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

1	Milligrams/deciliter (mg/dL)
2	Micromoles/liter (umol/L)
7	Test ordered, results not in chart
8	Not 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.)
9	Not 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.

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),¹³ 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.

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),¹³ 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.

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),¹³ for rules and site-specific codes and coding structures.)

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),¹³ for rules and site-specific codes and coding structures.)

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),¹³ for rules and site-specific codes and coding structures.)

Note: This includes only the bone, not the bone marrow.

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),¹³ 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.

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),¹³ for rules and site-specific codes and coding structures.)

Note: This includes only the liver.

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),¹³ for rules and site-specific codes and coding structures.)

Note: This includes only the lung, not pleura or pleural fluid.

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),¹³ for rules and site-specific codes and coding structures.)

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),¹³ for rules and site-specific codes and coding structures.)

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),¹³ for rules and site-specific codes and coding structures.)

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),¹³ for rules and site-specific codes and coding structures.)

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),¹³ for rules and site-specific codes and coding structures.)

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),¹³ for rules and site-specific codes and coding structures.)

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),¹³ for rules and site-specific codes and coding structures.)

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),¹³ for rules and site-specific codes and coding structures.)

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),¹³ for rules and site-specific codes and coding structures.)

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),¹³ for rules and site-specific codes and coding structures.)

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),¹³ for rules and site-specific codes and coding structures.)

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),¹³ for rules and site-specific codes and coding structures.)

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),¹³ for rules and site-specific codes and coding structures.)

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),¹³ for rules and site-specific codes and coding structures.)

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),¹³ for rules and site-specific codes and coding structures.)

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),¹³ for rules and site-specific codes and coding structures.)

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),¹³ for rules and site-specific codes and coding structures.)

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),¹³ for rules and site-specific codes and coding structures.)

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),¹³ for rules and site-specific codes and coding structures.)

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),¹³ for rules and site-specific codes and coding structures.)

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),¹³ for rules and site-specific codes and coding structures.)

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),¹³ for rules and site-specific codes and coding structures.)

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),¹³ for rules and site-specific codes and coding structures.)

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),¹³ for rules and site-specific codes and coding structures.)

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),¹³ for rules and site-specific codes and coding structures.)

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),¹³ for rules and site-specific codes and coding structures.)

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),¹³ for rules and site-specific codes and coding structures.)

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),¹³ for rules and site-specific codes and coding structures.)

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),¹³ 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.

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),¹³ 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.

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),¹³ 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.

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

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

10	No information whatsoever can be inferred from this exceptional value (e.g, unknown whether treatment was administered)
11	No proper value is applicable in this context (Autopsy only)
12	A proper value is applicable but not known (e.g., treatment administered but date is unknown)
Blank	A 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.

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

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.

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 1^stContact [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.

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.

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.

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.

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.

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

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

10	No information whatsoever can be inferred from this exceptional (non-date) value. (e.g., unknown if the diagnosis was initially based on ambiguous terminology).
11	No 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]).
12	A 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).
15	Information 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]).
Blank	A 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.

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

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

10	No information whatsoever can be inferred from this exceptional value (e.g, unknown if therapy was administered)
11	No proper value is applicable in this context (e.g., therapy was not administered)
12	A proper value is applicable but not known (e.g., therapy was administered and date is unknown)
Blank	A 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.

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.

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

12	A proper value is applicable but not known (e.g., date of 1st contact is unknown)
Blank	A 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.

Description

The NAACCR UDSC retired this data item in Version 12, as of January 1, 2010.

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.

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

12	A proper value is applicable but not known (i.e., birth date is unknown)
Blank	A 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.

Description

The NAACCR UDSC retired this data item in Version 11, as of January 1, 2006.

Description

This field is used by the Canadian provinces/territories to record the patient's date of death. See Chapter X for date format.

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

10	No information whatsoever can be inferred from this exceptional value (e.g, patient is not known to be deceased)
11	No proper value is applicable in this context (e.g. patient is alive)
12	A proper value is applicable but not known (e.g., date of death is unknown)
Blank	A 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.

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.

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

12	A proper value is applicable but not known. (e.g., date of diagnosis is unknown)
Blank	A 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.

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

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

10	No information whatsoever can be inferred from this exceptional value (e.g, unknown if patient was an inpatient).
11	No proper value is applicable in this context (e.g., patient was never an inpatient at the reporting facility).
12	A 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).
Blank	A 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.

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

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

10	No information whatsoever can be inferred from this exceptional value (e.g, unknown if patient was an inpatient).
11	No proper value is applicable in this context (e.g., patient was never an inpatient at the reporting facility).
12	A 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).
Blank	A 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.

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.

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

12	A 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).
Blank	A valid date value is provided in item Date of Last Cancer (tumor) Status [1772].

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.

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

12	A proper value is applicable but not known. This event occurred, but the date is unknown (e.g., date of last contact is unknown).
Blank	A 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.

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

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

11	No proper value is applicable in this context (e.g., information on multiple tumors not collected/not applicable for this site).
12	A 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).
15	Information is not available at this time, but it is expected that it will be available later (e.g., single tumor).
Blank	A 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.

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.

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

10	No information whatsoever can be inferred from this exceptional value (that is, unknown if any sentinel lymph node biopsy was performed)
11	No proper value is applicable in this context (for example, no sentinel lymph node biopsy performed; autopsy only cases)
12	A 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)
Blank	A valid date value is provided in item Date of Sentinel Lymph Node Biopsy [832]. Case was diagnosed prior to January 1, 2018.

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.

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

10	No information whatsoever can be inferred from this exceptional value (that is, unknown if any regional lymph node dissection was performed)
11	No proper value is applicable in this context (for example, no regional lymph node dissection was performed; autopsy only cases)
12	A 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)
Blank	A valid date value is provided in item Date of Regional Lymph Node Dissection [682]. Case was diagnosed prior to January 1, 2018.

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.

Description

The NAACCR UDSC retired this data item in Version 6, effective January 1, 1998. See Place of Death [1940].

Description

Death certificate identification number as assigned by the vital statistics office in the place recorded in Place of Death [1940].

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).¹³ 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),¹³ for rules and site-specific codes and coding structures.)

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).¹³ 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),¹³ for rules and site-specific codes and coding structures.)

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).¹³ 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),¹³ for rules and site-specific codes and coding structures.)

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).¹³ 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),¹³ for rules and site-specific codes and coding structures.)

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).¹³ 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),¹³ for rules and site-specific codes and coding structures.)

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).¹³ 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),¹³ for rules and site-specific codes and coding structures.)

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).¹³ 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),¹³ for rules and site-specific codes and coding structures.)

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),¹³ for rules and site-specific codes and coding structures.)

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),¹³ for rules and site-specific codes and coding structures.)

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),¹³ for rules and site-specific codes and coding structures.)

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),¹³ for rules and site-specific codes and coding structures.)

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),¹³ for rules and site-specific codes and coding structures.)

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),¹³ for rules and site-specific codes and coding structures.)

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),¹³ for rules and site-specific codes and coding structures.)

Description

Flag to indicate whether the derived AJCC stage was derived from CS or EOD codes.

Codes

blank	Not derived
1	AJCC fields derived from Collaborative Stage
2	AJCC fields derived from EOD (prior to 2004)

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.

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.

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.

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.

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),¹³ for rules and site-specific codes and coding structures.)

0	Neoadjuvant therapy was not administered as part of the first course of therapy
1	Neoadjuvant therapy was administered as part of the first course of therapy
9	Unknown

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.

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

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),¹³ for rules and site-specific codes and coding structures.)

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

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),¹³ for rules and site-specific codes and coding structures.)

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

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),¹³ for rules and site-specific codes and coding structures.)

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

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),¹³ for rules and site-specific codes and coding structures.)

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

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),¹³ for rules and site-specific codes and coding structures.)

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

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),¹³ for rules and site-specific codes and coding structures.)

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

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),¹³ for rules and site-specific codes and coding structures.)

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

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),¹³ for rules and site-specific codes and coding structures.)

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

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),¹³ for rules and site-specific codes and coding structures.)

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

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),¹³ for rules and site-specific codes and coding structures.)

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

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),¹³ for rules and site-specific codes and coding structures.)

Description

This data item stores the Derived Rai stage value derived from the values coded in the following SSDIs for the Lymphoma-CLL/SLL schema (9823/3).

Lymphocytosis [3885]
Adenopathy [3804]
Organomegaly [3907]
Anemia [3811]
Thrombocytopenia [3933]

The Rai stage is only applicable for Chronic Lymphocytic Leukemia/Small Lymphocytic Lymphoma (CLL/SLL) (9823/3) cases where the primary site is bone marrow (C421). For cases with a primary site other than bone marrow (C421), the derived Rai stage will be 8 and all the SSDIs will be coded to 5.

Derivation will be run on all cases diagnosed 1/1/2018 and forward.

Rationale

The Derived Rai stage can be used to evaluate disease spread at diagnosis, treatment patterns and outcomes over time.

Codes

0	Lymphocytosis
1	Lymphocytosis and Adenopathy
2	Lymphocytosis and Organomegaly (Adenopathy is any value other than 5)
3	Lymphocytosis and Anemia (Adenopathy and Organomegaly are any value other than 5)
4	Lymphocytosis and Thrombocytopenia (Adenopathy, Organomegaly and Anemia are any value other than 5)
8	Does not apply, primary site not bone marrow (C421) (All 5 SSDIs should be set to 5)
9	Unknown (All 5 SSDIs are 9 or blank; at least one is set to 9 OR Lymphocytosis is 0,7,9 OR Lymphocytosis is blank and one of the other SSDIs is a value other than 5 or 9)

This field should be left blank for all cases diagnosed prior to 2018, for schemas other than 00795, and when not required by standard setter.

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

0	Stage 0
0A	Stage 0A
01S	Stage 0is
1	Stage I
1A	Stage IA
1A1	Stage IA1
1A2	Stage IA2
1B	Stage IB
1B1	Stage IB1
1C	Stage IC
1S	Stage IS
2	Stage 2
2A	Stage 2A
2A1	Stage 2A1
2A2	Stage 2A2
2B	Stage 2B
2C	Stage 2C
3	Stage 3
3A	Stage 3A
3B	Stage 3B
3C	Stage 3C
3C1	Stage 3C1
3C2	Stage 3C2
4	Stage 4
4A	Stage 4A
4A1	Stage 4A1
4A2	Stage 4A2
4B	Stage 4B
4C	Stage 4C
OC	Stage OC
88	Not applicable
99	Unknown
Blank	The algorithm has not been run

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

1	Clinical
2	Pathologic
3	Clinical and pathologic information used
9	Unknown

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

1	Clinical
2	Pathologic
3	Clinical and pathologic information used
9	Unknown

Description

This data item is needed to store the results of the derived algorithmic calculation of SEER Combined 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

0A	Stage 0
0IS	Stage 0is
1	Stage I
1A	Stage IA
1A2	Stage IA2
1B	Stage IB
1B1	Stage IB1
1B2	Stage IB2
1C	Stage IC
1S	Stage IS
2	Stage 2
2A	Stage 2A
2A1	Stage
2A2	Stage IIA2
2B	Stage IIB
2C	Stage IIC
3	Stage III
3A	Stage IIIA
3B	Stage IIIB
3C	Stage IIIC
3C1	Stage IIIC1
3C2	Stage IIIC2
4	Stage IV
4A	Stage IVA
4A1	Stage IVA1
4A2	Stage IV42
4B	Stage IVB
4C	Stage IV4C
OC	Occult
88	Not applicable
99	Unknown
Blank	The algorithm has not been run

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

1	Clinical
2	Pathologic
3	Clinical and pathologic information used
9	Unknown

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)

88	Not applicable
Blank	Not derived

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)

88	Not applicable
Blank	Not derived

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)

88	Not applicable
Blank	Not derived

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

0	Stage 0
0A	Stage 0A
0IS	Stage 0is
1	Stage I
1A	Stage IA
1A1	Stage IA1
1A2	Stage IA2
1B	Stage IB
1B1	Stage IB1
1B2	Stage IB2
1C	Stage IC
1S	Stage IS
2	Stage II
2A	Stage IIA
2A1	Stage IIA1
2A2	Stage IIA2
2B	Stage IIB
2C	Stage IIC
3	Stage III
3A	Stage IIIA
3B	Stage IIIB
3C	Stage IIIC
3C1	Stage IIIC1
3C2	Stage IIIC2
4	Stage IV
4A	Stage IVA
4A1	Stage IVA1
4A2	Stage IVA2
4B	Stage IVB
4C	Stage IVC
OC	Occult
88	Not applicable
99	Unknown
Blank	Algorithm has not been run

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),¹³ for rules and site-specific codes and coding structures.)

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),¹³ for rules and site-specific codes and coding structures.)

Blank	Not derived
1	SS1977 derived from Collaborative Stage
2	SS1977 derived from EOD (prior to 2004)

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),¹³ for rules and site-specific codes and coding structures.)

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),¹³ for rules and site-specific codes and coding structures.)

1	SS2000 derived from Collaborative Stage
2	SS2000 derived from EOD (prior to 2004)
Blank	Not derived

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

0	In situ
1	Localized
2	Regional, direct extension only
3	Regional, regional lymph nodes only
4	Regional, direct extension and regional lymph nodes
7	Distant
8	Benign, borderline
9	Unknown if extension or metastasis (unstaged, unknown, or unspecified) Death certificate only case

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

1	Positive histology
2	Positive cytology
3	Positive histology PLUS - positive immunophenotyping AND/OR positive genetic studies (Used only for hematopoietic and lymphoid neoplasms M-9590/3-9992/3)
4	Positive microscopic confirmation, method not specified
5	Positive laboratory test/marker study
6	Direct visualization without microscopic confirmation
7	Radiography and/or other imaging techniques without microscopic confirmation
8	Clinical diagnosis only (other than 5, 6, or 7)
9	Unknown 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.

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.

Description

Data linkages between the NPCR and the National Breast and Cervical Cancer Early Detection (NBCCED) and/or Colorectal Cancer Early Detection (CRCED) programs are to capture post-linkage information at the patient and tumor level. Information on the fact (Early Detection Program Minimum Data Element (EDP MDE) Link variable) is to be reported in this data item. For reportable breast, cervical, and colorectal cancer cases, use the EDP MDE Link variable to record results from the registry’s data linkage with the appropriate NBCCEDP/CRCEDP program(s) in the state/territory/jurisdiction. The EDP MDE Link variable identifies breast, cervical, or colorectal cancer cases in the registry database that matched the same patient and tumor in the NBCCEDP/CRCEDP data set, indicating that the cancer was identified through that screening program (i.e.; patient Jane Doe right breast infiltrating duct carcinoma diagnosed in 2004 in the registry database matched the same Jane Doe right breast infiltrating duct carcinoma diagnosed in 2004 in the NBCCEDP data set).

Rationale

This data item classifies those cancers first identified through the screening programs and allows analyses to evaluate trends, identify disparities, and evaluate program success. This linkage process also has the potential to identify cancers not reported to the cancer registry.

Codes

0	Breast, cervical, or colorectal cancer record sent for linkage, no match for this cancer with the Early Detection Program (EDP) data
1	Breast, cervical, or colorectal cancer record sent for linkage, match for this cancer with EDP data
Blank	Breast, cervical, or colorectal cancer record not sent for linkage, or linkage results are pending, or record not a breast, cervical, or colorectal cancer

Description

Data linkages between the NPCR and the National Breast and Cervical Cancer Early Detection (NBCCED) and/or Colorectal Cancer Early Detection (CRCED) programs are to capture post-linkage information at the patient and tumor level. Information on the fact (Early Detection Program Minimum Data Element (EDP MDE) Link variable) is to be reported in the EDP MDE Link data item and the date that linkage was conducted is to be reported in the EDP MDE Link Date data item. For reportable breast, cervical, and colorectal cancer cases, use the EDP MDE Link Date variable to record results from the registry’s data linkage with the appropriate NBCCEDP/CRCEDP program(s) in the state/territory/jurisdiction. The EDP MDE Link Date variable identifies the date that breast, cervical, or colorectal cancer cases in the registry database matched the same patient and tumor in the NBCCEDP/CRCEDP data set, indicating that the cancer was identified through that screening program (i.e.; patient Jane Doe right breast infiltrating duct carcinoma diagnosed in 2004 in the registry database matched the same Jane Doe right breast infiltrating duct carcinoma diagnosed in 2004 in the NBCCEDP data set).

Rationale

This data item records the date cancers first linked with data from the screening programs and allows analyses to evaluate trends, identify disparities, and evaluate program success. This linkage process also has the potential to identify cancers not reported or reported late to the cancer registry.

Description

Epidermal growth factor receptor (EGFR) mutational analysis is performed for patients with advanced non-small cell lung cancer (NSCLC) to identify patients with certain activating mutations in the EGFR gene which are sensitive to tyrosine kinase inhibitors.

Rationale

EGFR mutational analysis is recommended by treatment guidelines for patients with advanced lung cancer as a prognostic marker and factor in determining appropriate therapy. It is a new data item for cases diagnosed 01/01/2021+.

Codes

0	Normal EGFR negative, EGFR wild type Negative for mutations, no alterations, no mutations (somatic) identified, not present, not detected
1	Abnormal (mutated)/detected in exon(s) 18, 19, 20, and/or 21
2	Abnormal (mutated)/detected but not in exon(s) 18, 19, 20, and/or 21
4	Abnormal (mutated)/detected, NOS, exon(s) not specified
7	Test ordered, results not in chart
8	Not 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.
9	Not documented in medical record EGFR not assessed or unknown if assessed
Blank	Diagnosis year is prior to 2021

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.

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

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)

00	None No distant metastasis Unknown if distant metastasis
88	Not 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
99	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.

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)

000	In situ, intraepithelial, noninvasive
800	No evidence of primary tumor
999	Unknown; 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.)

Description

EOD Prostate Pathologic Extension is used to assign pT category for prostate cancer based on radical prostatectomy specimens.

Rationale

EOD Prostate Pathologic Extension is used in EOD. It was previously collected as Prostate Pathological Extension, and Prostate, CS SSF# 3.

Codes (See the most current version of EOD (Prostate) (https://staging.seer.cancer.gov/) for rules and site-specific codes and coding structures.)

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)

000	None
800	Regional lymph node(s), NOS Lymph node(s), NOS
888	Not applicable–e.g., CNS, hematopoietic
999	Unknown

Note: See the most current version of EOD (https://staging.seer.cancer.gov/) for rules and site-specific codes and coding structures.

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 Edition⁸ for site-specific codes and coding rules for all EOD fields.)

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 Edition⁸ for site-specific codes and coding rules for all EOD fields.)

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 Edition⁸ for site-specific codes and coding rules for all EOD fields.)

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)¹⁰ for codes.)

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)¹⁰ for codes.)

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 Instructions⁹ for codes.)

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

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.

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

0	U: Upper (Cervical/Proximal esophagus to lower border of azygos vein)
1	M: Middle (Lower border of azygos vein to lower border of inferior pulmonary vein)
2	L: Lower (Lower border of inferior pulmonary vein to stomach, including gastroesophageal junction)
9	X: 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.

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

000	ER negative, or stated as less than 1%
001-100	1-100 percent
R10	Stated as 1-10%
R20	Stated as 11-20%
R30	Stated as 21-30%
R40	Stated as 31-40%
R50	Stated as 41-50%
R60	Stated as 51-60%
R70	Stated as 61-70%
R80	Stated as 71-80%
R90	Stated as 81-90%
R99	Stated as 91-100%
XX7	Test done, results not in chart
XX8	Not 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.)
XX9	Not documented in medical record Estrogen Receptor, Percent Positive Range not assessed or unknown if a

ABSTRACTED BY
Item #	Length	Source of Standard	Year Implemented	Version Implemented	Year Retired	Version Retired	Column #
570	3	CoC					756 - 758

Alternate Name:
XML NAACCR ID:	abstractedBy
PARENT XML ELEMENT:	Tumor

ACCESSION NUMBER--HOSP
Item #	Length	Source of Standard	Year Implemented	Version Implemented	Year Retired	Version Retired	Column #
550	9	CoC					745 - 753

Alternate Name:	Accession Number (CoC)
XML NAACCR ID:	accessionNumberHosp
PARENT XML ELEMENT:	Tumor

ADDR AT DX--CITY
Item #	Length	Source of Standard	Year Implemented	Version Implemented	Year Retired	Version Retired	Column #
70	50	CoC					74 - 123

CHAPTER X:

DATA DICTIONARY

Alternate Name:	City or Town (pre-96 CoC) City/Town at Diagnosis (CoC)
XML NAACCR ID:	addrAtDxCity
PARENT XML ELEMENT:	Tumor

ADDR AT DX--COUNTRY
Item #	Length	Source of Standard	Year Implemented	Version Implemented	Year Retired	Version Retired	Column #
102	3	NAACCR	2013	13			464 - 466

Alternate Name:
XML NAACCR ID:	addrAtDxCountry
PARENT XML ELEMENT:	Tumor

ADDR AT DX--NO & STREET							Revised
Item #	Length	Source of Standard	Year Implemented	Version Implemented	Year Retired	Version Retired	Column #
2330	60	SEER					4348 - 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

ADDR AT DX--POSTAL CODE
Item #	Length	Source of Standard	Year Implemented	Version Implemented	Year Retired	Version Retired	Column #
100	9	CoC					126 - 134

Alternate Name:	Zip Code (pre-CoC) Postal Code (CCCR) Postal Code at Diagnosis (CoC)
XML NAACCR ID:	addrAtDxPostalCode
PARENT XML ELEMENT:	Tumor

ADDR AT DX--STATE
Item #	Length	Source of Standard	Year Implemented	Version Implemented	Year Retired	Version Retired	Column #
80	2	CoC	2011	12.2			124 - 125

Alternate Name:	State at Diagnosis (CoC) State (pre-96 CoC)
XML NAACCR ID:	addrAtDxState
PARENT XML ELEMENT:	Tumor

ADDR AT DX--SUPPLEMENTL
Item #	Length	Source of Standard	Year Implemented	Version Implemented	Year Retired	Version Retired	Column #
2335	60	SEER	2003	10			4408 - 4467

ADDR CURRENT--CITY
Item #	Length	Source of Standard	Year Implemented	Version Implemented	Year Retired	Version Retired	Column #
1810	50	SEER					2803 - 2852

Alternate Name:	City/Town--Current (CoC)
XML NAACCR ID:	addrCurrentCity
PARENT XML ELEMENT:	Patient

ADDR CURRENT--COUNTRY
Item #	Length	Source of Standard	Year Implemented	Version Implemented	Year Retired	Version Retired	Column #
1832	3	NAACCR	2013	13			467 - 469

Alternate Name:
XML NAACCR ID:	addrCurrentCountry
PARENT XML ELEMENT:	Patient

ADDR CURRENT--NO & STREET
Item #	Length	Source of Standard	Year Implemented	Version Implemented	Year Retired	Version Retired	Column #
2350	60	SEER					4468 - 4527

Alternate Name:	Patient Address (Number and Street)-Current (CoC)
XML NAACCR ID:	addrCurrentNoStreet
PARENT XML ELEMENT:	Patient

ADDR CURRENT--POSTAL CODE
Item #	Length	Source of Standard	Year Implemented	Version Implemented	Year Retired	Version Retired	Column #
1830	9	SEER					2855 - 2863

Alternate Name:	Postal Code--Current (CoC)
XML NAACCR ID:	addrCurrentPostalCode
PARENT XML ELEMENT:	Patient

ADDR CURRENT--STATE
Item #	Length	Source of Standard	Year Implemented	Version Implemented	Year Retired	Version Retired	Column #
1820	2	SEER					2853 - 2854

Alternate Name:	State--Current (CoC)
XML NAACCR ID:	addrCurrentState
PARENT XML ELEMENT:	Patient

ADDR CURRENT--SUPPLEMENTL
Item #	Length	Source of Standard	Year Implemented	Version Implemented	Year Retired	Version Retired	Column #
2355	60	SEER	2003	10			4528 - 4587

Alternate Name:	Patient Address (Number and Street) Current--Supplemental (CoC)
XML NAACCR ID:	addrCurrentSupplementl
PARENT XML ELEMENT:	Patient

ADENOID CYSTIC BASALOID PATTERN
Item #	Length	Source of Standard	Year Implemented	Version Implemented	Year Retired	Version Retired	Column #
3803	5	NAACCR					1839 - 1843

Alternate Name:
XML NAACCR ID:	adenoidCysticBasaloidPattern
PARENT XML ELEMENT:	Tumor

ADENOPATHY							Revised
Item #	Length	Source of Standard	Year Implemented	Version Implemented	Year Retired	Version Retired	Column #
3804	1	NAACCR	2018	18			1910 - 1910

Alternate Name:	RAI Classification: Adenopathy
XML NAACCR ID:	adenopathy
PARENT XML ELEMENT:	Tumor

AFP POST-ORCHIECTOMY LAB VALUE
Item #	Length	Source of Standard	Year Implemented	Version Implemented	Year Retired	Version Retired	Column #
3805	7	NAACCR	2018	18			1959 - 1965

Alternate Name:	Testis Serum Markers: AFP (Alpha Fetoprotein) Post-Orchiectomy Lab Value
XML NAACCR ID:	afpPostOrchiectomyLabValue
PARENT XML ELEMENT:	Tumor

AFP POST-ORCHIECTOMY RANGE
Item #	Length	Source of Standard	Year Implemented	Version Implemented	Year Retired	Version Retired	Column #
3806	1	NAACCR	2018	18			1966 - 1966

AFP PRE-ORCHIECTOMY LAB VALUE
Item #	Length	Source of Standard	Year Implemented	Version Implemented	Year Retired	Version Retired	Column #
3807	7	NAACCR	2018	18			1951 - 1957