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

Item Search:

CHAPTER X:

DATA DICTIONARY

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

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

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

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

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

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

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

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

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

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

The first four numbers specify the year and the last five numbers are the numeric order in which the patient was entered into the registry database. Within a registry, all primaries for an individual must have the same accession number. The first four digits must be greater than or equal to 1944.
Rationale
This data item protects the identity of the patient and allows cases to be identified on a local, state, and national level. If the central registry preserves this number, they can refer to it when communicating with the reporting facilities. It also provides a way to link computerized follow-up reports from reporting facilities into the central database.
ADDR AT DX--CITY
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
7050CoC95 - 144
Alternate Name:City or Town (pre-96 CoC)
City/Town at Diagnosis (CoC)
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Name of the city in which the patient resides at the time the reportable tumor was diagnosed. If the patient resides in a rural area, record the name of the city used in the mailing address. If the patient has multiple primaries, the city of residence may be different for each primary.
Codes (in addition to valid City)
UNKNOWNCity at diagnosis unknown
ADDR AT DX--COUNTRY
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
1023NAACCR201313436 - 438
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
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.
Custom codes for both historic and future use
ZZNNorth America NOS
ZZCCentral America NOS
ZZSSouth America NOS
ZZPPacific NOS
ZZEEurope NOS
ZZFAfrica NOS
ZZAAsia NOS
ZZXNon-US NOS
ZZUUnknown
Custom codes for historic use only
XNINorth American Islands
XCBOther Caribbean Islands
XENEngland, Channel islands, Isle of Man
XSCScandinavia
XGRGermanic Countries
XSLSlavic Countries
CSKCzechoslovakia (former)
YUGYugoslavia
XUMUkraine and Moldova
XNFNorth Africa
XSDSudanese Countries
XWFWest Africa
XSFSouth Africa
XEFEast Africa
XIFAfrican Islands
XETEthiopia and Eritrea
XAPArabian Peninsula
XISIsrael and Palestine
XCRCaucasian Republics of former USSR
XOROther Asian Republics of former USSR
XSESoutheast Asia
XMSMalaysia, Singapore, Brunei
XCHChina, NOS
XMLMelanesian Islands
XMCMicronesian Islands
XPLPolynesian Islands
ADDR AT DX--NO & STREET
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
233060CoC3628 - 3687
Alternate Name:Patient Address (Number and Street) at Diagnosis (CoC)
Number and Street (pre-96 CoC)
XML NAACCR ID:
XML PARENT ELEMENT:
Description
The number and street address or the rural mailing address of the patient’s residence at the time the reportable tumor was diagnosed. If the patient has multiple tumors, address at diagnosis may be different for each tumor. Additional address information such as facility, nursing home, or name of apartment complex should be entered in Addr At DX--Supplementl [2335]. Do not update this item if patient moves after diagnosis.

U.S. addresses should conform to the U.S. Postal Service (USPS) Postal Addressing Standards. These standards are referenced in USPS Publication 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
Addresses that are formatted to conform to USPS Postal Addressing Standards can be more properly geocoded by geographic information systems (GIS) software and vendors to the correct census tract, which is required by NPCR and SEER registries. 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).
Codes (in addition to valid street address)
UNKNOWNPatient's address is unknown
ADDR AT DX--POSTAL CODE
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
1009CoC147 - 155
Alternate Name:Zip Code (pre-CoC)
Postal Code (CCCR)
Postal Code at Diagnosis (CoC)
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Postal code for the address of the patient's residence at the time the reportable tumor is diagnosed. If the patient has multiple tumors, the postal code may be different for each tumor. 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. Blanks follow the 6-character code.When available, enter the postal code for other countries.
Codes (in addition to known US and Canadian or other postal codes)
888888888Resident of country other than the United States, U.S. possessions or territories, or Canada and the postal code is unknown
999999999Resident of the United States (including its possessions, etc.) and the postal code is unknown
999999Resident of Canada and postal code is unknown
ADDR AT DX--STATE
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
802CoC201112.2145 - 146
Alternate Name:State at Diagnosis (CoC)
State (pre-96 CoC)
XML NAACCR ID:
XML PARENT ELEMENT:
Description
USPS abbreviation for the state, territory, commonwealth, U.S. possession, or CanadaPost abbreviation for the Canadian province/territory in which the patient resides at the time the reportable tumor is diagnosed. If the patient has multiple primaries, the state of residence may be different for each tumor. Effective with NAACCR Volume II, Version 13 a new data item, Addr at Dx--Country [102] was added to the standard transmission record layout. The UDS Committee expects the new items to supplement the use of Addr at Dx--State [80].
Codes (in addition to USPS abbreviations)
CDResident of Canada, NOS (province/territory unknown)
USResident of United States, NOS (state/commonwealth/territory/possession unknown)
XXResident of country other than the United States (including its territories, commonwealths, or possessions) or Canada, and country is known
YYResident of country other than the United States (including its territories, commonwealths, or possessions) or Canada, and country is unknown
ZZResidence unknown
ADDR AT DX--SUPPLEMENTL
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
233560CoC2003103688 - 3747
Alternate Name:Patient Address (Number and Street) at Diagnosis--Supplemental (CoC)
XML NAACCR ID:
XML PARENT ELEMENT:
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. If the patient has multiple tumors, address at diagnosis may be different for each tumor. Do not use this item for information stored in other address items such as Addr At DX--NO&Street [2330].
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.
ADDR CURRENT--CITY
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
181050CoC2131 - 2180
Alternate Name:City/Town--Current (CoC)
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Name of city of the patient’s current usual residence. If the patient has multiple tumors, the current city of residence should be the same for all tumors.
Rationale
"Current address" can be used to measure the regional "cancer burden" (cost, medical care needs), especially in major retirement regions. Sometimes central registries carry out follow-up by contacting the patients by a letter or telephone calls to ascertain their vital status. The most current reported address and telephone number are needed. This information is also useful for conducting interview studies.
ADDR CURRENT--COUNTRY
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
18323NAACCR201313439 - 441
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Country code for the address of patient’s current usual residence. If the patient has multiple tumors, the current country of residence should be the same for all tumors. This data item became part of the NAACCR transmission record effective with Volume II, Version 13 in order to include country and state for each geographic item and to use interoperable codes. It supplements the item Addr Current--State [1820].
Rationale
Country of patient’s current residence is an important element of the patient’s residential history profile and is useful for understanding risk factors, assessment of patient prognosis, and chances for survival.
Codes Use the International Standards Organization (ISO) 3166-1 Country Three Character Codes, whenever possible, augmented by custom codes, see below. See Appendix B for complete list of country names and corresponding three character alpha codes.
Custom codes for historic use only
ZZNNorth America NOS
ZZCCentral America NOS
ZZSSouth America NOS
ZZPPacific NOS
ZZEEurope NOS
ZZF Africa NOS
ZZAAsia NOS
ZZXNon-US NOS
ZZUUnknown
Custom codes for historic use only
XNINorth American Islands
SCBOther Caribbean Islands
XENEngland, Channel Island, Isle of Man
XSCScandinavia
XGRGermanic Countries
XSL Slavic Countries
CSKCzechoslovakia (former)
YUGYugoslavia (former)
XUMUkraine and Moldova
XNFNorth Africa
XSDSudanese Countries
XWF West Africa
XSFSouth Africa
XEFEast Africa
XIFAfrican Islands
XETEthiopia and Eritrea
XAPArabian Peninsula
XISIsrael and Palestine
XCRCaucasian Republics of former USSR
XOROther Asian Republics of former USSR
XSESoutheast Asia
XMSMalaysia, Singapore, Brunei
XCHChina, NOS
XMLMelanesian Islands
XMCMicronesian Islands
XPLPolynesian Islands
ADDR CURRENT--NO & STREET
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
235060CoC3748 - 3807
Alternate Name:Patient Address (Number and Street)-Current (CoC)
XML NAACCR ID:
XML PARENT ELEMENT:
Description
The number and street address or the rural mailing address of the patient’s current usual residence. This can be used to generate a follow-up inquiry, and must correspond to other fields in the current address. If the patient has multiple tumors, the current address should be the same. Additional address information such as facility, nursing home, or name of apartment complex should be entered in item Addr Current--Supplemental [2335].

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

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

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

Coding Instructions (summary of USPS guidelines)

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

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

APT

apartment

N

north

BLDG

building

NE

northeast

FL

floor

NW

northwest

STE

suite

S

south

UNIT

unit

SE

Southeast

RM

room

SW

southwest

DEPT

department

E

east

 

 

W

west


Punctuation marks should be avoided, except when punctuation is necessary to convey the meaning. Punctuation normally is limited to periods when the period carries meaning (e.g., 39.2 RD), slashes for fractional addresses (e.g., 101 ½ MAIN ST), and hyphens when the hyphen carries meaning (e.g., 289-01 MONTGOMERY AVE). Use of the pound sign (#) to designate address units should be avoided whenever possible. The preferred notation is as follows: 102 MAIN ST APT 101. If a pound sign is used, there must be a space between the pound sign and the secondary number (e.g., 425 FLOWER BLVD # 72).
ADDR CURRENT--POSTAL CODE
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
18309CoC2183 - 2191
Alternate Name:Postal Code--Current (CoC)
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Postal code for the address of the patient’s current usual residence. If the patient has multiple tumors, the postal codes should be the same. For U.S. residents, use either the 5-digit or the extended 9-digit ZIP code. Blanks follow the 5-digit code. For Canadian residents, use the 6-character alphanumeric postal code. Blanks follow the 6-character code. When available, enter postal code for other countries.
Rationale
“Current address” can be used to measure the regional “cancer burden” (cost, medical care needs), especially in major retirement regions. Sometimes central registries carry out follow-up by contacting the patients by a letter or telephone calls to ascertain their vital status. The most current reported address and telephone number are needed. This information also is useful for conducting interview studies.
Codes (in addition to U.S., Canadian, and Foreign postal codes)
999999Resident of Canada and postal code unknown
888888888Resident of country other than the United States (including its possessions, etc.) or Canada, and postal code unknown
999999999Resident of the United States (including its possessions, etc.) and postal code unknown
ADDR CURRENT--STATE
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
18202CoC2181 - 2182
Alternate Name:State--Current (CoC)
XML NAACCR ID:
XML PARENT ELEMENT:
Description
USPS abbreviation for the state, territory, commonwealth, U.S. possession, or CanadaPost abbreviation for the Canadian province/territory of the patient’s current usual residence. If the patient has multiple tumors, the current state of residence should be the same for all tumors. Effective with NAACCR Volume II, Version 13 a new data item, Addr Current--Country [1832] was added to the standard transmission record layout. The UDS Committee expects the new items to supplement the use of Addr Current--State [80].
Rationale
"Current address" can be used to measure the regional "cancer burden" (cost, medical care needs), especially in major retirement regions. Sometimes central registries carry out follow-up by contacting the patients via letter or telephone calls to ascertain vital status. The most current reported address and telephone number are needed. This information also is useful for conducting interview studies.
Codes (in addition to the U.S. and Canadian postal service abbreviations)
CDResident of Canada, NOS (province/territory unknown)
USResident of United States, NOS (state/commonwealth/territory/possession unknown)
XXResident of country other than the United States (including its territories, commonwealths, or possessions) or Canada, and country is known
YYResident of country other than the United States (including its territories, commonwealths, or possessions) or Canada, and country is unknown
ZZResidence unknown
ADDR CURRENT--SUPPLEMENTL
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
235560CoC2003103808 - 3867
Alternate Name:Patient Address (Number and Street) Current--Supplemental (CoC)
XML NAACCR ID:
XML PARENT ELEMENT:
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.
AGE AT DIAGNOSIS
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
2303SEER/CoC193 - 195
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Age of the patient at diagnosis in complete years. Different tumors for the same patient may have different values.
Codes
000Less than 1 year old; diagnosed in utero
0011 year old, but less than 2 years
0022 years old
...
101101 years old
...
120120 years old
999Unknown age
AMBIGUOUS TERMINOLOGY DX
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
4421SEER200611566 - 566
Alternate Name:Ambiguous Terminology
Ambiguous Terminology as Basis for Diagnosis
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Identifies all cases, including death certificate only and autopsy only, for which an ambiguous term is the most definitive word or phrase used to establish a cancer diagnosis (i.e., to determine whether or not the case is reportable). Ambiguous terminology may originate from any source document, such as pathology report, radiology report, or from a clinical report. This data item is used only when ambiguous terminology is used to establish diagnosis. It is not used when ambiguous terminology is used to clarify a primary site, specific histology, histologic group, or stage of disease.
Rationale
Cases with a reportable cancer diagnosis that has been established based only on reports that contain ambiguous terminology to describe final diagnostic findings cannot currently be identified. Multiple surveys have identified a lack of consensus in the interpretation and use of ambiguous terms across physician specialties. These cases may or may not have an actual cancer diagnosis based on clinician, radiologist, and pathologist review. Furthermore, the historical interpretation and use of ambiguous terms by cancer registrars and registries has not been consistent or compatible with physician use of these terms.

This data item will identify specific primary sites where the ambiguous terminology is commonly used to describe or establish a cancer diagnosis. Data collected will be used as the basis for modifications to case inclusion and reportable rules following complete analysis and impact assessment. This data item will allow cases to be identified within an analysis file and be excluded from patient contact studies.
Codes (refer to http://seer.cancer.gov/tools/mphrules/index.html for additional instructions.)
0Conclusive term
1Ambiguous term only
2Ambiguous term followed by conclusive term
9Unknown term
Refer to Table 2 in Chapter III for a list of ambiguous terms.
ARCHIVE FIN
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
310010CoC200310721 - 730
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
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.
AUTOPSY
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
19301NAACCR2274 - 2274
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Code indicating whether or not an autopsy was performed.
Codes
0Not applicable; patient alive
1Autopsy performed
2No autopsy performed
9Patient expired, unknown if autopsy performed
This data item is no longer supported by CoC (As of January 1, 2003).
BEHAVIOR (73-91) ICD-O-1
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
19721SEER1917 - 1917
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Area for retaining behavior portion (1 digit) of the ICD-O-1 or field trial morphology codes entered before a conversion to ICD-O-2. See grouped data item Morph (73-91) ICD-O-1 [1970] in Appendix E. The item name includes years 73-91. However, some states may have used the codes for cases before 1973. It is a subfield of the morphology code.
Codes
For tumors diagnosed before 1992, contains the ICD-O-1 or field trial 1-digit behavior code as originally coded, if available. Blank for tumors coded directly into a later version of ICD-O.
BEHAVIOR (92-00) ICD-O-2
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
4301SEER/CoC549 - 549
Alternate Name:ICD-O-2 Behaviour (CCCR)
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Code for the behavior of the tumor being reported using ICD-O-2. NAACCR adopted ICD-O-2 as the standard coding system for tumors diagnosed from January 1, 1992, through December 31, 2000. In addition, NAACCR recommended that cases diagnosed prior to 1992 be converted to ICD-O-2. See Behavior (73-91) ICD-O-1 [1972], for ICD-O-1 and field trial codes.
Clarification of Required Status This data item was required by all standard-setting organizations for tumors diagnosed from January 1, 1992, through December 31, 2000, and recommended for tumors diagnosed before 1992.

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

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

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

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

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

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

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

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

BIRTHPLACE
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
2503SEER/CoC206 - 208
Alternate Name:Place of Birth (SEER/CoC)
XML NAACCR ID:
XML PARENT ELEMENT:
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.
Codes
See Appendix B  for numeric and alphabetic lists of places and codes (also see Appendix B of the SEER Program Code Manual at seer.cancer.gov/tools/codingmanuals/index.html).
BIRTHPLACE--COUNTRY
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
2543NAACCR201313444 - 446
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Code for the country in which the patient was born. If the patient has multiple tumors, all records should contain the same code. This data item became part of the NAACCR transmission record effective with Volume II, Version 13 in order to include country and state for each geographic item and to use interoperable codes. It supplements the item BIRTHPLACE--STATE [252]. These two data items are intended to replace the use of BIRTHPLACE [250].
Rationale
Place of Birth is helpful for patient matching and can be used when reviewing race and ethnicity. It is an important item in algorithms for imputing race and ethnicity. In addition, adding birthplace data to race and ethnicity allows for a more specific definition of the population being reported. Careful descriptions of ancestry, birthplace, and immigration history of populations studied are needed to make the basis for classification into ethnic groups clear. Birthplace has been associated with variation in genetic, socioeconomic, cultural, and nutritional characteristics that affect patterns of disease. A better understanding of the differences within racial and ethnic categories also can help states develop effective, culturally-sensitive public health prevention programs to decrease the prevalence of high-risk behaviors and increase the use of preventive services.
Codes
Custom codes for historic use only
ZZNNorth America NOS
ZZCCentral American NOS
ZZSSouth America NOS
ZZPPacific NOS
ZZEEurope NOS
ZZFAfrica NOS
ZZAAsia NOS
ZZXNon-US NOS
ZZUUnknown
Custom codes for historic use only
XNINorth American Islands
XCBOther Caribbean Islands
XENEngland, Channel Islands, Isle of Man
XSCScandinavia
XGRGermanic Countries
XSLSlavic Countries
CSKCzechoslovakia (former)
YUGYugoslavia (former)
XUMUkraine and Moldova
XNFNorth Africa
XSDSudanese Countries
XWFWest Africa
XSFSouth Africa
XEFEast Africa
XIFAfrican Islands
XETEthiopia and Eritrea
XAPArabian Peninsula
XISIsrael and Palestine
XCRCaucasian Republics of former USSR
XOROther Asian Republics of former USSR
XSESoutheast Asia
XMS Malaysia, Singapore, Brunei
XCHChina, NOS
XMLMelanesian Islands
XMCMicronesian Islands
XPLPolynesian Islands
See Appendix B for numeric and alphabetic lists of places and codes (also see Appendix B of the SEER Program Code Manual at seer.cancer.gov/tools/codingmanuals/index.html).
BIRTHPLACE--STATE
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
2522NAACCR201313442 - 443
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
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).
CANCER STATUS
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
17701CoC2127 - 2127
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Records the presence or absence of clinical evidence of the patient's malignant or non-malignant tumor as of the Date of Last Contact [1750]. If the patient has multiple primaries, the values may be different for each primary.
Rationale
This item can be used to compute disease-free survival. By maintaining this data item, central registries can assist hospital registries by sharing this information with other hospital registries that serve the same patients, if the state’s privacy laws so permit.
Codes
1No evidence of this tumor
2Evidence of this tumor
9Unknown, indeterminate whether this tumor is present, not stated in patient record
CASEFINDING SOURCE
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
5012NAACCR200611564 - 565
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
This variable codes the earliest source of identifying information. For cases identified by a source other than reporting facilities (such as through death clearance or as a result of an audit), this variable codes the type of source through which the tumor was first identified. This data item cannot be used by itself as a data quality indicator. The timing of the casefinding processes (e.g., death linkage) varies from registry to registry, and the coded value of this variable is a function of that timing.
Rationale
This data item will help reporting facilities as well as regional and central registries in prioritizing their casefinding activities. It will identify reportable tumors that were first found through death clearance or sources other than traditional reporting facilities. It provides more detail than "Type of Reporting Source."

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

If a death certificate, independent pathology laboratory report, consultation-only report from a hospital, or other report was used to identify a case that was then abstracted from a different source, enter the code for the source that first identified the case, not the source from which it was subsequently abstracted. If a regional or central registry identifies a case and asks a reporting facility to abstract it, enter the code that corresponds to the initial source, not the code that corresponds to the eventual reporting facility.
Codes 
10Reporting Hospital, NOS
20Pathology Department Review (surgical pathology reports, autopsies, or cytology reports)
21Daily Discharge Review (daily screening of charts of discharged patients in the medical records department)
22Disease Index Review (review of disease index in the medical records department)
23Radiation Therapy Department/Center
24Laboratory Reports (other than pathology reports, code 20)
25Outpatient Chemotherapy
26Diagnostic Imaging/Radiology (other than radiation therapy, codes 23; includes nuclear medicine)
27Tumor Board
28Hospital Rehabilitation Service or Clinic
29Other Hospital Source (including clinic, NOS or outpatient department, NOS)
30Physician-Initiated Case
40Consultation-only or Pathology-only Report (not abstracted by reporting hospital)
50Independent (non-hospital) Pathology-Laboratory Report
60Nursing Home-Initiated Case
70Coroner's Office Records Review
75Managed Care Organization (MCO) or Insurance Records
80Death Certificate (case identified through death clearance)
85Out-of-State Case Sharing
90Other Non-Reporting Hospital Source
95Quality Control Review (case initially identified through quality control activities such as casefinding audit of a regional or central registry)
99Unknown
CAUSE OF DEATH
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
19104SEER2269 - 2272
Alternate Name:Underlying Cause of Death (SEER)
Underlying Cause of Death (ICD Code) (pre-96 CoC)
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Official cause of death as coded from the death certificate in valid ICD-7, ICD-8, ICD-9, and ICD-10 codes.
Rationale
Cause of death is used for calculation of adjusted survival rates by the life table method. The adjustment corrects for deaths other than from the diagnosed cancer.
Note: This data item is no longer supported by CoC (as of January 1, 2003).
Special codes in addition to ICD-7, ICD-8, ICD-9, and ICD-10 (refer to SEER Program Code Manual for additional instructions.)
0000Patient alive at last contact
7777State death certificate not available
7797State death certificate available but underlying cause of death is not coded
CENSUS BLOCK GROUP 2000
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
3621Census174 - 174
Alternate Name:Census Tract Block Group
XML NAACCR ID:
XML PARENT ELEMENT:
Description
This field is provided for coding the block group of patient’s residence at time of diagnosis, as defined by the 2000 Census.
Rationale
A block group is a subdivision of a census tract designed to have an average of 1500 people, versus a census tract’s average of 4500 people. All land area in the United States is described by a census block group in the 2000 Census. The Census Bureau publishes detailed population and socioeconomic data at this level.

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

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

Clarification of NPCR Required Status

 

Census-1990 data items:

Census-2000 data items:

Census Tract  1970/80/90  [110]

Census Tract  2000  [130]

Census Tr Cert 1970/80/90  [364]

Census Tr Certainty 2000  [365]

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

 


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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

 

Census-1990 data items:

Census-2000 data items:

Census Tract  1970/80/90  [110]

Census Tract  2000  [130]

Census Tr Cert 1970/80/90  [364]

Census Tr Certainty 2000  [365]

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

 


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

 

Census-1990 data items:

Census-2000 data items:

Census Tract  1970/80/90  [110]

Census Tract  2000  [130]

Census Tr Cert 1970/80/90  [364]

Census Tr Certainty 2000  [365]

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

 


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

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

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

 

 

Census-1990 data items: Census-2000 data items: Census-2010 data items:
Census Tract  1970/80/90  [110] Census Tract  2000  [130] Census Tract  2010  [135]
Census Tr Cert 1970/80/90  [364] Census Tr Certainty 2000  [365] Census Tr Certainty 2010  [367]
Census Tract  Cod Sys--1970/80/90 [120]

 

 


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

The ACS publishes tract-level poverty data annually, on a rolling five-year window, with a two-year lag (e.g., poverty data for 2006-2010 will be available in 2012). Cases for a given diagnosis year are initially coded using the most recent file available when the cancer data are first released, and the item is subsequently coded using the ACS file centered on the year of diagnosis. For example, cases diagnosed in 2012 will initially be coded using the 2008-2012 ACS file, and two years later using the 2010-2014 ACS file. An exception to this rule is that cases diagnosed in 2005 and 2006 will be coded using the 2005-2009 ACS file, because this was the first such file released. Codes may be automatically assigned by running the Poverty and Census Tract Linkage Program available through the Data Analysis Tools section of the NAACCR website.
Rationale
Many cancers are associated with socioeconomic status and it is useful to include a measure of this in analyses. A detailed rationale for this data item was published in Journal of Registry Management 2010; 37(4): 148-151.
Codes
10% - <5% poverty
25% - <10% poverty
310% - <20% poverty
4 20% - 100% poverty
9Unknown or not applicable
CENSUS TRACT 1970/80/90
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
1106SEER159 - 164
Alternate Name:Census Tract/Block Numbering Area (BNA) (SEER)
Census Tract
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Code for the census tract or BNA of the patient's residence at the time of diagnosis. SEER used this field for tumors reported before 1998. If the patient has more than one tumor, the codes may be different for each tumor.

Codes are those used by the U.S. Census Bureau. Census Bureau codes for BNA also are entered in this field.

Both census tracts and BNAs have a 4-digit basic number and also may have a 2-digit suffix. Census tract numbers range from 0001.00 to 9499.99. BNA numbers range from 9501.00 to 9989.99. See the Census Bureau’s “Area Classifications”35 for further details.
Rationale
Allows central registries to calculate incidence rates for geographical areas having population estimates. The Census Bureau provides population data for census tracts. Those rates can be used for general surveillance or special geographical and socioeconomic analysis.
Codes
Census Tract Codes000100-949999
BNA Codes950100-998999
000000Area not census-tracted
999999Area census-tracted, but census tract is not available
BlankCensus Tract 1970/80/90 not coded
Clarification of NPCR Required Status
Information on census tract, census tract certainty, and census tract coding system is required. Tumors diagnosed in 2003 or later, must be coded to the 2000 census definitions and recorded in Census Tract 2000 [130] and Census Tr Certainty 2000 [365]. Tumors diagnosed in 2002, or before must be coded to the 2000 census tract definitions OR to 1990 definitions OR to both the 2000 and 1990 census definitions. Census tract, census tract certainty and census tract coding system should be recorded in the year appropriate data item fields. For tumors diagnosed between January 1, 1998, and December 31, 2002, (inclusive) use of the 2000 census tract definitions is recommended.
CENSUS TRACT 2000
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
1306NAACCR168 - 173
Alternate Name:Census Tract--Alternate (pre-2003)
XML NAACCR ID:
XML PARENT ELEMENT:
Description
This field is provided for coding census tract of patient’s residence at time of diagnosis. See Census Tract 1970/80/90 [110]. Codes are those used by the U.S. Census Bureau for the Year 2000 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. See the Census Bureau’s “Area Classifications” at the following website: http://www.census.gov/prod/cen2000/doc/sf1.pdf for further details.
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 2000 Census tracts to tumors diagnosed in previous years, without losing the codes in data item 110.

The Census Bureau provides population data for census tracts. Those rates can be used for general surveillance or special geographical and socioeconomic analysis.

Because census tracts for particular cases can change between censuses, the central registry may wish to assign an alternate census tract code to its cases. For example, a registry may code its 2005 cases using both the 2000 and 2010 census tract boundaries. The central registry can use this information for different comparisons.
Codes
Census Tract Codes000100-999998
000000Area not census tracted
999999Area census-tracted, but census tract is not available
BlankCensus Tract 2000 not coded
Clarification of NPCR Required Status
Information on census tract, census tract certainty, and census tract coding system is required. Tumors diagnosed in 2003 or later, must be coded to the 2000 census definitions and recorded in Census Tract 2000 [130] and Census Tr Certainty 2000 [365]. Tumors diagnosed in 2002, or before must be coded to the 2000 census tract definitions OR to 1990 definitions OR to both the 2000 and 1990 census tract definitions. Census tract, census tract certainty and census tract coding system should be recorded in the year appropriate data item fields. For tumors diagnosed between January 1, 1998, and December 31, 2002, (inclusive) use of the 2000 cases tract definitions is recommended.
CENSUS TRACT 2010
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
1356NAACCR201112.1428 - 433
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
This field is provided for coding census tract of patient's residence at time of diagnosis. See Census Tract 1970/80/90 [110]; Census Tract 2000 [130]. Codes are those used by the U.S. Census Bureau for the Year 2010 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.
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 2010 Census tracts to tumors diagnosed in previous years, without losing the codes in data items [110] and [130].

The Census Bureau provides population data for census tracts. Those rates can be used for general surveillance or special geographical and socioeconomic analysis.

Because census tracts for particular cases can change between censuses, the central registry may wish to assign an alternate census tract code to its cases. For example, a registry may code its 2005 cases using both the 2000 and 2010 census tract boundaries. The central registry can use this information for different comparisons.
Codes
Census Tract Code000100-999998
000000Area not census tracted
999999Area census tracted, but census tract is not available
BlankCensus Tract 2010 not coded
Clarification of NPCR Required Status
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.
CLASS OF CASE
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
6102CoC1990pre V4776 - 777
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
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 FORDS for additional instructions)
INITIAL DIAGNOSIS AT REPORTING FACILITY
00*Initial diagnosis at the reporting facility AND all treatment or a decision not to treat was done ELSEWHERE
10*Initial diagnosis at the reporting facility or in a staff physician's office AND PART OR ALL of first course treatment or a decision not to treat was at the reporting facility, NOS
11Initial diagnosis in staff physician's office AND PART of first course treatment was done at the reporting facility
12Initial diagnosis in staff physician's office AND ALL first course treatment or a decision not to treat was done at the reporting facility
13*Initial diagnosis at the reporting facility AND PART of first course treatment was done at the reporting facility
14*Initial diagnosis at the reporting facility AND ALL first course treatment or a decision not to treat was done at the reporting facility
INITIAL DIAGNOSIS ELSEWHERE, FACILITY INVOLVED IN FIRST COURSE TREATMENT
20*Initial diagnosis elsewhere AND PART OR ALL of first course treatment was done at the reporting facility, NOS
21*Initial diagnosis elsewhere AND PART of treatment was done at the reporting facility
22*Initial diagnosis elsewhere AND ALL first course treatment was done at the reporting facility
Classes of Case not required by CoC to be abstracted (May be required by Cancer Committee, state or regional registry, or other entity)
PATIENT APPEARS IN PERSON AT REPORTING FACILITY; BOTH INITIAL DIAGNOSIS AND TREATMENT ELSEWHERE
30*Initial diagnosis and all first course treatment elsewhere AND reporting facility participated in DIAGNOSTIC WORKUP (for example, consult only, staging workup after initial diagnosis elsewhere)
31*Initial diagnosis and all first course treatment elsewhere AND reporting facility provided IN-TRANSIT care
32*Diagnosis AND all first course treatment provided elsewhere AND patient presents at reporting facility with disease RECURRENCE OR PERSISTENCE
33*Diagnosis AND all first course treatment provided elsewhere AND patient presents at reporting facility with disease HISTORY ONLY
34Type of case not required by CoC to be accessioned (for example, a benign colon tumor) AND initial diagnosis AND part or all of first course treatment by reporting facility
35Case diagnosed before program's Reference Date AND initial diagnosis AND PART OR ALL of first course treatment by reporting facility
36Type of case not required by CoC to be accessioned (for example, a benign colon tumor) AND initial diagnosis elsewhere AND part of all of first course treatment by reporting facility
37Case diagnosed before program's Reference Date AND initial diagnosis elsewhere AND all or part of first course treatment by reporting facility
38*Initial diagnosis established by AUTOPSY at the reporting facility, cancer not suspected prior to death
PATIENT DOES NOT APPEAR IN PERSON AT REPORTING FACILITY
40Diagnosis AND all first course treatment given at the same staff physician's office
41Diagnosis and all first course treatment given in two or more different staff physician offices
42Non-staff physician or non-CoC accredited clinic or other facility, not part of reporting facility, accessioned by reporting facility for diagnosis and/or treatment by that entity (for example, hospital abstracts cases from an independent radiation facility)
43*PATHOLOGY or other lab specimens ONLY
49*DEATH CERTIFICATE ONLY
UNKNOWN RELATIONSHIP TO REPORTING FACILITY
99*Nonanalytic case of unknown relationship to facility (not for use by CoC accredited cancer programs for analytic cases.); UNKNOWN
Note: This expanded list of coded values is effective with Version 12.

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

By using Class of Case codes in this manner for non-hospital sources, the central cancer registry is able to retain information reflecting the facility's role in managing the cancer consistent with the way it is reported from hospitals. Using Class of Case in conjunction with Type of Reporting Source [500] which identifies the source documents used to abstract the cancer being reported, the central cancer registry has two distinct types of information to use in making consolidation decisions
COC CODING SYS--CURRENT
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
21402CoC1932 - 1933
Alternate Name:Commission on Cancer Coding System-Current (CoC)
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Code the ACoS CoC coding system currently used in the record. CoC codes may be converted from an earlier version.
Codes
00No CoC coding system used
01Pre-1988 (Cancer Program Manual Supplement)
021988 Data Acquisition Manual
031989 Data Acquisition Manual Revisions
041990 Data Acquisition Manual Revisions
051994 Data Acquisition Manual (Interim/Revised)
06ROADS (effective with cases diagnosed 1996-1997)
07ROADS and 1998 Supplement (effective with cases diagnosed 1998-2002)
08FORDS (effective with cases diagnosed 2003 and forward)
99Unknown coding system
COC CODING SYS--ORIGINAL
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
21502CoC1934 - 1935
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Code for the ACoS CoC coding system originally used to code the record.
Codes
00No CoC coding system used
01Pre-1988 (Cancer Program Manual Supplement)
021988 Data Acquisition Manual
031989 Data Acquisition Manual Revisions
041990 Data Acquisition Manual Revisions
051994 Data Acquisition Manual (Interim/Revised)
06ROADS (effective with cases diagnosed 1996-1997)
07ROADS and 1998 Supplement (effective with cases diagnosed 1998-2002)
08FORDS (effective with cases diagnosed 2003 and forward)
99Original CoC coding system is not known
CODING SYSTEM FOR EOD
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
8701SEER19955937 - 937
Alternate Name:Coding System for Extent of Disease (SEER)
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Indicates the type of SEER EOD code applied to the tumor. Should be used whenever EOD coding is applied.
Rationale
Used in data editing and analysis.
Codes
02-Digit Nonspecific Extent of Disease (1973-82)
12-Digit Site-Specific Extent of Disease (1973-82)
213-Digit (expanded) Site-Specific Extent of Disease (1973-1982)
34-Digit Extent of Disease (1983-87)
410-Digit Extent of Disease, 1988 (1988-2003)
BlankCases diagnosed 2004+; or the item is not collected
COMORBID/COMPLICATION 1
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
31105CoC2003101186 - 1190
Alternate Name:Comorbidities and Complications #1
XML NAACCR ID:
XML PARENT ELEMENT:
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 FORDS for additional instructions.)
ICD-9-CM Codes 00100-13980, 24000-99990, E8700-E8799, E9300-E9499, V0720-V0739, V1000-V1590, V2220- V2310, V2540, V4400-V4589, and V5041-V5049.
00000No secondary diagnoses documented
Note: For comorbid conditions (ICD-9-CM codes 00100-13980 and 24000-99990), there is an assumed decimal point between the third and fourth characters. For complications (ICD-9-CM codes E8700-E8799 and E9300-E9499), there is an assumed decimal point between the fourth and fifth characters. For conditions influencing health status and contact with health services (ICD-9-CM codes V0720-V0739, V1000-V1590, V2220- V2310, V2540, V4400-V4589, and V5041-V5049), there is an assumed decimal point between the third and fourth characters.
COMORBID/COMPLICATION 10Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
31645CoC2006111231 - 1235
Alternate Name:Comorbidities and Complications #10
XML NAACCR ID:
XML PARENT ELEMENT:
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 FORDS for additional instructions.)
ICD-9-CM Codes 00100-13980, 24000-99990, E8700-E8799, E9300-E9499, V0720-V0739, V1000-V1590, V2220- V2310, V2540, V4400-V4589, and V5041-V5049.
Leave blank if no further secondary diagnosis.
Note: For comorbid conditions (ICD-9-CM codes 00100-13980 and 24000-99990), there is an assumed decimal point between the third and fourth characters. For complications (ICD-9-CM codes E8700-E8799 and E9300-E9499), there is an assumed decimal point between the fourth and fifth characters. For conditions influencing health status and contact with health services (ICD-9-CM codes V0720-V0739, V1000-V1590, V2220-V2310, V2540, V4400-V4589, and V5041-V5049), there is an assumed decimal point between the third and fourth characters.
COMORBID/COMPLICATION 2
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
31205CoC2003101191 - 1195
Alternate Name:Comorbidities and Complications #2
XML NAACCR ID:
XML PARENT ELEMENT:
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 FORDS for additional instructions.)
ICD-9-CM Codes 00100-13980, 24000-99990, E8700-E8799, E9300-E9499, V0720-V0739, V1000-V1590, V2220- V2310, V2540, V4400-V4589, and V5041-V5049.
 
Leave blank if no further secondary diagnosis.
Note: For comorbid conditions (ICD-9-CM codes 00100-13980 and 24000-99990), there is an assumed decimal point between the third and fourth characters. For complications (ICD-9-CM codes E8700-E8799 and E9300-E9499), there is an assumed decimal point between the fourth and fifth characters. For conditions influencing health status and contact with health services (ICD-9-CM codes V0720-V0739, V1000-V1590, V2220-V2310, V2540, V4400-V4589, and V5041-V5049), there is an assumed decimal point between the third and fourth characters.
COMORBID/COMPLICATION 3
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
31305CoC2003101196 - 1200
Alternate Name:Comorbidities and Complications #3
XML NAACCR ID:
XML PARENT ELEMENT:
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 FORDS for additional instructions.)
ICD-9-CM Codes 00100-13980, 24000-99990, E8700-E8799, E9300-E9499, V0720-V0739, V1000-V1590, V2220- V2310, V2540, V4400-V4589, and V5041-V5049.

Leave blank if no further secondary diagnoses.
Note: For comorbid conditions (ICD-9-CM codes 00100-13980 and 24000-99990), there is an assumed decimal point between the third and fourth characters. For complications (ICD-9-CM codes E8700-E8799 and E9300-E9499), there is an assumed decimal point between the fourth and fifth characters. For conditions influencing health status and contact with health services (ICD-9-CM codes V0720-V0739, V1000-V1590, V2220-V2310, V2540, V4400-V4589, and V5041-V5049), there is an assumed decimal point between the third and fourth characters.
COMORBID/COMPLICATION 4
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
31405CoC2003101201 - 1205
Alternate Name:Comorbidities and Complications #4
XML NAACCR ID:
XML PARENT ELEMENT:
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 FORDS for additional instructions.)
ICD-9-CM Codes 00100-13980, 24000-99990, E8700-E8799, E9300-E9499, V0720-V0739, V1000-V1590, V2220- V2310, V2540, V4400-V4589, and V5041-V5049.

Leave blank if no further secondary diagnoses.
Note: For comorbid conditions (ICD-9-CM codes 00100-13980 and 24000-99990), there is an assumed decimal point between the third and fourth characters. For complications (ICD-9-CM codes E8700-E8799 and E9300-E9499), there is an assumed decimal point between the fourth and fifth characters. For conditions influencing health status and contact with health services (ICD-9-CM codes V0720-V0739, V1000-V1590, V2220-V2310, V2540, V4400-V4589, and V5041-V5049), there is an assumed decimal point between the third and fourth characters.
COMORBID/COMPLICATION 5
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
31505CoC2003101206 - 1210
Alternate Name:Comorbidities and Complications #5
XML NAACCR ID:
XML PARENT ELEMENT:
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 FORDS for additional instructions.)
ICD-9-CM Codes 00100-13980, 24000-99990, E8700-E8799, E9300-E9499, V0720-V0739, V1000-V1590, V2220- V2310, V2540, V4400-V4589, and V5041-V5049.

Leave blank if no further secondary diagnoses.
Note: For comorbid conditions (ICD-9-CM codes 00100-13980 and 24000-99990), there is an assumed decimal point between the third and fourth characters. For complications (ICD-9-CM codes E8700-E8799 and E9300-E9499), there is an assumed decimal point between the fourth and fifth characters. For conditions influencing health status and contact with health services (ICD-9-CM codes V0720-V0739, V1000-V1590, V2220-V2310, V2540, V4400-V4589, and V5041-V5049), there is an assumed decimal point between the third and fourth characters.
COMORBID/COMPLICATION 6
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
31605CoC2003101211 - 1215
Alternate Name:Comorbidities and Complications #6
XML NAACCR ID:
XML PARENT ELEMENT:
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 FORDS for additional instructions.)
ICD-9-CM Codes 00100-13980, 24000-99990, E8700-E8799, E9300-E9499, V0720-V0739, V1000-V1590, V2220- V2310, V2540, V4400-V4589, and V5041-V5049.

Leave blank if no further secondary diagnoses.
Note: For comorbid conditions (ICD-9-CM codes 00100-13980 and 24000-99990), there is an assumed decimal point between the third and fourth characters. For complications (ICD-9-CM codes E8700-E8799 and E9300-E9499), there is an assumed decimal point between the fourth and fifth characters. For conditions influencing health status and contact with health services (ICD-9-CM codes V0720-V0739, V1000-V1590, V2220-V2310, V2540, V4400-V4589, and V5041-V5049), there is an assumed decimal point between the third and fourth characters.
COMORBID/COMPLICATION 7
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
31615CoC2006111216 - 1220
Alternate Name:Comorbidities and Complications #7
XML NAACCR ID:
XML PARENT ELEMENT:
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 FORDS for additional instructions.)
ICD-9-CM Codes 00100-13980, 24000-99990, E8700-E8799, E9300-E9499, V0720-V0739, V1000-V1590, V2220- V2310, V2540, V4400-V4589, and V5041-V5049.

Leave blank if no further secondary diagnosis.
Note: For comorbid conditions (ICD-9-CM codes 00100-13980 and 24000-99990), there is an assumed decimal point between the third and fourth characters. For complications (ICD-9-CM codes E8700-E8799 and E9300-E9499), there is an assumed decimal point between the fourth and fifth characters. For conditions influencing health status and contact with health services (ICD-9-CM codes V0720-V0739, V1000-V1590, V2220-V2310, V2540, V4400-V4589, and V5041-V5049), there is an assumed decimal point between the third and fourth characters.
COMORBID/COMPLICATION 8
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
31625CoC2006111221 - 1225
Alternate Name:Comorbidities and Complications #8
XML NAACCR ID:
XML PARENT ELEMENT:
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 FORDS for additional instructions.)
ICD-9-CM Codes 00100-13980, 24000-99990, E8700-E8799, E9300-E9499, V0720-V0739, V1000-V1590, V2220- V2310, V2540, V4400-V4589, and V5041-V5049.

Leave blank if no further secondary diagnosis.
Note: For comorbid conditions (ICD-9-CM codes 00100-13980 and 24000-99990), there is an assumed decimal point between the third and fourth characters. For complications (ICD-9-CM codes E8700-E8799 and E9300-E9499), there is an assumed decimal point between the fourth and fifth characters. For conditions influencing health status and contact with health services (ICD-9-CM codes V0720-V0739, V1000-V1590, V2220-V2310, V2540, V4400-V4589, and V5041-V5049), there is an assumed decimal point between the third and fourth characters.
COMORBID/COMPLICATION 9
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
31635CoC2006111226 - 1230
Alternate Name:Comorbidities and Complications #9
XML NAACCR ID:
XML PARENT ELEMENT:
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 FORDS for additional instructions.)
ICD-9-CM Codes 00100-13980, 24000-99990, E8700-E8799, E9300-E9499, V0720-V0739, V1000-V1590, V2220- V2310, V2540, V4400-V4589, and V5041-V5049.
Leave blank if no further secondary diagnosis.
Note: For comorbid conditions (ICD-9-CM codes 00100-13980 and 24000-99990), there is an assumed decimal point between the third and fourth characters. For complications (ICD-9-CM codes E8700-E8799 and E9300-E9499), there is an assumed decimal point between the fourth and fifth characters. For conditions influencing health status and contact with health services (ICD-9-CM codes V0720-V0739, V1000-V1590, V2220-V2310, V2540, V4400-V4589, and V5041-V5049), there is an assumed decimal point between the third and fourth characters.
COMPUTED ETHNICITY
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
2001SEER19954190 - 190
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Code identifying those cases for which ethnicity was determined by matching Name--Last [2230] and Name--Maiden [2390] to a computer list of Spanish/Hispanic names or by a software algorithm. This field was adopted for use for tumors diagnosed 1994 forward. See also Computed Ethnicity Source [210].
Rationale
One method of identifying persons of Hispanic origin is to apply a standard computer list or algorithm to items 2230 and 2390, the patient’s surname and/or maiden name. This has advantages across large populations of being reproducible and facilitating comparisons between areas using identical methods. It may sometimes be possible to identify population denominators in which the same method was used to identify Hispanics. Generally, only central registries will have this capability.

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

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

Note:
NAACCR recognizes that available definitions and abstracting instructions for the data items Name--Last and Name--Maiden may be inadequate for describing names used in some cultures, including Hispanic cultures. Explicit instructions have not been provided for entering compound names, with or without hyphens or “De.” Order of names, use of maternal and paternal names, and use of hyphens can vary across cultures. It is likely, too, that abstracting and coding practice for these items varies across registries. Limitations inherent in these definitions should be kept in mind in any use of the data.
COMPUTED ETHNICITY SOURCE
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
2101SEER191 - 191
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Code identifying the method used to determine ethnicity as recorded in Computed Ethnicity [200].
Codes
0No match was run, for 1994 and later tumors
1Census Bureau list of Spanish surnames, NOS
21980 Census Bureau list of Spanish surnames
31990 Census Bureau list of Spanish surnames
4GUESS Program
5Combination list including South Florida names
6Combination of Census and other locally generated list
7Combination of Census and GUESS, with or without other lists
8Other type of match
9Unknown type of match
Blank1993 and earlier tumors, no match was run
Note: For SEER, blanks are required for all cases diagnosed before 1994 and blanks are not allowed for any case diagnosed 1994 and after. Other registries may have computed this item for earlier years.
COUNTY AT DX
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
903FIPS/SEER156 - 158
Alternate Name:County (pre-96 SEER/CoC)
County at Diagnosis (CoC)
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Code for the county of the patient's residence at the time the tumor was diagnosed. 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." 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. 
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)
998Known town, city, state, or country of residence but county code not known AND a resident outside of the state of reporting institution (must meet all criteria)
999County unknown
COUNTY AT DX GEOCODE1990New
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
943NAACCR201616464 - 466
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
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 1990 Decennial Census. This code should be used for county and county-based (such as CHSDA) rates and analysis for all cases diagnosed prior to 2000.
Rationale
County of diagnosis is essential for investigating epidemiologic pattern at both the county and the census tract level. Census tracts are nested within counties and designated with a 6-digit number code. A given census tract code is commonly repeated within a state in different counties, making census tract numbers unique only when paired with the state and the county. Example from Massachusetts: Rural Franklin County contains a tract 040600 with 2010 population 4,612 people, and urban Suffolk County contains a tract 040600 with 2,444 people.

County borders occasionally change over time. For instance, part of Adams County in Colorado become a new county, Broomfield County, in 2001. Because the historic NAACCR county code, County at DX [90], is not associated with any particular date, census tract codes can be paired with the wrong county if these changes occur. Thus, county-level rates may be generated using temporally incorrect county populations. Further, this county code is derived (through geocoding) and, therefore, generally more accurate than those provided manually. Finally, some variables, like the Tract-Level Poverty Indicator (Census Tr Poverty Indictr [145]), requires census information closest to year of diagnosis and not the decade of diagnosis. Having separate geocoded county codes for each decennial census, as we do for census tract, enables registries to retain the original, reported county as needed but will ensure the correct pairing by county and tract occur.

Recording a county at diagnosis that reflects the relevant date (decade) and relies on geocoded data will improve the accuracy of county and census tract assignments and of links with geographic data (i.e., population, poverty category, urban/rural designation).
Codes
001-997County at diagnosis. Valid FIPS code
998Outside state/county code unknown. Known town, city, state, or country of residence but county code not known AND a resident outside of the state of reporting institution (must meet all criteria)
999County unknown. The county of the patient is unknown, or the patient is not a United States resident. County is not documented in the patient's medical record.
Note: For U.S. residents, historically, standard codes are those of the FIPS publication “Counties and Equivalent Entities of the United States, Its Possessions, and Associated Areas.” These FIPS codes (FIPS 6-4) have been replaced by INCITS standard codes, however, there is no impact on this variable as the codes align with the system the Census used for each decennial census and will automatically be accounted for during geocoding.
COUNTY AT DX GEOCODE2000New
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
953NAACCR201616467 - 469
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Code for the county of the patient's residence at the time the tumor was diagnosed is a derived (geocoded) variable based on Census Boundary files from 2000 Decennial Census. This code should be used for county and county-based (such as CHSDA) rates and analysis for all cases diagnosed in 2000-2009.
Rationale
County of diagnosis is essential for investigating epidemiologic pattern at both the county and the census tract level. Census tracts are nested within counties and designated with a 6-digit number code. A given census tract code is commonly repeated within a state in different counties, making census tract numbers unique only when paired with the state and the county. Example from Massachusetts: Rural Franklin County contains a tract 040600 with 2010 population 4,612 people, and urban Suffolk County contains a tract 040600 with 2,444 people.

County borders occasionally change over time. For instance, part of Adams County in Colorado become a new county, Broomfield County, in 2001. Because the historic NAACCR county code, County at DX [90], is not associated with any particular date, census tract codes can be paired with the wrong county if these changes occur. Thus, county-level rates may be generated using temporally incorrect county populations. Further, this county code is derived (through geocoding) and, therefore, generally more accurate than those provided manually. Finally, some variables, like the Tract-Level Poverty Indicator (Census Tr Poverty Indictr [145]), requires census information closest to year of diagnosis and not the decade of diagnosis. Having separate geocoded county codes for each decennial census, as we do for census tract, enables registries to retain the original, reported county as needed but will ensure the correct pairing by county and tract occur.

Recording a county at diagnosis that reflects the relevant date (decade) and relies on geocoded data will improve the accuracy of county and census tract assignments and of links with geographic data (i.e., population, poverty category, urban/rural designation).
Codes
001-997County at diagnosis. Valid FIPS code.
998Outside state/county code unknown. Known town, city, state, or country of residence but county code not known AND a resident outside of the state of reporting institution (must meet all criteria).
999County unknown. The county of the patient is unknown, or the patient is not a United States resident. County is not documented in the patient's medical record.
Note: For U.S. residents, historically, standard codes are those of the FIPS publication “Counties and Equivalent Entities of the United States, Its Possessions, and Associated Areas.” These FIPS codes (FIPS 6-4) have been replaced by INCITS standard codes, however, there is no impact on this variable as the codes align with the system the Census used for each decennial census and will automatically be accounted for during geocoding.
COUNTY AT DX GEOCODE2010New
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
963NAACCR201616470 - 472
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
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 2010 Decennial Census. This code should be used for county and county-based (such as CHSDA) rates and analysis for all cases diagnosed in 2010-2019.
Rationale
County of diagnosis is essential for investigating epidemiologic pattern at both the county and the census tract level. Census tracts are nested within counties and designated with a 6-digit number code. A given census tract code is commonly repeated within a state in different counties, making census tract numbers unique only when paired with the state and the county. Example from Massachusetts: Rural Franklin County contains a tract 040600 with 2010 population 4,612 people, and urban Suffolk County contains a tract 040600 with 2,444 people.

County borders occasionally change over time. For instance, part of Adams County in Colorado become a new county, Broomfield County, in 2001. Because the historic NAACCR county code, County at DX [90], is not associated with any particular date, census tract codes can be paired with the wrong county if these changes occur. Thus, county-level rates may be generated using temporally incorrect county populations. Further, this county code is derived (through geocoding) and, therefore, generally more accurate than those provided manually. Finally, some variables, like the Tract-Level Poverty Indicator (Census Tr Poverty Indictr [145]), requires census information closest to year of diagnosis and not the decade of diagnosis. Having separate geocoded county codes for each decennial census, as we do for census tract, enables registries to retain the original, reported county as needed but will ensure the correct pairing by county and tract occur.

Recording a county at diagnosis that reflects the relevant date (decade) and relies on geocoded data will improve the accuracy of county and census tract assignments and of links with geographic data (i.e., population, poverty category, urban/rural designation).
Codes
001-997County at diagnosis. Valid FIPS code.
998Outside state/county code unknown. Known town, city, state, or country of residence but county code not known AND a resident outside of the state of reporting institution (must meet all criteria).
999County unknown. The county of the patient is unknown, or the patient is not a United States resident. County is not documented in the patient's medical record.
Note: For U.S. residents, historically, standard codes are those of the FIPS publication “Counties and Equivalent Entities of the United States, Its Possessions, and Associated Areas.” These FIPS codes (FIPS 6-4) have been replaced by INCITS standard codes, however, there is no impact on this variable as the codes align with the system the Census used for each decennial census and will automatically be accounted for during geocoding.
COUNTY AT DX GEOCODE2020New
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
973NAACCR201616473 - 475
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Code for the county of the patient's residence at the time the tumor was diagnosed is a derived (geocoded) variable based on Census Boundary files from 2020 Decennial Census. This code should be used for county and county-based (such as CHSDA) rates and analysis for all cases diagnosed in 2020-2029.
Rationale
Census tracts are areas geographically nested within counties and designated with a 6-digit number code. This 6-digit code is commonly repeated within a state in different counties. Census tract numbers are only unique when paired with the state and the county. Therefore, a tract cannot be accurately identified without knowing the county. Example from Massachusetts: Rural Franklin County contains a tract 040600 with 2010 population 4,612 people. Urban Suffolk County contains a tract 040600 with 2,444 people. The county must be known in order to distinguish between the two tract codes. Because we historically used a single variable for County at DX [90], correct tract codes were frequently paired with the wrong county due to incorrect county assignment during abstracting or a change of county over time. Also, some variables, such as the Census Tract Poverty Indicator [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. For U.S. residents, this data item stores the county codes issued by the Federal Information Processing Standards (FIPS) publication Counties and Equivalent Entities of the United States, Its Possessions, and Associated Areas. The information in this publication is available in Appendix A.
  • It is recommended that geocoding be performed using the NAACCR geocoder.
  • It is recommended that all cases diagnosed through 2029 should have a geocoded County at DX Geocode2020.
  • At a minimum, all cases diagnosed through 2016-2029 should have a geocoded County at DX Geocode2020. Some cases, such as those diagnosed in 2019, must have both County at DX Geocode2010 [96] and County at DX Geocode2020 codes for proper assignment of the Census Tract Poverty Indicator [145].
  • Do not update this item if the patient’s county of residence 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.
  • 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.
  • For cases with a 9 or blank in Census Tr Certainty 2020 AND a valid FIPS code in County at DX [90], the valid FIPS code from Item [90] should be used.
  • 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 diagnosed through 2029 geocoded to a County at DX Geocode2020 to allow for both retrospective and cross-sectional analyses.
Codes
001-997County at diagnosis. Valid FIPS code.
998Outside state/county code unknown. Known town, city, state, or country of residence but county code not known AND a resident outside of the state of reporting institution (must meet all criteria).
999County unknown. The county of the patient is unknown, or the patient is not a United States resident. County is not documented in the patient's medical record.
Note: For U.S. residents, historically, standard codes are those of the FIPS publication “Counties and Equivalent Entities of the United States, Its Possessions, and Associated Areas.” These FIPS codes (FIPS 6-4) have been replaced by INCITS standard codes, however, there is no impact on this variable as the codes align with the system the Census used for each decennial census and will automatically be accounted for during geocoding.
COUNTY--CURRENT
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
18403NAACCR2192 - 2194
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Code for county of patient’s current residence. See Chapter V, Unresolved Issues, for further discussion.

Note:
This item was used by CoC only. CoC recommended use of FIPS codes (see Appendix A). The ROADS Manual also provided for use of geocodes for countries of residence outside the United States and Canada to be used in the county fields.
Rationale
This item may be used in administrative reports to define a referral area.
Codes (in addition to FIPS and geocodes)
998Known town, city, state, or country of residence but county code not known AND a resident outside of the state of reporting institution (must meet all criteria)
999County unknown
Note: This data item is no longer supported by CoC (as of January 1, 2003).
CRC CHECKSUM
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
208110NAACCR199861920 - 1929
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
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.
CS EXTENSIONRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28103AJCC200310988 - 990
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Identifies contiguous growth (extension) of the primary tumor within the organ of origin or its direct extension into neighboring organs. For certain sites such as ovary, discontinuous metastasis is coded in CS Extension.
Rationale
Tumor extension at diagnosis is a prognostic indicator used by Collaborative Staging to derive some TNM-T codes and some SEER Summary Stage codes.
Codes (See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
Note: For cases diagnosed prior to 2010, this was a 2 character field in CS version 1 which was converted to a 3 character field in CS version 2. Most 2 character codes were converted by adding a zero as the third character. For example, code 05 was usually converted to 050, 10 to 100, 11 to 110, etc. Special codes such as 88 and 99 were usually converted to 888 and 999, respectively.
CS LYMPH NODESRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28303AJCC200310992 - 994
Alternate Name:CS Lymph Nodes (SEER EOD)
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Identifies the regional lymph nodes involved with cancer at the time of diagnosis.
Rationale
The involvement of specific regional lymph nodes is a prognostic indicator used by Collaborative Staging to derive some TNM-N codes and SEER Summary Stage codes.
Codes (See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
Note: For cases prior to 2010, this was a 2 character field in CS version 1 which was converted to a 3 character field in CS version 2. Most 2 character codes were converted by adding a zero as the third character. For example, code 05 was usually converted to 050, 10 to 100, 11 to 110, etc. Special codes such as 88 and 99 were usually converted to 888 and 999 respectively.
CS LYMPH NODES EVALRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28401AJCC995 - 995
Alternate Name:CS Regional Nodes Evaluation
CS Reg Nodes Eval
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Records how the code for CS Lymph Nodes [2830] was determined, based on the diagnostic methods employed.
Rationale
This data item is used by Collaborative Staging to describe whether the staging basis for the TNM-N code is clinical or pathological and to record applicable prefix and suffix descriptors used with TNM staging.
Codes (See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS METS AT DXRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28502AJCC200310996 - 997
Alternate Name:CS Metastasis at Diagnosis
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Identifies the distant site(s) of metastatic involvement at time of diagnosis.
Rationale
The presence of metastatic disease at diagnosis is an independent prognostic indicator, and it is used by Collaborative Staging to derive TNM-M codes and SEER Summary Stage codes.
Codes (See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS METS AT DX-BONE
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28511AJCC201012999 - 999
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Identifies the presence of distant metastatic involvement of bone at time of diagnosis.
Rationale
The presence of metastatic bone disease at diagnosis is an independent prognostic indicator, and it is used by Collaborative Staging to derive TNM-M codes and SEER Summary Stage codes for some sites.
Codes (See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
Note: This includes only the bone, not the bone marrow.
CS METS AT DX-BRAIN
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28521AJCC2010121000 - 1000
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
The presence of metastatic brain disease at diagnosis is an independent prognostic indicator, and it is used by Collaborative Staging to derive TNM-M codes and SEER Summary Stage codes for some sites.
Rationale
The presence of metastatic brain disease at diagnosis is an independent prognostic indicator, and it is used by Collaborative Staging to derive TNM-M codes and SEER Summary Stage codes for some sites.
Codes (See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
Note: This includes only the brain, not spinal cord or other parts of the central nervous system.
CS METS AT DX-LIVER
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28531AJCC2010121001 - 1001
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Identifies the presence of distant metastatic involvement of the liver at time of diagnosis.
Rationale
The presence of metastatic liver disease at diagnosis is an independent prognostic indicator, and it is used by Collaborative Staging to derive TNM-M codes and SEER Summary Stage codes for some sites.
Codes (See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
Note: This includes only the liver.
CS METS AT DX-LUNG
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28541AJCC2010121002 - 1002
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Identifies the presence of distant metastatic involvement of the lung at time of diagnosis.
Rationale
The presence of metastatic lung disease at diagnosis is an independent prognostic indicator, and it is used by Collaborative Staging to derive TNM-M codes and SEER Summary Stage codes for some sites.
Codes (See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
Note: This includes only the lung, not pleura or pleural fluid.
CS METS EVALRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28601AJCC200310998 - 998
Alternate Name:CS Metastasis Evaluation
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Records how the code for CS Mets at Dx [2850] was determined based on the diagnostic methods employed.
Rationale
This data item is used by Collaborative Staging to describe whether the staging basis for the TNM-M code is clinical or pathological and to record applicable prefix and suffix descriptors used with TNM staging.
Codes (See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS POSTRX EXTENSION
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
27753AJCC2010121095 - 1097
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
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. The post-treatment data items measure the amount of tumor remaining after neoadjuvant therapy (systemic therapy or radiation therapy prior to surgery).

The implementation of this data item has been deferred indefinitely.
Rationale
The post-treatment data items will be used for analysis of the effectiveness of neoadjuvant therapy.
Codes (See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS POSTRX LYMPH NODES
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
27803AJCC2010121098 - 1100
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
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. The post-treatment data items measure the amount of tumor remaining after neoadjuvant therapy (systemic therapy or radiation therapy prior to surgery).

The implementation of this data item has been deferred indefinitely.
Rationale
The post-treatment data items will be used for analysis of the effectiveness of neoadjuvant therapy.
Codes (See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS POSTRX METS AT DX
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
27852AJCC2010121101 - 1102
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
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. The post-treatment data items measure the amount of tumor remaining after neoadjuvant therapy (systemic therapy or radiation therapy prior to surgery).

The implementation of this data item has been deferred indefinitely.
Rationale
The post-treatment data items will be used for analysis of the effectiveness of neoadjuvant therapy.
Codes (See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS POSTRX TUMOR SIZE
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
27703AJCC2010121092 - 1094
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
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. The post-treatment data items measure the amount of tumor remaining after neoadjuvant therapy (systemic therapy or radiation therapy prior to surgery).

The implementation of this data item has been deferred indefinitely.
Rationale
The post-treatment data items will be used for analysis of the effectiveness of neoadjuvant therapy.
Codes (See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS PRERX EXTENSION
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
27353AJCC2010121081 - 1083
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
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. The CS pre-treatment data items include all information prior to the start of therapy. In rare circumstances where workup could not be completed prior to therapy, these items may be based on testing after limited treatment in the absence of progression or regression of disease, such as delayed planned or usual diagnostic workup. This does not include diagnostic workup for progression of disease or regression.

The implementation of this data item has been deferred indefinitely.
Rationale
The CS pre-treatment data items will record the pre-treatment (clinical) stage. This is used for analysis of appropriate treatment selection. These items are a companion to the AJCC clinical stage information required by CoC, and likely will eventually replace the required AJCC staging. Codes are exactly the same as the regular CS codes. For these data fields, the eval fields also remain the same although the valid options will be limited by edits, in order to use the same tables in CS. The pre-treatment data items will be used for analysis of the effectiveness of neoadjuvant therapy.
Codes (See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS PRERX LYMPH NODES
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
27503AJCC2010121085 - 1087
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
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. The CS pre-treatment data items include all information prior to the start of therapy. In rare circumstances where workup could not be completed prior to therapy, these items may be based on testing after limited treatment in the absence of progression or regression of disease, such as delayed planned or usual diagnostic workup. This does not include diagnostic workup for progression of disease or regression.

The implementation of this data item has been deferred indefinitely.
Rationale
The CS pre-treatment data items will record the pre-treatment (clinical) stage. This is used for analysis of appropriate treatment selection. These items are a companion to the AJCC clinical stage information required by CoC, and likely will eventually replace the required AJCC staging. Codes are exactly the same as the regular CS codes. For these data fields, the eval fields also remain the same although the valid options will be limited by edits, in order to use the same tables in CS. The pre-treatment data items will be used for analysis of the effectiveness of neoadjuvant therapy.
Codes (See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS PRERX METS AT DX
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
27602AJCC2010121089 - 1090
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
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. The CS pre-treatment data items include all information prior to the start of therapy. In rare circumstances where workup could not be completed prior to therapy, these items may be based on testing after limited treatment in the absence of progression or regression of disease, such as delayed planned or usual diagnostic workup. This does not include diagnostic workup for progression of disease or regression.

The implementation of this data item has been deferred indefinitely.
Rationale
The CS pre-treatment data items will record the pre-treatment (clinical) stage. This is used for analysis of appropriate treatment selection. These items are a companion to the AJCC clinical stage information required by CoC, and likely will eventually replace the required AJCC staging. Codes are exactly the same as the regular CS codes. For these data fields, the eval fields also remain the same although the valid options will be limited by edits, in order to use the same tables in CS. The pre-treatment data items will be used for analysis of the effectiveness of neoadjuvant therapy.
Codes (See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS PRERX METS EVAL
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
27651AJCC2010121091 - 1091
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
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. The CS pre-treatment data items include all information prior to the start of therapy. In rare circumstances where workup could not be completed prior to therapy, these items may be based on testing after limited treatment in the absence of progression or regression of disease, such as delayed planned or usual diagnostic workup. This does not include diagnostic workup for progression of disease or regression.

The implementation of this data item has been deferred indefinitely.

Rationale
The CS pre-treatment data items will record the pre-treatment (clinical) stage. This is used for analysis of appropriate treatment selection. These items are a companion to the AJCC clinical stage information required by CoC, and likely will eventually replace the required AJCC staging. Codes are exactly the same as the regular CS codes. For these data fields, the eval fields also remain the same although the valid options will be limited by edits, in order to use the same tables in CS. The pre-treatment data items will be used for analysis of the effectiveness of neoadjuvant therapy.
Codes (See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS PRERX REG NODES EVAL
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
27551AJCC2010121088 - 1088
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
The CS pre-treatment data items include all information prior to the start of therapy. In rare circumstances where workup could not be completed prior to therapy, these items may be based on testing after limited treatment in the absence of progression or regression of disease, such as delayed planned or usual diagnostic workup. This does not include diagnostic workup for progression of disease or regression.

The implementation of this data item has been deferred indefinitely.
Rationale
The CS pre-treatment data items will record the pre-treatment (clinical) stage. This is used for analysis of appropriate treatment selection. These items are a companion to the AJCC clinical stage information required by CoC, and likely will eventually replace the required AJCC staging. Codes are exactly the same as the regular CS codes. For these data fields, the eval fields also remain the same although the valid options will be limited by edits, in order to use the same tables in CS. The pre-treatment data items will be used for analysis of the effectiveness of neoadjuvant therapy.
Codes (See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS PRERX TUM SZ/EXT EVAL
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
27401AJCC2010121084 - 1084
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
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. The CS pre-treatment data items include all information prior to the start of therapy. In rare circumstances where workup could not be completed prior to therapy, these items may be based on testing after limited treatment in the absence of progression or regression of disease, such as delayed planned or usual diagnostic workup. This does not include diagnostic workup for progression of disease or regression.

The implementation of this data item has been deferred indefinitely.
Rationale
The CS pre-treatment data items will record the pre-treatment (clinical) stage. This is used for analysis of appropriate treatment selection. These items are a companion to the AJCC clinical stage information required by CoC, and likely will eventually replace the required AJCC staging. Codes are exactly the same as the regular CS codes. For these data fields, the eval fields also remain the same although the valid options will be limited by edits, in order to use the same tables in CS. The pre-treatment data items will be used for analysis of the effectiveness of neoadjuvant therapy.
Codes (See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS PRERX TUMOR SIZE
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
27303AJCC2010121078 - 1080
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
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. The CS pre-treatment data items include all information prior to the start of therapy. In rare circumstances where workup could not be completed prior to therapy, these items may be based on testing after limited treatment in the absence of progression or regression of disease, such as delayed planned or usual diagnostic workup. This does not include diagnostic workup for progression of disease or regression.

The implementation of this data item has been deferred indefinitely.
Rationale
The CS pre-treatment data items will record the pre-treatment (clinical) stage. This is used for analysis of appropriate treatment selection. These items are a companion to the AJCC clinical stage information required by CoC, and likely will eventually replace the required AJCC staging. Codes are exactly the same as the regular CS codes. For these data fields, the eval fields also remain the same although the valid options will be limited by edits, in order to use the same tables in CS. The pre-treatment data items are used for analysis of the effectiveness of neoadjuvant therapy.
Codes (See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS SITE-SPECIFIC FACTOR 1
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28803AJCC2003101003 - 1005
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.
Rationale
Site-specific factors are used to record additional staging information needed by Collaborative Staging to derive TNM and/or SEER Summary Stage codes for particular site-histology schema.
Codes (The information recorded in CS Site-Specific Factor 1 differs for each anatomic site. See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS SITE-SPECIFIC FACTOR 2
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28903AJCC2003101006 - 1008
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.
Rationale
Site-specific factors are used to record additional staging information needed by Collaborative Staging to derive TNM and/or SEER Summary Stage codes for particular site-histology schema.
Codes (The information recorded in CS Site-Specific Factor 2 differs for each anatomic site. See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS SITE-SPECIFIC FACTOR 3
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
29003AJCC2003101009 - 1011
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.
Rationale
Site-specific factors are used to record additional staging information needed by Collaborative Staging to derive TNM and/or SEER Summary Stage codes for particular site-histology schema.
Codes (The information recorded in CS Site-Specific Factor 3 differs for each anatomic site. See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS SITE-SPECIFIC FACTOR 4
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
29103AJCC2003101012 - 1014
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.
Rationale
Site-specific factors are used to record additional staging information needed by Collaborative Staging to derive TNM and/or SEER Summary Stage codes for particular site-histology schema.
Codes (The information recorded in CS Site-Specific Factor 4 differs for each anatomic site. See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS SITE-SPECIFIC FACTOR 5
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
29203AJCC2003101015 - 1017
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.
Rationale
Site-specific factors are used to record additional staging information needed by Collaborative Staging to derive TNM and/or SEER Summary Stage codes for particular site-histology schema.
Codes (The information recorded in CS Site-Specific Factor 5 differs for each anatomic site. See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS SITE-SPECIFIC FACTOR 6
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
29303AJCC2003101018 - 1020
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.
Rationale
Site-specific factors are used to record additional staging information needed by Collaborative Staging to derive TNM and/or SEER Summary Stage codes for particular site-histology schema.
Codes (The information recorded in CS Site-Specific Factor 6 differs for each anatomic site. See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS SITE-SPECIFIC FACTOR 7
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28613AJCC2010121021 - 1023
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.
Rationale
Site-specific factors are used to record additional staging information needed by Collaborative Staging to derive TNM and/or SEER Summary Stage codes for particular site-histology schema.
Codes (The information recorded in CS Site-Specific Factor 7 differs for each anatomic site. See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS SITE-SPECIFIC FACTOR 8
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28623AJCC2010121024 - 1026
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.
Rationale
Site-specific factors are used to record additional staging information needed by Collaborative Staging to derive TNM and/or SEER Summary Stage codes for particular site-histology schema.
Codes (The information recorded in CS Site-Specific Factor 8 differs for each anatomic site. See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS SITE-SPECIFIC FACTOR 9
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28633AJCC2010121027 - 1029
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.
Rationale
Site-specific factors are used to record additional staging information needed by Collaborative Staging to derive TNM and/or SEER Summary Stage codes for particular site-histology schema.
Codes (The information recorded in CS Site-Specific Factor 9 differs for each anatomic site. See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS SITE-SPECIFIC FACTOR10
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28643AJCC2010121030 - 1032
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.
Rationale
Site-specific factors are used to record additional staging information needed by Collaborative Staging to derive TNM and/or SEER Summary Stage codes for particular site-histology schema.
Codes (The information recorded in CS Site-Specific Factor10 differs for each anatomic site. See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS SITE-SPECIFIC FACTOR11
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28653AJCC2010121033 - 1035
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.
Rationale
Site-specific factors are used to record additional staging information needed by Collaborative Staging to derive TNM and/or SEER Summary Stage codes for particular site-histology schema.
Codes (The information recorded in CS Site-Specific Factor11 differs for each anatomic site. See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS SITE-SPECIFIC FACTOR12
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28663AJCC2010121036 - 1038
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.
Rationale
Site-specific factors are used to record additional staging information needed by Collaborative Staging to derive TNM and/or SEER Summary Stage codes for particular site-histology schema.
Codes (The information recorded in CS Site-Specific Factor12 differs for each anatomic site. See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS SITE-SPECIFIC FACTOR13
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28673AJCC2010121039 - 1041
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.
Rationale
Site-specific factors are used to record additional staging information needed by Collaborative Staging to derive TNM and/or SEER Summary Stage codes for particular site-histology schema.
Codes (The information recorded in CS Site-Specific Factor13 differs for each anatomic site. See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS SITE-SPECIFIC FACTOR14
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28683AJCC2010121042 - 1044
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.
Rationale
Site-specific factors are used to record additional staging information needed by Collaborative Staging to derive TNM and/or SEER Summary Stage codes for particular site-histology schema.
Codes (The information recorded in CS Site-Specific Factor14 differs for each anatomic site. See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS SITE-SPECIFIC FACTOR15
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28693AJCC2010121045 - 1047
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.
Rationale
Site-specific factors are used to record additional staging information needed by Collaborative Staging to derive TNM and/or SEER Summary Stage codes for particular site-histology schema.
Codes (The information recorded in CS Site-Specific Factor15 differs for each anatomic site. See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS SITE-SPECIFIC FACTOR16
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28703AJCC2010121048 - 1050
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.
Rationale
Site-specific factors are used to record additional staging information needed by Collaborative Staging to derive TNM and/or SEER Summary Stage codes for particular site-histology schema.
Codes (The information recorded in CS Site-Specific Factor16 differs for each anatomic site. See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS SITE-SPECIFIC FACTOR17
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28713AJCC2010121051 - 1053
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.
Rationale
Site-specific factors are used to record additional staging information needed by Collaborative Staging to derive TNM and/or SEER Summary Stage codes for particular site-histology schema.
Codes (The information recorded in CS Site-Specific Factor17 differs for each anatomic site. See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS SITE-SPECIFIC FACTOR18
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28723AJCC2010121054 - 1056
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.
Rationale
Site-specific factors are used to record additional staging information needed by Collaborative Staging to derive TNM and/or SEER Summary Stage codes for particular site-histology schema.
Codes (The information recorded in CS Site-Specific Factor18 differs for each anatomic site. See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS SITE-SPECIFIC FACTOR19
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28733AJCC2010121057 - 1059
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.
Rationale
Site-specific factors are used to record additional staging information needed by Collaborative Staging to derive TNM and/or SEER Summary Stage codes for particular site-histology schema.
Codes (The information recorded in CS Site-Specific Factor19 differs for each anatomic site. See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS SITE-SPECIFIC FACTOR20
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28743AJCC2010121060 - 1062
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.
Rationale
Site-specific factors are used to record additional staging information needed by Collaborative Staging to derive TNM and/or SEER Summary Stage codes for particular site-histology schema.
Codes (The information recorded in CS Site-Specific Factor20 differs for each anatomic site. See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS SITE-SPECIFIC FACTOR21
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28753AJCC2010121063 - 1065
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.
Rationale
Site-specific factors are used to record additional staging information needed by Collaborative Staging to derive TNM and/or SEER Summary Stage codes for particular site-histology schema.
Codes (The information recorded in CS Site-Specific Factor21 differs for each anatomic site. See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS SITE-SPECIFIC FACTOR22
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28763AJCC2010121066 - 1068
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.
Rationale
Site-specific factors are used to record additional staging information needed by Collaborative Staging to derive TNM and/or SEER Summary Stage codes for particular site-histology schema.
Codes (The information recorded in CS Site-Specific Factor22 differs for each anatomic site. See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS SITE-SPECIFIC FACTOR23
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28773AJCC2010121069 - 1071
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.
Rationale
Site-specific factors are used to record additional staging information needed by Collaborative Staging to derive TNM and/or SEER Summary Stage codes for particular site-histology schema.
Codes (The information recorded in CS Site-Specific Factor23 differs for each anatomic site. See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS SITE-SPECIFIC FACTOR24
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28783AJCC2010121072 - 1074
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.
Rationale
Site-specific factors are used to record additional staging information needed by Collaborative Staging to derive TNM and/or SEER Summary Stage codes for particular site-histology schema.
Codes (The information recorded in CS Site-Specific Factor24 differs for each anatomic site. See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS SITE-SPECIFIC FACTOR25
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28793AJCC2010121075 - 1077
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.
Rationale
CS Site-Specific Factor25 is used to discriminate between CS staging schema or between AJCC chapters where site and histology alone are insufficient to identify the tumor type or location to identify the applicable staging method.
Codes (The information recorded in CS Site-Specific Factor25 differs for each anatomic site. See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS TUMOR SIZE
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28003AJCC200310985 - 987
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Records the largest dimension or diameter of the primary tumor in millimeters.
Rationale
Tumor size at diagnosis is an independent prognostic indicator for many tumors and it is used by Collaborative Staging to derive some TNM-T codes.
Codes (See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS TUMOR SIZE/EXT EVALRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
28201AJCC200310991 - 991
Alternate Name:CS Tumor Size/Extension Evaluation
CS TS/Ext-Eval
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Records how the codes for the two items CS Tumor Size [2800] and CS Extension [2810] were determined, based on the diagnostic methods employed.
Rationale
This item is used by Collaborative Staging to describe whether the staging basis for the TNM-T code is clinical or pathological and to record applicable prefix and suffix descriptors used with TNM staging.
Codes (See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS VERSION DERIVED
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
29366AJCC1173 - 1178
Alternate Name:CS Version Latest
XML NAACCR ID:
XML PARENT ELEMENT:
Description
This data item is recorded the first time the CS output fields are derived and should be updated each time the CS Derived items are recomputed. The CS version number is returned as part of the output of the CS algorithm.
Rationale
The CS algorithm may be re-applied to compute the CS Derived items; for example, when the data are to be used for a special study, transmitted, or when an updated CS algorithm is produced. This item identifies the specific algorithm used to obtain the CS Derived values in the data record.
Codes (See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS Version Derived is a 6-digit code (e.g., 010100). The first two digits represent the major version number; the second two digits represent minor version changes; and, the last two digits represent even less significant changes, such as corrections of typographical errors that do not affect coding or derivation results.

This item should not be blank if the CS Derived items contain values. It should be blank if the CS Derived items are empty or the CS algorithm has not been applied.
CS VERSION INPUT CURRENT
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
29376AJCC2010121161 - 1166
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
This item indicates the version of CS input fields after they have been updated or recoded. This data item is recorded the first time the CS input fields are entered and should be updated each time the CS input fields are modified.
Rationale
Over time, the input codes and instructions for CS items may change. This item identifies the correct interpretation of input CS items.
Codes (See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS Version Input Current is a 6-digit code (e.g., 020100). The first two digits represent the major version number; the second two digits represent minor version changes; and, the last two digits represent even less significant changes, such as corrections of typographical errors that do not affect coding or derivation of results.
CS VERSION INPUT ORIGINAL
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
29356AJCC1167 - 1172
Alternate Name:CS Version 1ST
XML NAACCR ID:
XML PARENT ELEMENT:
Description
This item indicates the number of the version initially used to code Collaborative Staging (CS) fields. The CS version number is returned as part of the output of the CS algorithm.
Rationale
Over time, the input codes and instructions for CS items may change. This item identifies the correct interpretation of input CS items.
Codes (See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org),13 for rules and site-specific codes and coding structures.)
CS Version Input Original is a 6-digit code (e.g., 010100). The first two digits represent the major version number; the second two digits represent minor version changes; and, the last two digits represent even less significant changes, such as corrections of typographical errors that do not affect coding or derivation of results.
DATE 1ST CRS RX COC
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
12708CoC1446 - 1453
Alternate Name:Date Started (pre 96 CoC)
Date of First Course Treatment (CoC)
Date of 1st Crs RX--CoC
XML NAACCR ID:
XML PARENT ELEMENT:
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 FORDS for details. See Chapter V, Unresolved Issues for further discussion of the difference between SEER and CoC items. See Chapter X for date format. Use Date 1st Crs RX CoC Flag [1271] if there is no appropriate or known date for this item.
 
Formerly Date of 1st Crs RX--CoC.
Clarification of NPCR Required Status
Central registries funded by NPCR are required to collect either Date Initial RX SEER [1260] or Date 1st Crs RX CoC [1270].
DATE 1ST CRS RX COC FLAG
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
12712NAACCR2010121454 - 1455
Alternate Name:Date of 1st Crs Rx Flag
XML NAACCR ID:
XML PARENT ELEMENT:
Description
This flag explains why no appropriate value is in the field, Date 1st Crs RX CoC [1270].
 
Formerly Date of 1st Crs Rx Flag.
Rationale
Before Version 12 (through 2009 diagnosis), date fields included codes that provided information other than dates. As part of an initiative to standardize date fields, new fields were introduced to accommodate non-date information that had previously been transmitted in date fields.
Codes (See Appendix H for the complete Flavors of Null table, which includes the NAACCR codes, HL7 codes and definitions.)
10No information whatsoever can be inferred from this exceptional value (e.g, unknown whether treatment was administered)
11No proper value is applicable in this context (Autopsy only)
12A proper value is applicable but not known (e.g., treatment administered but date is unknown)
BlankA valid date value is provided in item Date 1st Crs RX CoC [1270], or the date was not expected to have been transmitted
Comment: This is part of the initiative of the transformation from the old NAACCR date standards to interoperable dates.
DATE CASE COMPLETED
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
20908NAACCR1959 - 1966
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
The date that: (1) the abstractor decided that the tumor report was complete and (2) the case passed all edits that were applied. Definitions may vary among registries and software providers. This field is locally used by central registries. See Chapter X for date format. Standard edits check that no dates are later than the current date. These specifications will not necessarily be the same as those used for Date Case Completed--CoC [2092].
DATE CASE COMPLETED--COC
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
20928CoC2010121967 - 1974
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
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 FORDS for details. This item should be autocoded by the registry software; specifications may be obtained from NCDB. The CoC specifications will not necessarily be the same as those used for Date Case Completed [2090]. See Chapter X for date format.
DATE CASE INITIATED
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
20858NAACCR2010121951 - 1958
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Date the electronic abstract is initiated in the reporting facility's cancer registry database. See Chapter X for date format. Standard edits check that no dates are later than the current date or the date completed.
Rationale
This item is used to assess and monitor the timeliness of reporting. Timeliness of abstracting (and reporting) is a concern for all standard-setting organizations and consequently, timeliness standards have been established. Examples of use are as follows:

·        This item can be used with the Date of 1stContact [580] to measure timeliness of abstracting by individual reporting facilities

·        This item can be used with Date Case Report Exported [2110] to determine the “residency time” of a case report within a reporting facility’s database prior to data transmission to a central cancer registry

·        This item can be used with Date Case Report Received [2111] to monitor central registry timeliness in entering case reports (for case reports abstracted in-house from hardcopy provided by a reporting facility)

·        This item can be used with Date Case Completed [2090] to monitor timeliness of case report completion

DATE CASE LAST CHANGED
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
21008NAACCR1975 - 1982
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Date the case was last changed or updated. See Chapter X for date format. Standard edits check that no dates are later than the current date.
DATE CASE REPORT EXPORTED
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
21108NPCR1983 - 1990
Alternate Name:Date Case Transmitted (pre-98 NAACCR)
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Date the reporting facility exports the electronic abstract to a file for transmission to the central registry. See Chapter X for date format. Standard edits check that no dates are later than the current date. Definitions may vary among registries and software providers.
DATE CASE REPORT LOADED
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
21128NPCR19975.11999 - 2006
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Date the tumor report is loaded into a central registry computerized processing file for initiation of quality control activities (e.g., visual editing, application of computerized edits, etc.). See Chapter X for date format.
DATE CASE REPORT RECEIVED
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
21118NPCR19975.11991 - 1998
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Date the abstract (or source record) is received by the central cancer registry for the respective tumor. If multiple reports are received from two or more sources and if a single date is needed, use the date the first abstract (or source record) was received from any source. See Chapter X for date format.
Rationale
This item is used to assess and monitor the timeliness of reporting. Timeliness of abstracting (and reporting) is a concern for all standard-setting organizations. This item can be used with the Date of 1st Contact [580] or the Path--Date of Specimen Collection [7320] to measure timeliness of reporting to central cancer registries by individual reporting facilities. This data item also can be used with the Date Tumor Record Availbl [2113] to measure timeliness of processing within the central cancer registry.
DATE CONCLUSIVE DX
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
4438SEER200611567 - 574
Alternate Name:Date of Conclusive Diagnosis
Date of Conclusive Terminology
Date of Conclusive DX
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Documents the date when a conclusive cancer diagnosis (definite statement of malignancy) is made following an initial diagnosis that was based only on ambiguous terminology. See Chapter X for date format. Use DATE CONCLUSIVE DX FLAG [448] if there is no appropriate or known date for this item.
 
Formerly Date of Conclusive DX.
Rationale
This date will allow analysis of the primary site locations and frequency of cases that were originally diagnosed by ambiguous terminology and later confirmed by other conclusive method.

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

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

When death certificate only (Class of Case 49, Type of Reporting Source 7) tumors are collected, the date of death should be used as the Date of 1st Contact. When Autopsy Only (Class of Case 38, Type of Reporting Source 6) tumors are collected, the date of death should be used as the Date of 1st Contact.
Rationale
Timeliness of abstracting (and reporting) is a concern for all standard-setting organizations. Date of 1st Contact is one of several data items that can be used to measure timeliness of reporting to central cancer registries by individual facilities. For tumors that are not diagnosed at the reporting facility following its Reference Date (Class of Case 20-22, 30-37), the Date of 1st Contact [580] can be used in conjunction with the Date Case Report Received [2111] to measure timeliness of reporting by individual facilities.
Comment: To accurately measure the timeliness of data collection and submission of abstracts that are first diagnosed at autopsy (Class of Case 38, Type of Reporting Source 6) the date of death should be used as the Date of 1st Contact since the diagnosis was not determined until the autopsy was performed. Death Certificate Only cases (Class of Case 49, Type of Reporting Source 7) are created only by the central registry. For these cases, Date of 1st Contact should be filled with the date of death, and timeliness for DCO cases should be measured by different criteria.
DATE OF 1ST CONTACT FLAG
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
5812NAACCR201012753 - 754
Alternate Name:Date of First Contact Flag
XML NAACCR ID:
XML PARENT ELEMENT:
Description
This flag explains why no appropriate value is in the field Date of 1st Contact [580]. This data item was first available in Volume II Version 12.
Rationale
Before Version 12 (through 2009 diagnosis), date fields included codes that provided information other than dates. As part of an initiative to standardize date fields, new fields were introduced to accommodate non-date information that had previously been transmitted in date fields.
Codes (See Appendix H for the complete Flavors of Null table, which includes the NAACCR codes, HL7 codes and definitions.)
12A proper value is applicable but not known (e.g., date of 1st contact is unknown)
BlankA valid date value is provided in item Date of 1st Contact [580], or the date was not expected to have been transmitted
Comment: This is part of the initiative of the transformation from the old NAACCR date standards to interoperable dates.
DATE OF BIRTH
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
2408SEER/CoC196 - 203
Alternate Name:Birth Date(SEER/CoC/CCCR)
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Date of birth of the patient. See Chapter X for date format. If age at diagnosis and year of diagnosis are known, but year of birth is unknown, then year of birth should be calculated and so coded. Only the year should be entered, left-justified. Estimate date of birth when information is not available. It is better to estimate than to leave birth date unknown.
DATE OF BIRTH FLAG
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
2412NAACCR201012204 - 205
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
This flag explains why no appropriate value is in the field, Date of Birth [240]. This data item was first available in Volume II Version 12.
Rationale
Before Version 12 (through 2009 diagnosis), date fields included codes that provided information other than dates. As part of an initiative to standardize date fields, new fields were introduced to accommodate non-date information that had previously been transmitted in date fields.
Codes (See Appendix H for the complete Flavors of Null table, which includes the NAACCR codes, HL7 codes and definitions. Use code 12 when date of birth is unknown.)
12A proper value is applicable but not known (i.e., birth date is unknown)
BlankA valid date value is provided in item Date of Birth [240], or the date was not expected to have been transmitted
Comment: This is part of the initiative of the transformation from the old NAACCR date standards to interoperable dates.
DATE OF DEATH--CANADA
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
17558CCCR200911.32280 - 2287
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
This field is used by the Canadian provinces/territories to record the patient's date of death. See Chapter X for date format.
DATE OF DEATH--CANADAFLAG
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
17562NAACCR2010122288 - 2289
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
This flag explains why no appropriate value is in the field, Date of Death--Canada [1755]. This data item was first available in Volume II Version 12.
Rationale
Before Version 12 (through 2009 diagnosis), date fields included codes that provided information other than dates. As part of an initiative to standardize date fields, new fields were introduced to accommodate non-date information that had previously been transmitted in date fields.
Codes (See Appendix H for the complete Flavors of Null table, which includes the NAACCR codes, HL7 codes and definitions.)
10No information whatsoever can be inferred from this exceptional value (e.g, patient is not known to be deceased)
11No proper value is applicable in this context (e.g. patient is alive)
12A proper value is applicable but not known (e.g., date of death is unknown)
BlankA valid date value is provided in item Date of Death--Canada [1755], or the date was not expected to have been transmitted
Comment: This is part of the initiative of the transformation from the old NAACCR date standards to interoperable dates.
DATE OF DIAGNOSIS
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
3908SEER/CoC530 - 537
Alternate Name:Date of Initial Diagnosis (CoC)
XML NAACCR ID:
XML PARENT ELEMENT:
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 FORDS manual.
DATE OF DIAGNOSIS FLAG
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
3912NAACCR201012538 - 539
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
This flag explains why no appropriate value in in the field, Date of Diagnosis [390]. This data item was first available in Volume II Version 12.
Rationale
Before Version 12 (through 2009 diagnosis), date fields included codes that provided information other than dates. As part of an initiative to standardize date fields, new fields were introduced to accommodate non-date information that had previously been transmitted in date fields.
Codes (See Appendix H for the complete Flavors of Null table, which includes the NAACCR codes, HL7 codes and definitions.)
12A proper value is applicable but not known. (e.g., date of diagnosis is unknown)
BlankA valid date value is provided in item Date of Diagnosis [390], or the date was not expected to have been transmitted
Comment: This is part of the initiative of the transformation from the old NAACCR date standards to interoperable dates.
DATE OF INPT ADM
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
5908NAACCR755 - 762
Alternate Name:Date of Inpatient Admission (CoC)
Date of Inpatient Adm
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Date of the inpatient admission to the reporting facility for the most definitive surgery. In the absence of surgery, use date of inpatient admission for any other therapy. In the absence of therapy, use date of inpatient admission for diagnostic evaluation. See Chapter X for date format. Use DATE OF INPT ADM FLAG [591] if there is no appropriate or known date for this item.
 
Formerly Date of Inpatient Adm.
Note: This data item is no longer supported by CoC (as of January 1, 2003).
DATE OF INPT ADM FLAG
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
5912NAACCR201012763 - 764
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
This flag explains why no appropriate value is in the field, Date of Inpt Adm [590]. 
Rationale
Before Version 12 (through 2009 diagnosis), date fields included codes that provided information other than dates. As part of an initiative to standardize date fields, new fields were introduced to accommodate non-date information that had previously been transmitted in date fields.
Codes (See Appendix H for the complete Flavors of Null table, which includes the NAACCR codes, HL7 codes and definitions.)
10No information whatsoever can be inferred from this exceptional value (e.g, unknown if patient was an inpatient).
11No proper value is applicable in this context (e.g., patient was never an inpatient at the reporting facility).
12A proper value is applicable but not known. This event occurred, but the date is unknown (e.g., the patient was an inpatient but the date is unknown).
BlankA valid date value is provided in item Date of Inpt Adm [590], or the date was not expected to have been transmitted.
Comment: This is part of the initiative of the transformation from the old NAACCR date standards to interoperable dates.
DATE OF INPT DISCH
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
6008NAACCR765 - 772
Alternate Name:Date of Inpatient Discharge (CoC)
Date of Inpatient Disch
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Date of the inpatient discharge from the reporting facility after the most definitive surgery. In the absence of surgery, use date of inpatient discharge for other therapy. In the absence of therapy, use date of inpatient discharge for diagnostic evaluation. This discharge date corresponds to the admission date described by Date of Inpt Adm [590]. See Chapter X for date format. Use DATE OF INPT DISCH FLAG [601] if there is no appropriate or known date for this item. Note: This item is not the same as the old NAACCR item, Date of Discharge, which has been deleted from the NAACCR layout.
 
Formerly Date of Inpatient Disch.
Note: This data item is no longer supported by CoC (as of January 1, 2003).
DATE OF INPT DISCH FLAG
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
6012NAACCR201012773 - 774
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
This flag explains why no appropriate value is in the field, Date of Inpt Disch [600]. This data item was first available in Volume II Version 12.
Rationale
Before Version 12 (through 2009 diagnosis), date fields included codes that provided information other than dates. As part of an initiative to standardize date fields, new fields were introduced to accommodate non-date information that had previously been transmitted in date fields.
Codes (See Appendix H for the complete Flavors of Null table, which includes the NAACCR codes, HL7 codes and definitions.)
10No information whatsoever can be inferred from this exceptional value (e.g, unknown if patient was an inpatient).
11No proper value is applicable in this context (e.g., patient was never an inpatient at the reporting facility).
12A proper value is applicable but not known. This event occurred, but the date is unknown (e.g., the patient was an inpatient but the date is unknown).
BlankA valid date value is provided in item Date of Inpt Disch [600], or the date was not expected to have been transmitted.
Comment: This is part of the initiative of the transformation from the old NAACCR date standards to interoperable dates.
DATE OF LAST CONTACT
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
17508SEER/CoC2116 - 2123
Alternate Name:Date of Last Contact or Death (CoC)
Date of Last Follow-Up or of Death (SEER)
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Date of last contact with the patient, or date of death. If the patient has multiple tumors, Date of Last Contact should be the same for all tumors. See Chapter X for date format.
Rationale
Used for recording Date of Last Contact from active or passive follow-up. Used to record date of death and to calculate survival.
DATE OF LAST CONTACT FLAG
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
17512NAACCR2010122124 - 2125
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
This flag explains why no appropriate value is in the field, Date of Last Contact [1750].
Rationale
Before Version 12 (through 2009 diagnosis), date fields included codes that provided information other than dates. As part of an initiative to standardize date fields, new fields were introduced to accommodate non-date information that had previously been transmitted in date fields.
Codes (See Appendix H for the complete Flavors of Null table, which includes the NAACCR codes, HL7 codes and definitions.)
12A proper value is applicable but not known. This event occurred, but the date is unknown (e.g., date of last contact is unknown).
BlankA valid date value is provided in item Date of Last Contact [1750], or the date was not expected to have been transmitted.
Comment: This is part of the initiative of the transformation from the old NAACCR date standards to interoperable dates.
DATE OF MULT TUMORS
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
4458SEER200611579 - 586
Alternate Name:Date of Multiple Tumors
XML NAACCR ID:
XML PARENT ELEMENT:
Description
This data item is used to identify the month, day and year the patient is diagnosed with multiple tumors reported as a single primary using the SEER, IARC, or Canadian Cancer Registry multiple primary rules. See Chapter X for date format. Use DATE OF MULT TUMORS FLAG [439] if there is no appropriate or known date for this item.
 
Formerly Date of Multiple Tumors.
Rationale
Patients with multiple tumors may have a worse prognosis or more extensive treatment than patients with a single tumor. This data item will make it possible to identify important information about these cases for data analysis. The Date of Multiple Tumors will allow separation of cases with multiple tumors present at the time of initial diagnosis from cases with subsequent tumors abstracted as the same primary. The date will allow tracking of the time interval between the date of original diagnosis and the first date of subsequent tumor(s) for specific primary sites and tumor histologies.
Codes (refer to http://seer.cancer.gov/tools/mphrules/index.html for additional instructions).
DATE OF MULT TUMORS FLAG
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
4392NAACCR201012587 - 588
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
This flag explains why no appropriate value is in the field, Date of Mult Tumors [445]. This data item was first available in Volume II Version 12.
Rationale
Before Version 12 (through 2009 diagnosis), date fields included codes that provided information other than dates. As part of an initiative to standardize date fields, new fields were introduced to accommodate non-date information that had previously been transmitted in date fields.
Codes (See Appendix H for the complete Flavors of Null table, which includes the NAACCR codes, HL7 codes and definitions.)
11No proper value is applicable in this context (e.g., information on multiple tumors not collected/not applicable for this site).
12A proper value is applicable but not known. This event occurred, but the date is unknown (e.g., patient was diagnosed with multiple tumors and the date is unknown).
15Information is not available at this time, but it is expected that it will be available later (e.g., single tumor).
BlankA valid date value is provided in item Date of Mult Tumors [445], or the date was not expected to have been transmitted.
Comment: This is part of the initiative of the transformation from the old NAACCR date standards to interoperable dates.
DATE TUMOR RECORD AVAILBL
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
21138NPCR19975.12007 - 2014
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Date the demographic and tumor identification information on a primary/reportable neoplasm, compiled from one or more source records, from one or more facilities, is available in the central cancer registry database to be counted as an incident tumor. Cancer identification information includes, at a minimum, site, histology, laterality, behavior, and date of diagnosis. See Chapter X for date format.
Rationale
This item is used to assess and monitor the timeliness of reporting. Timeliness of abstracting (and reporting) is a concern for all standard-setting organizations. This data item can be used with the Date Case Report Received [2111] to measure timeliness of processing within the central cancer registry. This item also can be used with the Date of 1st Contact [580] or the Path--Date of Specimen Collection [7320] to measure overall timeliness.
DC STATE FILE NUMBER
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
23806State201112.23878 - 3883
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Death certificate identification number as assigned by the vital statistics office in the place recorded in Place of Death [1940].
DERIVED AJCC-6 M
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
29802AJCC2003101109 - 1110
Alternate Name:Derived 6 M Storage Code
Derived AJCC M
XML NAACCR ID:
XML PARENT ELEMENT:
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 (http://cancerstaging.org/cstage/manuals.html).13 The display code should be used for display on the screen and in reports.
Rationale
The Collaborative Stage Data Collection System was designed by a joint task force including representatives from SEER, ACoS, CDC, NAACCR, NCRA, CCCR, CPAC, and AJCC, to provide a single uniform set of codes and rules for coding extent of disease (EOD) and stage information to meet the needs of all of the participating standard setters. When CS data items are coded, a computer algorithm provides the derivation of T, N, M, and stage-based on AJCC Cancer Staging Manual 6th & 7th Editions, SEER Summary Stage 1977, and SEER Summary Stage 2000. There are separate derived CS fields in the NAACCR record based on AJCC 6th Edition for 2004+ cases and AJCC 7th Edition for 2010+ cases.
Codes (See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org/cstage/manuals.html),13 for rules and site-specific codes and coding structures.)
DERIVED AJCC-6 M DESCRIPT
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
29901AJCC2003101111 - 1111
Alternate Name:Derived AJCC M Descriptor
Derived 6 M Descriptor Storage Code
XML NAACCR ID:
XML PARENT ELEMENT:
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 (http://cancerstaging.org/cstage/manuals.html).13 The display code should be used for display on the screen and in reports.
Rationale
The Collaborative Stage Data Collection System was designed by a joint task force including representatives from SEER, ACoS, CDC, NAACCR, NCRA, CCCR, CPAC, and AJCC, to provide a single uniform set of codes and rules for coding extent of disease (EOD) and stage information to meet the needs of all of the participating standard setters. When CS data items are coded, a computer algorithm provides the derivation of T, N, M, and stage-based on AJCC Cancer Staging Manual 6th & 7th Editions, SEER Summary Stage 1977, and SEER Summary Stage 2000. There are separate derived CS fields in the NAACCR record based on AJCC 6th Edition for 2004+ cases and AJCC 7th Edition for 2010+ cases.
Codes (See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org/cstage/manuals.html),13 for rules and site-specific codes and coding structures.)
DERIVED AJCC-6 N
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
29602AJCC2003101106 - 1107
Alternate Name:Derived 6 N Descriptor Storage Code
Derived AJCC N
XML NAACCR ID:
XML PARENT ELEMENT:
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 (http://cancerstaging.org/cstage/manuals.html).13 The display code should be used for display on the screen and in reports.
Rationale
The Collaborative Stage Data Collection System was designed by a joint task force including representatives from SEER, ACoS, CDC, NAACCR, NCRA, CCCR, CPAC, and AJCC, to provide a single uniform set of codes and rules for coding extent of disease (EOD) and stage information to meet the needs of all of the participating standard setters. When CS data items are coded, a computer algorithm provides the derivation of T, N, M, and stage-based on AJCC Cancer Staging Manual 6th & 7th Editions, SEER Summary Stage 1977, and SEER Summary Stage 2000. There are separate derived CS fields in the NAACCR record based on AJCC 6th Edition for 2004+ cases and AJCC 7th Edition for 2010+ cases.
Codes (See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org/cstage/manuals.html),13 for rules and site-specific codes and coding structures.)
DERIVED AJCC-6 N DESCRIPT
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
29701AJCC2003101108 - 1108
Alternate Name:Derived AJCC N Descriptor
Derived 6 N Descriptor Storage Code
XML NAACCR ID:
XML PARENT ELEMENT:
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 (http://cancerstaging.org/cstage/manuals.html).13 The display code should be used for display on the screen and in reports.
Rationale
The Collaborative Stage Data Collection System was designed by a joint task force including representatives from SEER, ACoS, CDC, NAACCR, NCRA, CCCR, CPAC, and AJCC, to provide a single uniform set of codes and rules for coding extent of disease (EOD) and stage information to meet the needs of all of the participating standard setters. When CS data items are coded, a computer algorithm provides the derivation of T, N, M, and stage-based on AJCC Cancer Staging Manual 6th & 7th Editions, SEER Summary Stage 1977, and SEER Summary Stage 2000. There are separate derived CS fields in the NAACCR record based on AJCC 6th Edition for 2004+ cases and AJCC 7th Edition for 2010+ cases.
Codes (See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org/cstage/manuals.html),13 for rules and site-specific codes and coding structures.)
DERIVED AJCC-6 STAGE GRP
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
30002AJCC2003101112 - 1113
Alternate Name:Derived 6 Stage Group Storage Code
Derived AJCC Stage Group
XML NAACCR ID:
XML PARENT ELEMENT:
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 (http://cancerstaging.org/cstage/manuals.html).13 The display code should be used for display on the screen and in reports.
Rationale
The Collaborative Stage Data Collection System was designed by a joint task force including representatives from SEER, ACoS, CDC, NAACCR, NCRA, CCCR, CPAC, and AJCC, to provide a single uniform set of codes and rules for coding extent of disease (EOD) and stage information to meet the needs of all of the participating standard setters. When CS data items are coded, a computer algorithm provides the derivation of T, N, M, and stage-based on AJCC Cancer Staging Manual 6th & 7th Editions, SEER Summary Stage 1977, and SEER Summary Stage 2000. There are separate derived CS fields in the NAACCR record based on AJCC 6th Edition for 2004+ cases and AJCC 7th Edition for 2010+ cases.
Codes (See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org/cstage/manuals.html),13 for rules and site-specific codes and coding structures.)
DERIVED AJCC-6 T
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
29402AJCC2003101103 - 1104
Alternate Name:Derived T
Derived AJCC T
XML NAACCR ID:
XML PARENT ELEMENT:
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 (http://cancerstaging.org/cstage/manuals.html).13 The display code should be used for display on the screen and in reports.
Rationale
The Collaborative Stage Data Collection System was designed by a joint task force including representatives from SEER, ACoS, CDC, NAACCR, NCRA, CCCR, CPAC, and AJCC, to provide a single uniform set of codes and rules for coding extent of disease (EOD) and stage information to meet the needs of all of the participating standard setters. When CS data items are coded, a computer algorithm provides the derivation of T, N, M, and stage-based on AJCC Cancer Staging Manual 6th & 7th Editions, SEER Summary Stage 1977, and SEER Summary Stage 2000. There are separate derived CS fields in the NAACCR record based on AJCC 6th Edition for 2004+ cases and AJCC 7th Edition for 2010+ cases.
Codes (See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org/cstage/manuals.html),13 for rules and site-specific codes and coding structures.)
DERIVED AJCC-6 T DESCRIPT
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
29501AJCC2003101105 - 1105
Alternate Name:Derived AJCC T Descriptor
Derived 6 T Descriptor Storage Code
XML NAACCR ID:
XML PARENT ELEMENT:
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 (http://cancerstaging.org/cstage/manuals.html).13 The display code should be used for display on the screen and in reports.
Rationale
The Collaborative Stage Data Collection System was designed by a joint task force including representatives from SEER, ACoS, CDC, NAACCR, NCRA, CCCR, CPAC, and AJCC, to provide a single uniform set of codes and rules for coding extent of disease (EOD) and stage information to meet the needs of all of the participating standard setters. When CS data items are coded, a computer algorithm provides the derivation of T, N, M, and stage-based on AJCC Cancer Staging Manual 6th & 7th Editions, SEER Summary Stage 1977, and SEER Summary Stage 2000. There are separate derived CS fields in the NAACCR record based on AJCC 6th Edition for 2004+ cases and AJCC 7th Edition for 2010+ cases.
Codes (See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org/cstage/manuals.html),13 for rules and site-specific codes and coding structures.)
DERIVED AJCC-7 M
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
34203AJCC2010121122 - 1124
Alternate Name:Derived 7 M Storage Code
XML NAACCR ID:
XML PARENT ELEMENT:
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 (http://cancerstaging.org/cstage/manuals.html),13 for rules and site-specific codes and coding structures.)
DERIVED AJCC-7 M DESCRIPT
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
34221AJCC2010121125 - 1125
Alternate Name:Derived 7 M Descript Storage Code
XML NAACCR ID:
XML PARENT ELEMENT:
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 (http://cancerstaging.org/cstage/manuals.html),13 for rules and site-specific codes and coding structures.)
DERIVED AJCC-7 N
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
34103AJCC2010121118 - 1120
Alternate Name:Derived 7 N Storage Code
XML NAACCR ID:
XML PARENT ELEMENT:
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 (http://cancerstaging.org/cstage/manuals.html),13 for rules and site-specific codes and coding structures.)
DERIVED AJCC-7 N DESCRIPT
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
34121AJCC2010121121 - 1121
Alternate Name:Derived 7 N Descript Storage Code
XML NAACCR ID:
XML PARENT ELEMENT:
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 (http://cancerstaging.org/cstage/manuals.html),13 for rules and site-specific codes and coding structures.)
DERIVED AJCC-7 STAGE GRP
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
34303AJCC2010121126 - 1128
Alternate Name:Derived 7 Stage Grp Storage Code
XML NAACCR ID:
XML PARENT ELEMENT:
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 (http://cancerstaging.org/cstage/manuals.html),13 for rules and site-specific codes and coding structures.)
DERIVED AJCC-7 T
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
34003AJCC2010121114 - 1116
Alternate Name:Derived 7 T Storage Code
XML NAACCR ID:
XML PARENT ELEMENT:
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 (http://cancerstaging.org/cstage/manuals.html),13 for rules and site-specific codes and coding structures.)
DERIVED AJCC-7 T DESCRIPT
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
34021AJCC2010121117 - 1117
Alternate Name:Derived 7 T Descript Storage Code
XML NAACCR ID:
XML PARENT ELEMENT:
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 (http://cancerstaging.org/cstage/manuals.html),13 for rules and site-specific codes and coding structures.)
DERIVED AJCC--FLAG
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
30301AJCC2003101158 - 1158
Alternate Name:AJCC Conversion Flag
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Flag to indicate whether the derived AJCC stage was derived from CS or EOD codes.
Codes
blankNot derived
1AJCC fields derived from Collaborative Stage
2AJCC fields derived from EOD (prior to 2004)
DERIVED NEOADJUV RX FLAG
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
36001AJCC2010121157 - 1157
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
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 (http://cancerstaging.org/cstage/manuals.html),13 for rules and site-specific codes and coding structures.)
0Neoadjuvant therapy was not administered as part of the first course of therapy
1Neoadjuvant therapy was administered as part of the first course of therapy
9Unknown
This data item will record whether neoadjuvant therapy was administered. This will be a derived field based on RX SUMM--SYTEMIC/SUR SEQ [1639] & RX SUMM--SURG/RAD SEQ [1380].

Comments:

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

DERIVED POSTRX-7 M
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
34902AJCC2010121150 - 1151
Alternate Name:Derived PostRX 7 M Storage Code
XML NAACCR ID:
XML PARENT ELEMENT:
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 (http://cancerstaging.org/cstage/manuals.html).13

The display code should be used for display on the screen and in reports.The implementation of this data item has been deferred indefinitely.
Rationale
The Collaborative Stage Data Collection System was designed by a joint task force including representatives from SEER, ACoS, CDC, NAACCR, NCRA, CCCR, CPAC, and AJCC, to provide a single uniform set of codes and rules for coding extent of disease (EOD) and stage information to meet the needs of all of the participating standard setters. When CS data items are coded, a computer algorithm provides the derivation of T, N, M, and stage-based on AJCC Cancer Staging Manual 6th & 7th Editions, SEER Summary Stage 1977, and SEER Summary Stage 2000. There are separate derived CS fields in the NAACCR record based on AJCC 6th Edition for 2004+ cases and AJCC 7th Edition for 2010+ cases.
Codes (See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org/cstage/manuals.html),13 for rules and site-specific codes and coding structures.)
DERIVED POSTRX-7 N
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
34823AJCC2010121147 - 1149
Alternate Name:Derived PostRX 7 N Storage Code
XML NAACCR ID:
XML PARENT ELEMENT:
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 (http://cancerstaging.org/cstage/manuals.html).13

The display code should be used for display on the screen and in reports.The implementation of this data item has been deferred indefinitely.
Rationale
The Collaborative Stage Data Collection System was designed by a joint task force including representatives from SEER, ACoS, CDC, NAACCR, NCRA, CCCR, CPAC, and AJCC, to provide a single uniform set of codes and rules for coding extent of disease (EOD) and stage information to meet the needs of all of the participating standard setters. When CS data items are coded, a computer algorithm provides the derivation of T, N, M, and stage-based on AJCC Cancer Staging Manual 6th & 7th Editions, SEER Summary Stage 1977, and SEER Summary Stage 2000. There are separate derived CS fields in the NAACCR record based on AJCC 6th Edition for 2004+ cases and AJCC 7th Edition for 2010+ cases.
Codes (See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org/cstage/manuals.html),13 for rules and site-specific codes and coding structures.)
DERIVED POSTRX-7 STGE GRP
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
34923AJCC2010121152 - 1154
Alternate Name:Derived PostRX 7 Stge Grp Storage Code
XML NAACCR ID:
XML PARENT ELEMENT:
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 (http://cancerstaging.org/cstage/manuals.html).13

The display code should be used for display on the screen and in reports. The implementation of this data item has been deferred indefinitely.
Rationale
The Collaborative Stage Data Collection System was designed by a joint task force including representatives from SEER, ACoS, CDC, NAACCR, NCRA, CCCR, CPAC, and AJCC, to provide a single uniform set of codes and rules for coding extent of disease (EOD) and stage information to meet the needs of all of the participating standard setters. When CS data items are coded, a computer algorithm provides the derivation of T, N, M, and stage-based on AJCC Cancer Staging Manual 6th & 7th Editions, SEER Summary Stage 1977, and SEER Summary Stage 2000. There are separate derived CS fields in the NAACCR record based on AJCC 6th Edition for 2004+ cases and AJCC 7th Edition for 2010+ cases.
Codes (See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org/cstage/manuals.html),13 for rules and site-specific codes and coding structures.)
DERIVED POSTRX-7 T
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
34803AJCC2010121144 - 1146
Alternate Name:Derived PostRX 7 T Storage Code
XML NAACCR ID:
XML PARENT ELEMENT:
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 (http://cancerstaging.org/cstage/manuals.html).13

The display code should be used for display on the screen and in reports.The implementation of this data item has been deferred indefinitely.
Rationale
The Collaborative Stage Data Collection System was designed by a joint task force including representatives from SEER, ACoS, CDC, NAACCR, NCRA, CCCR, CPAC, and AJCC, to provide a single uniform set of codes and rules for coding extent of disease (EOD) and stage information to meet the needs of all of the participating standard setters. When CS data items are coded, a computer algorithm provides the derivation of T, N, M, and stage-based on AJCC Cancer Staging Manual 6th & 7th Editions, SEER Summary Stage 1977, and SEER Summary Stage 2000. There are separate derived CS fields in the NAACCR record based on AJCC 6th Edition for 2004+ cases and AJCC 7th Edition for 2010+ cases.
Codes (See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org/cstage/manuals.html),13 for rules and site-specific codes and coding structures.)
DERIVED PRERX-7 M
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
34603AJCC2010121137 - 1139
Alternate Name:Derived PreRX 7 M Storage Code
XML NAACCR ID:
XML PARENT ELEMENT:
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 (http://cancerstaging.org/cstage/manuals.html).13

The display code should be used for display on the screen and in reports. The implementation of this data item has been deferred indefinitely.
Rationale
The Collaborative Stage Data Collection System was designed by a joint task force including representatives from SEER, ACoS, CDC, NAACCR, NCRA, CCCR, CPAC, and AJCC, to provide a single uniform set of codes and rules for coding extent of disease (EOD) and stage information to meet the needs of all of the participating standard setters. When CS data items are coded, a computer algorithm provides the derivation of T, N, M, and stage-based on AJCC Cancer Staging Manual 6th & 7th Editions, SEER Summary Stage 1977, and SEER Summary Stage 2000. There are separate derived CS fields in the NAACCR record based on AJCC 6th Edition for 2004+ cases and AJCC 7th Edition for 2010+ cases.
Codes (See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org/cstage/manuals.html),13 for rules and site-specific codes and coding structures.)
DERIVED PRERX-7 M DESCRIP
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
34621AJCC2010121140 - 1140
Alternate Name:Derived PreRX 7 M Descrip Storage Code
XML NAACCR ID:
XML PARENT ELEMENT:
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 (http://cancerstaging.org/cstage/manuals.html).13

The display code should be used for display on the screen and in reports. The implementation of this data item has been deferred indefinitely.
Rationale
The Collaborative Stage Data Collection System was designed by a joint task force including representatives from SEER, ACoS, CDC, NAACCR, NCRA, CCCR, CPAC, and AJCC, to provide a single uniform set of codes and rules for coding extent of disease (EOD) and stage information to meet the needs of all of the participating standard setters. When CS data items are coded, a computer algorithm provides the derivation of T, N, M, and stage-based on AJCC Cancer Staging Manual 6th & 7th Editions, SEER Summary Stage 1977, and SEER Summary Stage 2000. There are separate derived CS fields in the NAACCR record based on AJCC 6th Edition for 2004+ cases and AJCC 7th Edition for 2010+ cases.
Codes (See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org/cstage/manuals.html),13 for rules and site-specific codes and coding structures.)
DERIVED PRERX-7 N
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
34503AJCC2010121133 - 1135
Alternate Name:Derived PreRX 7 N Storage Code
XML NAACCR ID:
XML PARENT ELEMENT:
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 (http://cancerstaging.org/cstage/manuals.html).13

The display code should be used for display on the screen and in reports. The implementation of this data item has been deferred indefinitely.
Rationale
The Collaborative Stage Data Collection System was designed by a joint task force including representatives from SEER, ACoS, CDC, NAACCR, NCRA, CCCR, CPAC, and AJCC, to provide a single uniform set of codes and rules for coding extent of disease (EOD) and stage information to meet the needs of all of the participating standard setters. When CS data items are coded, a computer algorithm provides the derivation of T, N, M, and stage-based on AJCC Cancer Staging Manual 6th & 7th Editions, SEER Summary Stage 1977, and SEER Summary Stage 2000. There are separate derived CS fields in the NAACCR record based on AJCC 6th Edition for 2004+ cases and AJCC 7th Edition for 2010+ cases.
Codes (See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org/cstage/manuals.html),13 for rules and site-specific codes and coding structures.)
DERIVED PRERX-7 N DESCRIP
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
34521AJCC2010121136 - 1136
Alternate Name:Derived PreRX 7 N Descrip Storage Code
XML NAACCR ID:
XML PARENT ELEMENT:
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 (http://cancerstaging.org/cstage/manuals.html).13

The display code should be used for display on the screen and in reports. The implementation of this data item has been deferred indefinitely.
Rationale
The Collaborative Stage Data Collection System was designed by a joint task force including representatives from SEER, ACoS, CDC, NAACCR, NCRA, CCCR, CPAC, and AJCC, to provide a single uniform set of codes and rules for coding extent of disease (EOD) and stage information to meet the needs of all of the participating standard setters. When CS data items are coded, a computer algorithm provides the derivation of T, N, M, and stage-based on AJCC Cancer Staging Manual 6th & 7th Editions, SEER Summary Stage 1977, and SEER Summary Stage 2000. There are separate derived CS fields in the NAACCR record based on AJCC 6th Edition for 2004+ cases and AJCC 7th Edition for 2010+ cases.
Codes (See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org/cstage/manuals.html),13 for rules and site-specific codes and coding structures.)
DERIVED PRERX-7 STAGE GRP
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
34703AJCC2010121141 - 1143
Alternate Name:Derived PreRX 7 Stge Grp Storage Code
XML NAACCR ID:
XML PARENT ELEMENT:
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 (http://cancerstaging.org/cstage/manuals.html).13

The display code should be used for display on the screen and in reports. The implementation of this data item has been deferred indefinitely.
Rationale
The Collaborative Stage Data Collection System was designed by a joint task force including representatives from SEER, ACoS, CDC, NAACCR, NCRA, CCCR, CPAC, and AJCC, to provide a single uniform set of codes and rules for coding extent of disease (EOD) and stage information to meet the needs of all of the participating standard setters. When CS data items are coded, a computer algorithm provides the derivation of T, N, M, and stage-based on AJCC Cancer Staging Manual 6th & 7th Editions, SEER Summary Stage 1977, and SEER Summary Stage 2000. There are separate derived CS fields in the NAACCR record based on AJCC 6th Edition for 2004+ cases and AJCC 7th Edition for 2010+ cases.
Codes (See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org/cstage/manuals.html),13 for rules and site-specific codes and coding structures.)
DERIVED PRERX-7 T
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
34403AJCC2010121129 - 1131
Alternate Name:Derived PreRX 7 T Storage Code
XML NAACCR ID:
XML PARENT ELEMENT:
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 (http://cancerstaging.org/cstage/manuals.html).13

The display code should be used for display on the screen and in reports. The implementation of this data item has been deferred indefinitely.
Rationale
The Collaborative Stage Data Collection System was designed by a joint task force including representatives from SEER, ACoS, CDC, NAACCR, NCRA, CCCR, CPAC, and AJCC, to provide a single uniform set of codes and rules for coding extent of disease (EOD) and stage information to meet the needs of all of the participating standard setters. When CS data items are coded, a computer algorithm provides the derivation of T, N, M, and stage-based on AJCC Cancer Staging Manual 6th & 7th Editions, SEER Summary Stage 1977, and SEER Summary Stage 2000. There are separate derived CS fields in the NAACCR record based on AJCC 6th Edition for 2004+ cases and AJCC 7th Edition for 2010+ cases.
Codes (See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org/cstage/manuals.html),13 for rules and site-specific codes and coding structures.)
DERIVED PRERX-7 T DESCRIP
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
34421AJCC2010121132 - 1132
Alternate Name:Derived PreRX 7 T Descrip Storage Code
XML NAACCR ID:
XML PARENT ELEMENT:
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 (http://cancerstaging.org/cstage/manuals.html).13

The display code should be used for display on the screen and in reports. The implementation of this data item has been deferred indefinitely.
Rationale
The Collaborative Stage Data Collection System was designed by a joint task force including representatives from SEER, ACoS, CDC, NAACCR, NCRA, CCCR, CPAC, and AJCC, to provide a single uniform set of codes and rules for coding extent of disease (EOD) and stage information to meet the needs of all of the participating standard setters. When CS data items are coded, a computer algorithm provides the derivation of T, N, M, and stage-based on AJCC Cancer Staging Manual 6th & 7th Editions, SEER Summary Stage 1977, and SEER Summary Stage 2000. There are separate derived CS fields in the NAACCR record based on AJCC 6th Edition for 2004+ cases and AJCC 7th Edition for 2010+ cases.
Codes (See the most current version of the Collaborative Stage Data Collection System (http://cancerstaging.org/cstage/manuals.html),13 for rules and site-specific codes and coding structures.)
DERIVED SEER CLIN STG GRPNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
36105SEER201616858 - 862
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
This data item is needed to store the results of the derived algorithmic calculation of Derived SEER Clinical Stage Group.
Rationale
The SEER Program is developing an algorithm to calculate clinical and pathologic stage group based on their T, N, and M components and additional information as needed to calculate stage. For example, for thyroid, additional information is needed on histology and age to calculate stage. Once the T, N, and M are known an algorithm can assign the stage group instead of a registrar having to look up the stage. There are also provisions for a separate field for directly assigned stage group if the registrar prefers entering it.
  Codes
0Stage 0
0AStage 0A
01SStage 0is
1Stage I
1AStage IA
1A1Stage IA1
1A2Stage IA2
1BStage IB
1B1Stage IB1
1CStage IC
1SStage IS
2Stage 2
2AStage 2A
2A1Stage 2A1
2A2Stage 2A2
2BStage 2B
2CStage 2C
3Stage 3
3AStage 3A
3BStage 3B
3CStage 3C
3C1Stage 3C1
3C2Stage 3C2
4Stage 4
4AStage 4A
4A1Stage 4A1
4A2Stage 4A2
4BStage 4B
4CStage 4C
OCStage OC
88Not applicable
99Unknown
BlankThe algorithm has not been run
DERIVED SEER CMB M SRCNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
36261SEER201616885 - 885
Alternate Name:Derived SEER Combined M Source
XML NAACCR ID:
XML PARENT ELEMENT:
Description
This item is needed to store the results of the source information selected for the derived algorithmic calculation of Derived SEER Combined M [3620].
Codes
1Clinical
2Pathologic
3Clinical and pathologic information used
9Unknown
DERIVED SEER CMB N SRCNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
36241SEER201616884 - 884
Alternate Name:Derived SEER Combined N Source
XML NAACCR ID:
XML PARENT ELEMENT:
Description
This item is needed to store the results of the source information selected for the derived algorithmic calculation of Derived SEER Combined N [3618].
Codes
1Clinical
2Pathologic
3Clinical and pathologic information used
9Unknown
DERIVED SEER CMB STG GRPNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
36145SEER201616863 - 867
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
This data item is needed to store the results of the derived algorithmic calculation of Derived SEER Clinical Stage Group.
Rationale
Rationale for change proposal (potential benefits of change): The SEER Program is developing an algorithm to calculate clinical and pathologic stage group based on their T, N, and M components and additional information as needed to calculate stage. For example, for thyroid, additional information is needed on histology and age to calculate stage. Once the T, N, and M are known an algorithm can assign the stage group instead of a registrar having to look up the stage. There are also provisions for a separate field for directly assigned stage group if the registrar prefers entering it.
Codes
0AStage 0
0ISStage 0is
1Stage I
1AStage IA
1A2Stage IA2
1BStage IB
1B1Stage IB1
1B2Stage IB2
1CStage IC
1SStage IS
2Stage 2
2AStage 2A
2A1Stage
2A2Stage IIA2
2BStage IIB
2CStage IIC
3Stage III
3AStage IIIA
3BStage IIIB
3CStage IIIC
3C1Stage IIIC1
3C2Stage IIIC2
4Stage IV
4AStage IVA
4A1Stage IVA1
4A2Stage IV42
4BStage IVB
4CStage IV4C
OCOccult
88Not applicable
99Unknown
BlankThe algorithm has not been run
DERIVED SEER CMB T SRCNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
36221SEER201616883 - 883
Alternate Name:Derived SEER Combined T Source
XML NAACCR ID:
XML PARENT ELEMENT:
Description
This item is needed to store the results of the source information selected for the derived algorithmic calculation of Derived SEER Combined T [3616].
Codes
1Clinical
2Pathologic
3Clinical and pathologic information used
9Unknown
DERIVED SEER COMBINED MNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
36205SEER201616878 - 882
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
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 FORDS manual)
88Not applicable
BlankNot derived
DERIVED SEER COMBINED NNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
36185SEER201616873 - 877
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
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 FORDS manual)
88Not applicable
BlankNot derived
DERIVED SEER COMBINED TNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
36165SEER868 - 872
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
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 FORDS manual)
88Not applicable
BlankNot derived
DERIVED SEER PATH STG GRPNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
36055SEER853 - 857
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
This data item is needed to store the results of the derived algorithmic calculation of Derived SEER Pathologic Stage Group.
Rationale
The SEER Program is developing an algorithm to calculate clinical and pathologic stage group based on their T, N, and M components and additional information as needed to calculate stage. For example, for thyroid, additional information is needed on histology and age to calculate stage. Once the T, N, and M are known an algorithm can assign the stage group instead of a registrar having to look up the stage. There are also provisions for a separate field for directly assigned stage group if the registrar prefers entering it.
Codes
0Stage 0
0AStage 0A
0ISStage 0is
1Stage I
1AStage IA
1A1Stage IA1
1A2Stage IA2
1BStage IB
1B1Stage IB1
1B2Stage IB2
1CStage IC
1SStage IS
2Stage II
2AStage IIA
2A1Stage IIA1
2A2Stage IIA2
2BStage IIB
2CStage IIC
3Stage III
3AStage IIIA
3BStage IIIB
3CStage IIIC
3C1Stage IIIC1
3C2Stage IIIC2
4Stage IV
4AStage IVA
4A1Stage IVA1
4A2Stage IVA2
4BStage IVB
4CStage IVC
OCOccult
88Not applicable
99Unknown
BlankAlgorithm has not been run
DERIVED SS1977
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
30101AJCC2003101155 - 1155
Alternate Name:Derived SEER Summary Stage 1977
XML NAACCR ID:
XML PARENT ELEMENT:
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 (http://cancerstaging.org/cstage/manuals.html),13 for rules and site-specific codes and coding structures.)
DERIVED SS1977--FLAG
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
30401AJCC2003101159 - 1159
Alternate Name:SS1977 Conversion Flag
XML NAACCR ID:
XML PARENT ELEMENT:
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 (http://cancerstaging.org/cstage/manuals.html),13 for rules and site-specific codes and coding structures.)
BlankNot derived
1SS1977 derived from Collaborative Stage
2SS1977 derived from EOD (prior to 2004)
DERIVED SS2000
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
30201AJCC2003101156 - 1156
Alternate Name:Derived SEER Summary Stage 2000
XML NAACCR ID:
XML PARENT ELEMENT:
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 (http://cancerstaging.org/cstage/manuals.html),13 for rules and site-specific codes and coding structures.)
DERIVED SS2000--FLAG
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
30501AJCC2003101160 - 1160
Alternate Name:SS2000 Conversion Flag
XML NAACCR ID:
XML PARENT ELEMENT:
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 (http://cancerstaging.org/cstage/manuals.html),13 for rules and site-specific codes and coding structures.)
1SS2000 derived from Collaborative Stage
2SS2000 derived from EOD (prior to 2004)
BlankNot derived
DERIVED SS2017New
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
7621SEER201616894 - 894
Alternate Name:Derived Summary Stage 2017
XML NAACCR ID:
XML PARENT ELEMENT:
Description
These two new items are needed to store the results of a 2017 version of Summary Stage (SS) based on a computer algorithm, Derived SEER SS2017 [762], and to allow for the direct assignment of this variable, Directly Assigned SEER SS2017 [764].
Rationale
The SEER program has collected staging information on cases since its inception in 1973. For many cancer sites, the different versions of AJCC stage over time have made the analyses of long term trends in stage very difficult. Therefore, for long-term staging trends, SEER has relied on a more simplified summary stage. When Collaborative Stage (CS) information is no longer available, SEER will need to derive summary stage via computer algorithm based on T, N, or M (clinical, pathologic, Derived SEER combined) or SEER Primary Tumor, SEER Regional Nodes, and SEER Mets and other information as needed. The SEER Derived SS2017 criteria may be applied to earlier CS and EOD data for cases prior to 2017. The SEER Directly Assigned SS2017 data item is provided for those wishing to collect summary stage but who aren’t collecting all of the fields needed by the computer algorithm to derive SS2017.
Codes
0In situ
1Localized
2Regional, direct extension only
3Regional, regional lymph nodes only
4Regional, direct extension and regional lymph nodes
5Regional, NOS
7Distant
8Not applicable
9Unstaged
DIAGNOSTIC CONFIRMATION
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
4901SEER/CoC562 - 562
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Code for the best method of diagnostic confirmation of the cancer being reported at any time in the patient’s history.
Rationale
Diagnostic confirmation is useful to calculate rates based on microscopically confirmed cancers. Full incidence calculations must also include tumors that are only confirmed clinically. The percentage of tumors that not micropscopically confirmed is an indication of whether case finding is including sources outside of pathology reports.
Codes
1Positive histology
2Positive cytology
3Positive histology PLUS - positive immunophenotyping AND/OR positive genetic studies (Used only for hematopoietic and lymphoid neoplasms M-9590/3-9992/3)
4Positive microscopic confirmation, method not specified
5Positive laboratory test/marker study
6Direct visualization without microscopic confirmation
7Radiography and/or other imaging techniques without microscopic confirmation
8Clinical diagnosis only (other than 5, 6, or 7)
9Unknown whether or not microscopically confirmed; death certificate only
Note: Code 3 (used only for hematopoietic and lymphoid neoplasms M-9590/3-9992/3) was adopted for use effective with 2010 diagnoses.
DIAGNOSTIC PROC 73-87
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
22002SEER199551949 - 1950
Alternate Name:Diagnostic Procedures (1973-87 SEER)
XML NAACCR ID:
XML PARENT ELEMENT:
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.
DIRECTLY ASSIGNED SS2017New
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
7641SEER895 - 895
Alternate Name:Directly Assigned Summary Stage 2017
XML NAACCR ID:
XML PARENT ELEMENT:
Description
These two new items are needed to store the results of a 2017 version of Summary Stage (SS) based on a computer algorithm, Derived SEER SS2017 [762], and to allow for the direct assignment of this variable, Directly Assigned SEER SS2017 [764].
Rationale
The SEER program has collected staging information on cases since its inception in 1973. For many cancer sites, the different versions of AJCC stage over time have made the analyses of long term trends in stage very difficult. Therefore, for long-term staging trends, SEER has relied on a more simplified summary stage. When Collaborative Stage (CS) information is no longer available, SEER will need to derive summary stage via computer algorithm based on T, N, or M (clinical, pathologic, Derived SEER combined) or SEER Primary Tumor, SEER Regional Nodes, and SEER Mets and other information as needed. The SEER Derived SS2017 criteria may be applied to earlier CS and EOD data for cases prior to 2017. The SEER Directly Assigned SS2017 data item is provided for those wishing to collect summary stage but who aren’t collecting all of the fields needed by the computer algorithm to derive SS2017.
Codes
0In situ
1Localized
2Regional, direct extension only
3regional, regional lymph nodes only
4Regional, direct extension and regional lymph nodes
5Regional, NOS
7Distant
8Not applicable
9Unstaged
EOD--EXTENSION
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
7902SEER909 - 910
Alternate Name:Extension (SEER EOD) (96 CoC)
Extension (pre-96 SEER/CoC)
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Part of the 10-digit EOD [779]. Detailed site-specific codes for anatomic EOD used by SEER for tumors diagnosed from January 1, 1988, through December 31, 2003.

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

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

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

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

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

EXTENT OF DISEASE 10-DIG
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
77912906 - 917
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
The name for a group of subfields that contain detailed site-specific codes for the anatomic EOD. SEER uses the subfields for tumors diagnosed from January 1, 1988, through December 31, 2003.

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

Subfields

EOD--Tumor Size [780]
EOD--Extension [790]
EOD--Extension Prost Path [800]
EOD--Lymph Node Involv [810]
Regional Nodes Positive [820]
Regional Nodes Examined [830]
FOLLOWING REGISTRY
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
244010CoC4295 - 4304
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Records the FIN of the registry responsible for following the patient.
Rationale
The number is essential to NCDB for monitoring data submissions, ensuring the accuracy of data, and identifying areas for special studies.
 
Instructions for Coding
CoC maintains the codes, including those for non-hospital sources of reporting.

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

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

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

Canadian addresses should conform to the Canada Postal Guide. The current Canadian Postal Address standards may be found at the following website: http://www.canadapost.ca.
Rationale
Sometimes registries carry out follow-up by contacting the patient and other contacts by a letter or phone call to ascertain their vital status. When a patient's current address is unknown or the patient is for some reason not to be contacted (e.g., patient is a minor child), the most current name, address and phone number of another contact, such as a relative or neighbor are needed. This information may also be useful for conducting research studies.
Note: Prior to Version 5, Follow-Up Contact fields may have been used for patient current address in the NAACCR record layout.
FOLLOW-UP CONTACT--POSTAL
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
18469SEER19975.12260 - 2268
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Postal code for the address of the follow-up contact’s current usual residence. If the patient has multiple tumors, the Follow-up Contact-Postal should be the same for all tumors. For U.S. residents, use either the 5-digit or the extended 9-digit ZIP code. Blanks follow the 5-digit code. For Canadian residents, use the 6-character, alphanumeric postal code. Blanks follow the 6-character code. When available, enter postal code for other countries.
Rationale
Sometimes registries carry out follow-up by contacting the patient and other contacts by a letter or phone call to ascertain their vital status. When a patient's current address is unknown or the patient is for some reason not to be contacted (e.g., patient is a minor child), the most current name, address and phone number of another contact, such as a relative or neighbor are needed. This information may also be useful for conducting research studies.
Codes (in addition to U.S., Canadian, and foreign postal codes)
888888888Resident of country other than the United States (including its possessions, etc.) or Canada, and postal code unknown
999999999Resident of the United States (including its possessions, etc.) or Canada, and postal code unknown
FOLLOW-UP CONTACT--STATE
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
18442SEER19975.12258 - 2259
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
USPS abbreviation for the state (including U.S. territories, commonwealths, or possessions), or Canada Post abbreviation for the Canadian province/territory of the follow-up contact’s current usual residence. If the patient has multiple tumors, the follow-up contact state should be the same for all tumors. Effective with NAACCR Volume II, Version 13, a new data item, FollowUp Contact--Country [1847] was added to the standard transmission record layout. The UDS Committee expects the new item to supplement the use of Follow-Up Contact--State [1844].
Rationale
Sometimes registries carry out follow-up by contacting the patient and other contacts by a letter or phone call to ascertain their vital status. When a patient's current address is unknown or the patient is for some reason not to be contacted (e.g., patient is a minor child), the most current name, address and phone number of another contact, such as a relative or neighbor are needed. This information may also be useful for conducting research studies.
Codes (in addition to USPS and Canadian Postal Service abbreviations)
CDResident of Canada, NOS (province/territory unknown)
USResident of United States, NOS (state/commonwealth/territory/possession unknown)
XXResident of country other than the United States (including its territories, commonwealths, or possessions) or Canada, and country is known
YYResident of country other than the United States (including its territories, commonwealths, or possessions) or Canada, and country is unknown
ZZResidence unknown
FOLLOW-UP CONTACT--SUPPL
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
239360SEER2003104004 - 4063
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
This data item provides the ability to store additional address information such as the name of a place or facility, a nursing home, or the name of an apartment complex. It can be used to generate a follow-up inquiry, and must correspond to the other fields in the follow-up contact address. If the patient has multiple tumors, Follow-Up Contact--Suppl should be the same for all tumors.
Rationale
Sometimes registries carry out follow-up by contacting the patient and other contacts by a letter or phone call to ascertain their vital status. When a patient's current address is unknown or the patient is for some reason not to be contacted (e.g., patient is a minor child), the most current name, address and phone number of another contact, such as a relative or neighbor are needed. This information may also be useful for conducting research studies.
FOLLOW-UP SOURCE
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
17901CoC2129 - 2129
Alternate Name:Follow-Up Method (pre-96 CoC)
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Records the source from which the latest follow-up information was obtained.
Rationale
For registries performing follow-up, this field helps evaluate the success rates of various methods of follow-up. It also can be used to report to institutions the source of follow-up information that is sent to them. When there is a conflict in follow-up information, knowing the source can help resolve the inconsistency.
Codes
0Reported hospitalization
1Readmission
2Physician
3Patient
4Department of Motor Vehicles
5Medicare/Medicaid file
7Death certificate
8Other
9Unknown, not stated in patient record
FOLLOW-UP SOURCE CENTRAL
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
17912NAACCR2006112278 - 2279
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
This field is created by the central registry. It records the source from which the consolidated information was obtained on a patient's vital status and date of last contact. Follow-up Source Central would be updated when new or more reliable information becomes available. However, when the existing date of last contact/vital status is deemed to be more reliable than newly obtained information, then neither the date of last contact/vital status nor the follow-up source central would be changed.
Rationale
For central registries performing follow-up, this field could help evaluate the success rates of various methods of follow-up. When new follow-up information conflicts with the existing information, knowing the follow-up source can help resolve any discrepancies.
 Codes
00Follow-up not performed for this patient
(01-29)File Linkages
01Medicare/Medicaid File
02Center for Medicare and Medicaid Services (CMS, formerly HCFA)
03Department of Motor Vehicle Registration
04National Death Index (NDI)
05State Death Tape/Death Certificate File
06County/Municipality Death Tape/ Death Certificate File
07Social Security Administration Death Master File
08Hospital Discharge Data
09Health Maintenance Organization (HMO) file
10Social Security Epidemiological Vital Status Data
11Voter Registration File
12Research/Study Related Linkage
29Linkages, NOS
(30-39)Hospitals and Treatment Facilities
30Hospital in-patient/outpatient
31Casefinding
32Hospital cancer registry
33Radiation treatment center
34Oncology clinic
35Ambulatory surgical center
39Clinic/facility, NOS
(40-49)Physicians
40Attending physician
41Medical oncologist
42Radiation oncologist
43Surgeon
48Other specialist
49Physician, NOS
(50-59)Patient
50Patient contact
51Relative contact
59Patient, NOS
(60-98)Other
60Central or Regional cancer registry
61Internet sources
62Hospice
63Nursing homes
64Obituary
65Other research/study related sources
98Other, NOS
99Unknown source
GIS COORDINATE QUALITY
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
3662NAACCR36611422 - 423
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Code indicating the basis of assignment of latitude and longitude coordinates for an individual record from an address. This data item is helpful in identifying cases that were assigned coordinates based on incomplete information, post office boxes, or rural routes. This item is coded at the central registry, not by the reporting facility. Most of the time, this information is provided by geocoding software. Alternatively, a central registry staff member manually assigns the code. Codes are hierarchical, with lower numbers having priority.
Rationale
Spatial analysis of cancer data often requires identifying data records with a high degree of geographic precision. Researchers can use this code as a basis for selecting records with a degree of precision that is appropriate to the study.
Codes
00Coordinates derived from local government-maintained address points, which are based on property parcel locations, not interpolation over a street segment's address range
01Coordinates assigned by Global Positioning System (GPS)
02Coordinates are match of house number and street, and based on property parcel location
03Coordinates are match of house number and street, interpolated over the matching street segment's address range
04Coordinates are street intersections
05Coordinates are at mid-point of street segment (missing or invalid building number)
06Coordinates are address ZIP code+4 centroid
07Coordinates are address ZIP code+2 centroid
08Coordinates were obtained manually by looking up a location on a paper or electronic map
09Coordinates are address 5-digit ZIP code centroid
10Coordinates are point ZIP code of Post Office Box or Rural Route
11Coordinates are centroid of address city (when address ZIP code is unknown or invalid, and there are multiple ZIP codes for the city)
12Coordinates are centroid of county
98Latitude and longitude are assigned, but coordinate quality is unknown
99Latitude and longitude are not assigned, but geocoding was attempted; unable to assign coordinates based on available information
BlankGIS Coordinate Quality not coded
Instructions for Coding: Where multiple codes are applicable, use the lower code value. Note: This data item is similar in function to Census Tract Certainty 1970/80/90 [364] and Census Tract Certainty 2000 [365]. The codes for this data item and the two census tract data items all describe how location information was assigned based on the patient's resident address at the time of diagnosis.

This data item must be populated if Latitude [2352] and Longitude [2354] are also populated.
GRADE
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
4401SEER/CoC555 - 555
Alternate Name:Grade, Differentiation, or Cell Lineage Indicator (SEER/CCCR)
Grade/Differentiation (CoC)
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Code for the grade or degree of differentiation of the reportable tumor. For lymphomas and leukemias, field also is used to indicate T-, B-, Null-, or NK-cell origin.

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

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

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

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

 

GRADE PATH SYSTEM
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
4491AJCC201012557 - 557
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Indicates whether a two, three or four grade system is used.
Rationale
This item is used to show whether a two, three or four grade system is used. This is the grade system stated in the path report; it is not converted. This item is used in conjunction with Grade Path Value [441] and is abstracted in addition to Grade Differentiation [440].
Codes (Refer to the most recent version of FORDS for additional instructions.)
2Two-Grade System
3Three-Grade System
4Four-Grade System
BlankNot a two, three or four grade system; unknown
GRADE PATH VALUE
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
4411AJCC201012556 - 556
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Describes the actual grade according to the grading system in Grade Path System [449].
Rationale
This data item will record grade specified in Grade Path System. This does not replace Grade [440].
Codes (Refer to the most recent version of FORDS for additional instructions.)
1Recorded as Grade I or 1
2Recorded as Grade II or 2
3Recorded as Grade III or 3
4Recorded as Grade IV or 4
BlankNo Two, Three or Four System Grade is available; unknown
HISTOLOGIC TYPE ICD-O-3
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
5224SEER/CoC20019550 - 553
Alternate Name:ICD-O-3 Histology (CCCR)
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Codes for the histologic type of the tumor being reported using ICD-O-3. NAACCR adopted ICD-O-3 as the standard coding system for tumors diagnosed in 2001 and later, and recommended that prior tumors be converted from ICD-O-2. Effective with 2010 diagnoses, this item also includes histology codes as per the 2008 WHO Hematopoietic/Lymphoid publication39, which are listed on pages 3-5 of the NAACCR 2010 Implementation Guidelines. http://www.naaccr.org/StandardsandRegistryOperations/ImplementationGuidelines.aspx.

Note: See Histology (92-00) ICD-O-2 [420] for ICD-O-2 codes. Effective with 2010 diagnoses, this item also includes histology codes as per the 2008 WHO Hematopoietic/Lymphoid publication 39, which are listed on pages 3-5 of the NAACCR 2010 Implementation Guidelines. http://www.naaccr.org/LinkClick.aspx?fileticket=U-3o31G2Lik%3d&tabid=126&mid=466
Codes
See ICD-O-3,14 Morphology Section and the SEER Hematopoietic database.
Clarification of Required Status
This data item 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 when conversion algorithms and tables are available) for tumors diagnosed before 2001.

When the histologic type is coded according to 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].
HISTOLOGY (73-91) ICD-O-1
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
19714SEER1913 - 1916
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Area for retaining the histology portion (4 digits) 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 1973-91. However, some states may have used the codes for cases before 1973.
Codes For cases diagnosed before 1992, contains the ICD-O-1 or field trial 4-digit histology code as originally coded, if available. Blank for tumors coded directly into ICD-O-2 or ICD-O-3 (i.e., 1992 and later cases).
HISTOLOGY (92-00) ICD-O-2
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
4204SEER/CoC545 - 548
Alternate Name:Histology (CoC)
ICD-O-2 Histology (CCCR)
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Codes for the histologic type of the tumor being reported using ICD-O-2. NAACCR adopted ICD-O-2 as the standard coding system for tumors diagnosed in 1992 and later and recommended that prior cases be converted to ICD-O-2.

Note: See Histology (73-91) ICD-O-1 [1971] for ICD-O-1 and field trial codes.

Codes See ICD-O-2,15 Morphology Section.

 

Clarification of Required Status
This data item is 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 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].
ICD REVISION COMORBID
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
31651CoC2006111185 - 1185
Alternate Name:ICD Revision Comorbidities
XML NAACCR ID:
XML PARENT ELEMENT:
Description
This item indicates the coding system in which the Comorbidities and Complications (secondary diagnoses) codes are provided.
Rationale
The CoC currently requires the collection and reporting of up to 10 ICD-9-CM codes describing secondary diagnoses for patients hospitalized for cancer treatment. Currently the use of ICD-10-CM is not mandatory in U.S. hospitals, though it may become so in the future. In the event this occurs cancer registries that maintain or collect this information will need to differentiate between ICD-9-CM and ICD-10-CM code use. The code values and definitions for this item would be expanded as necessary. Allowable codes reported in the Comorbidity and Complications items in FORDS would be re-assessed at the same time.
Codes
0No comorbidities or complications recorded in patient's record
1ICD-10-CM
9ICD-9-CM
BlankComorbidities and Complications not collected
ICD REVISION NUMBER
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
19201SEER2273 - 2273
Alternate Name:ICD Code Revision Used for Cause of Death (SEER)
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Indicator for the coding scheme used to code the cause of death.
Codes
0Patient alive at last follow-up
1ICD-10
7ICD-7
8ICDA-8
9ICD-9
ICD-O-2 CONVERSION FLAG
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
19801SEER1919 - 1919
Alternate Name:Review Flag for 1973-91 Cases (SEER)
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Code specifying how the conversion of site and morphology codes from ICD-O-1 and the field trial editions to ICD-O-2 was accomplished. The item names include years 1973-91. However, some states may have used the codes for tumors before 1973. The code also covers morphology conversions from ICD-O-3 to ICD-O-2.
Codes
0Primary site and morphology originally coded in ICD-O-2
1Primary site and morphology converted without review
2Primary site converted with review; morphology machine-converted without review
3Primary site machine-converted without review, morphology converted with review
4Primary site and morphology converted with review
5Morphology converted from ICD-O-3 without review
6Morphology converted from ICD-O-3 with review
BlankNot converted
ICD-O-3 CONVERSION FLAG
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
21161SEER/CoC200192015 - 2015
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Code specifying how the conversion of site and morphology codes from ICD-O-2 to ICD-O-3 was accomplished.
Codes
0Morphology (Morph--Type&Behav ICD-O-3 [521]) originally coded in ICD-O-3
1Morphology (Morph--Type&Behav ICD-O-3 [521]) converted from (Morph--Type&Behav ICD-O-2 [419]) without review
3Morphology (Morph--Type&Behav ICD-O-3 [521]) converted from (Morph--Type&Behav ICD-O-2 [419]) with review
BlankNot converted (clarification for cases diagnosed as of January 1, 2007: cases coded in prior ICD-O version and not converted to ICD-O-3)
IHS LINK
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
1921NPCR200611421 - 421
Alternate Name:Indian Health Service Linkage
XML NAACCR ID:
XML PARENT ELEMENT:
Description
This variable captures the results of the linkage of the registry database with the Indian Health Service patient registration database.
Rationale
The IHS linkage identifies cancer cases among American Indians who were misclassified as non-Indian in the registry database in order to improve the quality of cancer surveillance data on American Indians in individual registries and in all registries as a whole. The goal is to include cancer incidence data for American Indians in the United States Cancer Statistics by use of this variable as well as the race variable.
Codes
0Record sent for linkage, no IHS match
1Record sent for linkage, IHS match
BlankRecord not sent for linkage or linkage result pending
INDUSTRY SOURCE
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
3001NPCR216 - 216
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Code that best describes the source of industry information provided on this patient. 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).
Rationale
Industry information may come from a variety of sources. The most valid and reliable source of industry information for patients has not yet been determined.
Codes
0Unknown industry/no industry available
1Reporting facility records
2Death certificate
3Interview
7Other source
8Not applicable, patient less than 14 years of age at diagnosis
9Unknown source
BlankNot collected
INPATIENT STATUS
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
6051NAACCR201012775 - 775
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
This data item records whether there was an inpatient admission for the most definitive therapy, or in the absence of therapy, for diagnostic evaluation. This data item was first available in Volume II Version 12 (effective January 2010).
Rationale
Before Version 12 (through 2009 diagnosis), date fields included information in addition to dates. This data item incorporates the non-date meanings for the Date of Inpt Adm [590] and Date of Inpt Disch [600] in order to retain the non-date information with the transition to interoperable dates.
Codes
0Patient was never an inpatient
1Patient was inpatient
9Unknown if patient was an inpatient (only used for consolidated cases)
BlankNot collected
Comment: This is part of the initiative of the transformation from the old NAACCR date standards to interoperable dates.
INSTITUTION REFERRED FROM
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
241010CoC4315 - 4324
Alternate Name:Facility Referred From
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Identifies the facility that referred the patient to the reporting facility.
Rationale
This number is used to document and monitor referral patterns.

Instructions for Coding

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

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

For facilities with FINs greater than or equal to 10000000 that were assigned by CoC after January 1, 2001: Enter FIN codes of this type as 2 zeroes followed by the full 8-digit code. These sometimes are called CoC FIN 10-digit codes.
Note: This item is not supported by CoC as of January 1, 2010, (the respective NPI item is required).
Codes (in addition to CoC assigned codes)
0000000000Case not referred from a facility
0099999999Case referred from a facility, but facility number is unknown
INSTITUTION REFERRED TORevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
242010CoC4335 - 4344
Alternate Name:Facility Referred To
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Identifies the facility to which the patient was referred for further care.
Rationale
This number is used to document and monitor referral patterns.
 
Instructions for Coding
CoC maintains the codes, including those for non-hospital sources of reporting.

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

For facilities with FINs greater than or equal to 10000000 that were assigned by CoC after January 1, 2001: Enter FIN codes of this type as 2 zeroes followed by the full 8-digit code. These sometimes are called CoC FIN 10-digit codes.
Note: This item is not supported by CoC as of January 1, 2010, (the respective NPI item is required).
Codes (in addition to CoC assigned codes)
0000000000Case not referred to a facility
0099999999Case referred to a facility, but facility number is unknown
LATERALITY
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
4101SEER/CoC544 - 544
Alternate Name:Laterality at Diagnosis (SEER)
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Code for the side of a paired organ, or the side of the body on which the reportable tumor originated. This applies to the primary site only.
Codes
0Not a paired site
1Right: origin of primary
2Left: origin of primary
3Only one side involved, right or left origin unspecified
4Bilateral involvement at time of diagnosis, lateral origin unknown for a single primary; or both ovaries involved simultaneously, single histology; bilateral retinoblastomas; bilateral Wilms' tumors
5Paired site: midline tumor
9Paired site, but no information concerning laterality
LATITUDE
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
235210NAACCR2003104064 - 4073
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Paired with Longitude [2354], this represents the point location of the individual’s residence on the earth’s surface. It is typically determined by matching an address to a reference file or by identifying the residence using satellite imagery. This item is coded at the central registry, not by the reporting facility.
Rationale
Latitude and Longitude comprise the universal standard for designating location on the earth’s surface. Geographic Information Systems software can be used to convert these values into projected coordinates for map display.

Allowable values and format

Latitude is a 10- digit numeric field, right justified, with up to six decimal places and an explicit decimal point. The format is x12.345678, where “x” is reserved for a negative sign for locations south of the equator. Latitude north of the equator is positive. The datum of the decimal degree data shall be North American Datum of 1983 (NAD 83).

Values are in decimal degrees, not degrees/minutes/seconds.

Correct: Latitude: 41. 890833

Not this: Latitude: 41 deg 53' 27"
LONGITUDE
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
235411NAACCR2003104074 - 4084
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Paired with Latitude [2352], this represents the point location of the individual’s residence on the earth’s surface. It is typically determined by matching an address to a reference file or by identifying the residence using satellite imagery. This item is coded at the central registry, not by the reporting facility.
Rationale
Latitude and Longitude comprise the universal standard for designating location on the earth’s surface. Geographic Information Systems software can be used to convert these values into projected coordinates for map display.

Allowable values and format

Longitude is an 11 digit numeric field, right justified, with up to six decimal places and an explicit decimal point. The format is x123.456789, where “x” is reserved for a negative sign for locations west of the Prime Meridian (0 degrees) and east of 180 degrees. The datum of the decimal degree data shall be North American Datum of 1983 (NAD 83).

Values are in decimal degrees, not degrees/minutes/seconds.
Longitude: -123.128943
Longitude: -71 deg 7' 44"
LYMPH-VASCULAR INVASION
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
11821AJCC201012984 - 984
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Indicates whether lymphatic duct or blood vessel (LVI) is identified in the pathology report.
Rationale
This data item will record the information as stated in the record. Presence or absence of cancer cells in the lymphatic ducts or blood vessels is useful for prognosis.
Codes
0Lymph-vascular Invasion stated as Not Present
1Lymph-vascular Invasion Present/Identified
8Not Applicable
9Unknown/Indeterminate/not mentioned in path report
MARITAL STATUS AT DX
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
1501SEER176 - 176
Alternate Name:Marital Status at Diagnosis (SEER/CoC)
Marital Status at Initial Diagnosis (pre-96 CoC)
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Code for the patient’s marital status at the time of diagnosis for the reportable tumor. If the patient has multiple tumors, marital status may be different for each tumor.
Rationale
Incidence and survival with certain cancers vary by marital status. The item also helps in patient identification.
Codes
1Single (never married)
2Married (including common law)
3Separated
4Divorced
5Widowed
6Unmarried or Domestic Partner (same sex or opposite sex, registered or unregistered, other than common law marriage)
9Unknown
MEDICAL RECORD NUMBER
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
230011CoC3606 - 3616
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Records medical record number used by the facility to identify the patient. The CoC FORDS manual instructs registrars to record numbers assigned by the facility’s Health Information Management (HIM) Department only, not department-specific numbers.
Rationale
This number identifies the patient in a facility. It can be used by a central registry to point back to the patient record, and it helps identify multiple reports on the same patient.
Codes (in addition to the medical record number)
UNKMedical record number unknown
RTRadiation therapy department patient without HIM number
SU1-day surgery clinic patient without HIM number
Note: Other standard abbreviations may be used to indicate departments within the facility for patients without HIM numbers assigned.
METS AT DX-BONENew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
11121SEER201616838 - 838
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
This field identifies whether bone is an involved metastatic site. The six Mets at Dx-Metastatic Sites fields provide information on specific metastatic sites for data analysis.
Rationale
Information on site of metastatic disease at diagnosis has prognostic implications to survival among patients with initial late stage disease. Capturing data on where the patient’s metastatic lesions (including the number of locations) will be an important variable to include when looking at survival. Survival among metastatic patients is becoming increasingly important for cancer survivors.
Codes
0None; no bone metastases
1Yes; distant bone metastases
8Not applicable
9Unknown whether bone is an involved metastatic site. Not documented in patient record.
METS AT DX-BRAINNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
11131SEER201616839 - 839
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
This field identifies whether brain is an involved metastatic site. The six Mets at Dx-Metastatic Sites fields provide information on specific metastatic sites for data analysis.
Rationale
Information on site of metastatic disease at diagnosis has prognostic implications to survival among patients with initial late stage disease. Capturing data on where the patient’s metastatic lesions (including the number of locations) will be an important variable to include when looking at survival. Survival among metastatic patients is becoming increasingly important for cancer survivors.
Codes
0None; no brain metastses
1Yes; distant brain metastases
8Not applicable
9Unknown whether brain is involved metastatic site. Not documented in patient record.
METS AT DX-DISTANT LNNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
11141SEER201616840 - 840
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
This field identifies whether distant lymph node(s) are an involved metastatic site. The six Mets at Dx-Metastatic Sites fields provide information on specific metastatic sites for data analysis.
Rationale
Information on site of metastatic disease at diagnosis has prognostic implications to survival among patients with initial late stage disease. Capturing data on where the patient’s metastatic lesions (including the number of locations) will be an important variable to include when looking at survival. Survival among metastatic patients is becoming increasingly important for cancer survivors.
Codes
0None; no distant lymph node metastases
1Yes; distant lymph node metastases
8Not applicable
9Unknown whether distant lymph node(s) are involved metastatic site. Not documented in patient record.
METS AT DX-LIVERNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
11151SEER201616841 - 841
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
This field identifies whether liver is an involved metastatic site. The six Mets at Dx-Metastatic Sites fields provide information on specific metastatic sites for data analysis.
Rationale
Information on site of metastatic disease at diagnosis has prognostic implications to survival among patients with initial late stage disease. Capturing data on where the patient’s metastatic lesions (including the number of locations) will be an important variable to include when looking at survival. Survival among metastatic patients is becoming increasingly important for cancer survivors.
Codes
0None; no liver metastases
1Yes; distant liver metastases
8Not applicable
9Unknown whether liver is involved metastatic site. Not documented in patient record.
METS AT DX-LUNGNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
11161SEER201616842 - 842
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
This field identifies whether lung is an involved metastatic site. The six Mets at Dx-Metastatic Sites fields provide information on specific metastatic sites for data analysis.
Rationale
Information on site of metastatic disease at diagnosis has prognostic implications to survival among patients with initial late stage disease. Capturing data on where the patient’s metastatic lesions (including the number of locations) will be an important variable to include when looking at survival. Survival among metastatic patients is becoming increasingly important for cancer survivors.
Codes
0None; no lung metastases
1Yes; distant lung metastases
8Not applicable
9Unknown whether lung is involved metastatic site. Not documented in patient record.
METS AT DX-OTHERNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
11171SEER201616843 - 843
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
This field identifies whether other metastatic involvement, other than bone, brain, liver, lung or distant lymph nodes exists. Some examples include but are not limited to the adrenal gland, bone marrow, pleura, peritoneum and skin. The six Mets at Dx-Metastatic Sites fields provide information on specific metastatic sites for data analysis.
Rationale
Information on site of metastatic disease at diagnosis has prognostic implications to survival among patients with initial late stage disease. Capturing data on where the patient’s metastatic lesions (including the number of locations) will be an important variable to include when looking at survival. Survival among metastatic patients is becoming increasingly important for cancer survivors.
Codes
0None; no other metastases
1Yes; distant metastases in known site(s) other than bone, brain, liver, lung or distant lymph nodes
8Not applicable
9Unknown whether any other metastatic site. Not documented in patient record.
MILITARY RECORD NO SUFFIX
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
23102CoC3617 - 3618
Alternate Name:Military Medical Record Number Suffix (CoC)
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Patient identifier used by military hospitals to record relationship of the patient to the sponsor.
Codes
01-19Child
20Sponsor
30-39Spouse
40-44Mother
45-49Father
50-54Mother-in-law
55-59Father-in-law
60-69Other eligible dependents
98Civilian emergency (Air Force/Navy)
99Not classified elsewhere/stillborn
BlankNot a military facility
MORPH (73-91) ICD-O-1
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
197061913 - 1918
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
The name for a group of subfields describing the type and behavior of the tumor being reported using ICD-O-1 codes.

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

Subfields
Histology (73-91) ICD-O-1 [1971]
Behavior (73-91) ICD-O-1 [1972]
Grade (73-91) ICD-O-1 [1973]
MORPH CODING SYS--CURRENT
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
4701NAACCR560 - 560
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Code that best describes how morphology is currently coded. If converted, this field shows the system it is converted to.
Codes
1ICD-O, First Edition
2ICD-O, 1986 Field Trial
3ICD-O, 1988 Field Trial
4ICD-O, Second Edition
5ICD-O, Second Edition, plus REAL lymphoma codes effective 1/1/95
6ICD-O, Second Edition, plus FAB codes effective 1/1/98
7ICD-O, Third Edition
8ICD-O, Third Edition, plus 2008 WHO hematopoietic/lymphoid new terms used for conditions diagnosed 1/1/2010 and later
9Other
MORPH CODING SYS--ORIGINL
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
4801NAACCR561 - 561
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Code that best describes how morphology was originally coded. If later converted, this field shows the original codes used.
Codes
1ICD-O, First Edition
2ICD-O, 1986 Field Trial
3ICD-O, 1988 Field Trial
4ICD-O, Second Edition
5ICD-O, Second Edition, plus REAL lymphoma codes effective 1/1/95
6ICD-O, Second Edition, plus FAB codes effective 1/1/98
7ICD-O, Third Edition
8ICD-O, Third Edition, plus 2008 WHO hematopoietic/lymphoid new terms used for conditions diagnosed 1/1/2010 and later
9Other
MORPH--TYPE&BEHAV ICD-O-2
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
4195545 - 549
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
The name for a group of subfields describing the type and behavior of the tumor being reported using ICD-O-2 codes.

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

Subfields

Histology (92-00) ICD-O-2 [420]
Behavior (92-00) ICD-O-2 [430]
MORPH--TYPE&BEHAV ICD-O-3
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
521520019550 - 554
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
The name for a group of subfields describing the type and behavior of the tumor being reported using ICD-O-3 codes.

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

Subfields
Histologic Type ICD-O-3 [522]
Behavior Code ICD-O-3 [523]
MULT TUM RPT AS ONE PRIM
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
4442SEER200611577 - 578
Alternate Name:Multiple Tumors Reported as Single Primary
Type of Multiple Tumors Reported As One Primary
XML NAACCR ID:
XML PARENT ELEMENT:
Description
This data item is used to identify the type of multiple tumors in cases with multiple tumors that are abstracted and reported as a single primary using the SEER, IARC, or Canadian Cancer Registry multiple primary rules. Multiple tumors may individually exhibit in situ, invasive, or a combination of in situ and invasive behaviors. Multiple intracranial and central nervous system tumors may individually exhibit benign, borderline, malignant, or a combination of these behaviors. Multiple tumors found in the same organ or in a single primary site may occur at the time of initial diagnosis or later.
Rationale
Patients with multiple tumors that are currently reported as a single primary 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, and to compare individually reported cancer cases with historical data if the rules are changed.
Codes (refer to http://seer.cancer.gov/tools/mphrules/index.html for additional instructions).
00Single tumor
10Multiple benign
11Multiple borderline
12Benign and borderline
20Multiple in situ
30In situ and invasive
31Polyp and adenocarcinoma
32FAP with carcinoma
40Multiple invasive
80Unknown in situ or invasive
88NA
99Unknown
MULTIPLICITY COUNTER
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
4462SEER200611589 - 590
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
This data item is used to count the number of tumors (multiplicity) that are reported as a single primary, when present at the time of diagnosis or occurring later.
Rationale
Patients with multiple tumors reported as a single primary for surveillance purposes 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.
Codes (refer to http://seer.cancer.gov/tools/mphrules/index.html for additional instructions).
00No primary tumor identified
01One tumor only
02Two tumors present; bilateral ovaries involved with cystic carcinoma
03Three tumors present
..
..
88Information on multiple tumors not collected/not applicable for this site
89Multicentric, multifocal, number unknown
99Unknown if multiple tumors; not documented
BlankInformation not collected for this diagnosis date (e.g., all cases diagnosed prior to 2007)
Note: Codes 00 and 89 were added effective for 2011.
NAACCR RECORD VERSIONRevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
503NAACCR17 - 19
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
This item applies only to record types I, C, A, and M. Code the NAACCR record version used to create the record. The correction record (U) has its own record version data item.
Rationale
The NAACCR Layout version is necessary to communicate to the recipient of data in NAACCR form where the various items are found and how they are coded. It should be added to the record when the recorded is created.
Codes
1202010 Version 12
1212011 Version 12.1
1222012 Version 12.2
1302013 Version 13
1402014 Version 14
1502015 Version 15
1602016 Version 16
Historically (before 2010), this was a 1-character field with the following codes in column 19:

1             1992-1994 Version 2 and Version 3
4             1995 Version 4.0
5             1996 and 1997 Version 5.0 or Version 5.1
6             1998 Version 6
7             1999 Version 7
8             2000 Version 8
9             2001 and 2002 Version 9 and 9.1
A             2003, 2004, and 2005 Version 10, 10.1, and 10.2
B             2006, 2007, and 2008 Version 11, 11.1, 11.2, and 11.3
Blank     September 1989 Version

Note: Code 4 was assigned to the 1995 Version to synchronize the document version and the layout version numbers. Layout document Versions 2 and 3 are coded as 1.
NAME--ALIAS
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
228040NAACCR3466 - 3505
Alternate Name:Alias (CoC)
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Records an alternate name or “AKA” (also known as) used by the patient, if known. Note that maiden name is entered in Name--Maiden [2390].
Note: This data item is no longer supported by CoC (as of January 1, 2003). 
NAME--FIRST
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
224040CoC3380 - 3419
Alternate Name:First Name (CoC)
XML NAACCR ID:
XML PARENT ELEMENT:
Description
First name of the patient.
Note: The CoC FORDS manual allows this field to be blank. If facilities with CoC-approved cancer programs submit blanks to the central registry, it is suggested that the central registry devise procedures for completing the last and first name with text, such as UNKNOWN, after verifying with the hospital that the field was left intentionally blank.

Note: See the most recent FORDS for CoC allowable values.
NAME--LAST
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
223040CoC201112.23340 - 3379
Alternate Name:Last Name (CoC)
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Last name of the patient.
Note: See the most recent FORDS for CoC allowable values.
NAME--MAIDEN
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
239040NAACCR3506 - 3545
Alternate Name:Maiden Name (CoC)
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Maiden name of female patients who are or have been married.
Rationale
This is used to link reports on a woman who changed her name between reports. It also is critical when using Spanish surname algorithms to categorize ethnicity.

The field should be left blank if the maiden name is not known or not applicable. Since a value in this field may be used by linkage software or other computer algorithms, only legitimate surnames are allowable, and any variation of "unknown" or "not applicable" is not allowable.
Note: This data item is no longer supported by CoC (as of January 1, 2003).
NAME--MIDDLE
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
225040CoC3420 - 3459
Alternate Name:Middle Name (CoC)
Middle Initial (pre-96 CoC)
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Middle name or, if middle name is unavailable, middle initial of the patient.

Note: See the most recent FORDS for CoC allowable values.
NAME--PREFIX
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
22603NAACCR201112.23460 - 3462
Alternate Name:Name Prefix (CoC)
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Abbreviated title that precedes name in a letter (e.g., "Rev," "Ms").
Note: This data item is no longer supported by CoC (as of January 1, 2003).
NAME--SPOUSE/PARENT
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
229060NAACCR201112.23546 - 3605
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
NAACCR has not adopted standards for this item. Use varies by area.
NAME--SUFFIX
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
22703NAACCR201112.23463 - 3465
Alternate Name:Name Suffix (CoC)
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Title that follows a patient's last name, such as a generation order or credential status (e.g., "MD," "Jr.").
Note: This data item is no longer supported by CoC (as of January 1, 2003).
NEXT FOLLOW-UP SOURCE
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
18001CoC2130 - 2130
Alternate Name:Next Follow-Up Method (pre-96 CoC)
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Identifies the method planned for the next follow-up.
Codes
0Chart requisition
1Physician letter
2Contact letter
3Phone call
4Other hospital contact
5Other, NOS
8Foreign residents (not followed)
9Not followed, other cases for which follow-up is not required
NHIA DERIVED HISP ORIGIN
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
1911NAACCR200510.2418 - 418
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
The NAACCR Hispanic Identification Algorithm (NHIA) uses a combination of standard variables to directly or indirectly classify cases as Hispanic for analytic purposes. It is possible to separate Hispanic ancestral subgroups (e.g., Mexican) when indirect assignment results from birthplace information but not from surname match. The algorithm uses the following standard variables: Spanish/Hispanic Origin [190], Name--Last [2230], Name--Maiden [2390], Birthplace [250], Race 1 [160], IHS Link [192], and Sex [220].

Code 7 (Spanish surname only) of the Spanish/Hispanic Origin [190] data item became effective with 1994 diagnoses. It is recommended that NHIA should be run on 1995 and later diagnoses. However, a central registry may run it on their data for prior years. For greater detail, please refer to the technical documentation: http://www.naaccr.org/LinkClick.aspx?fileticket=6E20OT41TcA%3d&tabid=118&mid=458.
Rationale
Sometimes despite best efforts to obtain complete information directly from the medical record, information is not available and is reported to the cancer registry as a missing data item. With regard to Hispanic ethnicity, some cancer registries have found it necessary to rely on indirect methods to populate this data element. Registries often have significant numbers or proportions of Hispanic populations in their jurisdiction.
Codes
0Non-Hispanic
1Mexican, by birthplace or other specific identifier
2Puerto Rican, by birthplace or other specific identifier
3Cuban, by birthplace or other specific identifier
4South or Central American (except Brazil), by birthplace or other specific identifier
5Other specified Spanish/Hispanic origin (includes European; excludes Dominican Republic), by birthplace or other specific identifier
6Spanish, NOS; Hispanic, NOS; Latino, NOS
7NHIA surname match only
8Dominican Republic
BlankAlgorithm has not been run
Note: Code 8 was added in Standards Volume II Version 10.2 effective January 2005.
NPCR DERIVED CLIN STG GRPNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
36504NPCR201616896 - 899
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
This item is needed to store the results of NPCR’s derived algorithmic calculation of clinical stage group based on AJCC T, N, and M and relevant biomarkers and prognostic factors. At this time the algorithm derives AJCC 7th ed. Stage group only; however, updates to future AJCC editions are anticipated.
Rationale
The purpose of the derived stage fields is to segregate the data values for AJCC clinical and pathological stage groups derived from the NPCR algorithm from the values directly entered from the medical record or by the registrar. NPCR’s primary interest is in the directly-entered values, but derived values will have a purpose primarily at the central registry. It is important to not mix data values from the two sources in the same data items.
Codes: (Refer to the most recent version of FORDS for additional coding instructions)
88Not applicable
99Unknown
BlankNot staged
NPCR DERIVED PATH STG GRPNew
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
36554NPCR201616900 - 903
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
This new item is needed to store the results of NPCR’s derived algorithmic calculation of pathological stage group based on AJCC T, N, and M and relevant biomarkers and prognostic factors. At this time the algorithm derives AJCC 7th ed. Stage group only; however, updates to future AJCC editions is anticipated.
Rationale
The purpose of the derived stage fields is to segregate the data values for AJCC clinical and pathological stage groups derived from the NPCR algorithm from the values directly entered from the medical record or by the registrar. NPCR’s primary interest is in the directly-entered values, but derived values will have a purpose primarily at the central registry. It is important to not mix data values from the two sources in the same data items.
Codes:  (Refer to the most recent version of FORDS for additional coding instructions)
88Not applicable
99Unknown
BlankNot staged
NPCR SPECIFIC FIELD
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
372075NPCR2013131306 - 1380
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
A 75 character field to be used when information for a particular primary site needs to be collected by NPCR.
Rationale
This field allows NPCR to retain data collected through the CER project and is a place holder when additional site-specific information is needed.

Codes
To be determined for each site where needed.

BlankField not coded
NPI--ARCHIVE FIN
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
310510CMS200711.1711 - 720
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
This field identifies the NPI number (National Provider Identifier) of the facility at the time it initially accessioned the tumor.

NPI, a unique identification number for US health care providers, was scheduled for 2007-2008 implementation by the Centers for Medicare & Medicaid Services (CMS) as part of the Health Insurance Portability and Accountability Act of 1996 (HIPAA). For billing purposes, large practices and large group providers were required to use NPI codes by May 2007; small health plans were required to use NPI codes by May 2008.
Rationale
The NPI-Archive FIN is the functional equivalent of Archive FIN [3100].
Codes [only valid NPI assigned 10-digit numeric codes (9-digit number plus 1 check digit). The check digit algorithm is available at: https://nppes.cms.hhs.gov/NPPES/NPIRegistryHome.do]
NPI--FOLLOWING REGISTRY
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
244510CMS200711.14285 - 4294
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
The NPI (National Provider Identifier) code that records the registry responsible for following the patient.

NPI, a unique identification number for US health care providers, was scheduled for 2007-2008 implementation by the Centers for Medicare & Medicaid Services (CMS) as part of the Health Insurance Portability and Accountability Act of 1996 (HIPAA). For billing purposes, large practices and large group providers were required to use NPI codes by May 2007; small health plans were required to use NPI codes by May 2008.
Rationale
The number is essential to NCDB for monitoring data submissions, ensuring the accuracy of data, and identifying areas for special studies.
Codes [only valid NPI assigned 10-digit numeric codes (9-digit number plus 1 check digit). The check digit algorithm is available at: https://nppes.cms.hhs.gov/NPPES/NPIRegistryHome.do]
Blank
NPI--INST REFERRED FROM
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
241510CMS200711.14305 - 4314
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
The NPI (National Provider Identifier) code that identifies the facility that referred the patient to the reporting facility.

NPI, a unique identification number for US health care providers, was scheduled for 2007-2008 implementation by the Centers for Medicare & Medicaid Services (CMS) as part of the Health Insurance Portability and Accountability Act of 1996 (HIPAA). For billing purposes, large practices and large group providers were required to use NPI codes by May 2007; small health plans were required to use NPI codes by May 2008.
Rationale
This number is used to document and monitor referral patterns.
Codes [only valid NPI assigned 10-digit numeric codes (9-digit number plus 1 check digit). The check digit algorithm is available at: https://nppes.cms.hhs.gov/NPPES/NPIRegistryHome.do]
Blank
NPI--INST REFERRED TORevised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
242510CMS200711.14325 - 4334
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
The NPI (National Provider Identifier) code that identifies the facility to which the patient was referred for further care.

NPI, a unique identification number for US health care providers, was scheduled for 2007-2008 implementation by the Centers for Medicare & Medicaid Services (CMS) as part of the Health Insurance Portability and Accountability Act of 1996 (HIPAA). For billing purposes, large practices and large group providers were required to use NPI codes by May 2007; small health plans were required to use NPI codes by May 2008.
Rationale
This number is used to document and monitor referral patterns.
Codes [only valid NPI assigned 10-digit numeric codes (9-digit number plus 1 check digit). The check digit algorithm is available at: https://nppes.cms.hhs.gov/NPPES/NPIRegistryHome.do]
Blank
NPI--PHYSICIAN 3
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
249510CMS200711.14449 - 4458
Alternate Name:Radiation Oncologist (CoC)
XML NAACCR ID:
XML PARENT ELEMENT:
Description
The NPI (National Provider Identifier) code for another physician involved in the care of the patient. NPI, a unique identification number for US health care providers, was scheduled for 2007-2008 implementation by the Centers for Medicare & Medicaid Services (CMS) as part of the Health Insurance Portability and Accountability Act of 1996 (HIPAA). For billing purposes, large practices and large group providers were required to use NPI codes by May 2007; small health plans were required to use NPI codes by May 2008.
Rationale
Used to monitor patient radiotherapy care.
Codes [only valid NPI assigned 10-digit numeric codes (9-digit number plus 1 check digit). The check digit algorithm is available at: https://nppes.cms.hhs.gov/NPPES/NPIRegistryHome.do]
Blank
NPI--PHYSICIAN 4
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
250510CMS200711.14467 - 4476
Alternate Name:Medical Oncologist (CoC)
XML NAACCR ID:
XML PARENT ELEMENT:
Description
The NPI (National Provider Identifier) code for another physician involved in the care of the patient.

NPI, a unique identification number for US health care providers, was scheduled for 2007-2008 implementation by the Centers for Medicare & Medicaid Services (CMS) as part of the Health Insurance Portability and Accountability Act of 1996 (HIPAA). For billing purposes, large practices and large group providers were required to use NPI codes by May 2007; small health plans were required to use NPI codes by May 2008.
Rationale
Used to monitor patient medical oncology care.
Codes [only valid NPI assigned 10-digit numeric codes (9-digit number plus 1 check digit). The check digit algorithm is available at: https://nppes.cms.hhs.gov/NPPES/NPIRegistryHome.do]
Blank
NPI--PHYSICIAN--FOLLOW-UP
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
247510CMS200711.14413 - 4422
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
The NPI (National Provider Identifier) code for the physician currently responsible for the patient's medical care.

NPI, a unique identification number for US health care providers, was scheduled for 2007-2008 implementation by the Centers for Medicare & Medicaid Services (CMS) as part of the Health Insurance Portability and Accountability Act of 1996 (HIPAA). For billing purposes, large practices and large group providers were required to use NPI codes by May 2007; small health plans were required to use NPI codes by May 2008.
Rationale
Used to monitor post-treatment patient care.
Codes [only valid NPI assigned 10-digit numeric codes (9-digit number plus 1 check digit). The check digit algorithm is available at: https://nppes.cms.hhs.gov/NPPES/NPIRegistryHome.do]
Blank
NPI--PHYSICIAN--MANAGING
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
246510CMS200711.14395 - 4404
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
The NPI (National Provider Identifier) code that identifies the physician who is responsible for the overall management of the patient during diagnosis and/or treatment for this cancer.

NPI, a unique identification number for US health care providers, was scheduled for 2007-2008 implementation by the Centers for Medicare & Medicaid Services (CMS) as part of the Health Insurance Portability and Accountability Act of 1996 (HIPAA). For billing purposes, large practices and large group providers were required to use NPI codes by May 2007; small health plans were required to use NPI codes by May 2008.
Rationale
Used to monitor patient care.
Codes [only valid NPI assigned 10-digit numeric codes (9-digit number plus 1 check digit). The check digit algorithm is available at: https://nppes.cms.hhs.gov/NPPES/NPIRegistryHome.do]
Blank
NPI--PHYSICIAN--PRIMARY SURG
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
248510CMS200711.14431 - 4440
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
The NPI (National Provider Identifier) code for the physician who performed the most definitive surgical procedure.

NPI, a unique identification number for US health care providers, was scheduled for 2007-2008 implementation by the Centers for Medicare & Medicaid Services (CMS) as part of the Health Insurance Portability and Accountability Act of 1996 (HIPAA). For billing purposes, large practices and large group providers were required to use NPI codes by May 2007; small health plans were required to use NPI codes by May 2008.
Rationale
Used to monitor patient surgical care.
Codes [only valid NPI assigned 10-digit numeric codes (9-digit number plus 1 check digit). The check digit algorithm is available at: https://nppes.cms.hhs.gov/NPPES/NPIRegistryHome.do]
Blank
NPI--REGISTRY ID
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
4510CMS200711.120 - 29
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
The NPI (National Provider Identifier) code that represents the data transmission source. This item stores the NPI of the facility registry that transmits the record.

NPI, a unique identification number for US health care providers, was scheduled for 2007-2008 implementation by the Centers for Medicare & Medicaid Services (CMS) as part of the Health Insurance Portability and Accountability Act of 1996 (HIPAA). For billing purposes, large practices and large group providers were required to use NPI codes by May 2007; small health plans were required to use NPI codes by May 2008.

If the transmission source is not a health care provider or a covered entity, this item will be blank and the item Registry ID [40] should be used to identify the transmission source.
Rationale
The NPI equivalent of Registry ID [40].
Codes [only valid NPI assigned 10-digit numeric codes (9-digit number plus 1 check digit). The check digit algorithm is available at: https://nppes.cms.hhs.gov/NPPES/NPIRegistryHome.do]
NPI--REPORTING FACILITY
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
54510CMS200711.1691 - 700
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
The NPI (National Provider Identifier) code for the facility submitting the data in the record.

NPI, a unique identification number for US health care providers, was scheduled for 2007-2008 implementation by the Centers for Medicare & Medicaid Services (CMS) as part of the Health Insurance Portability and Accountability Act of 1996 (HIPAA). For billing purposes, large practices and large group providers were required to use NPI codes by May 2007; small health plans were required to use NPI codes by May 2008.
Rationale
The NPI equivalent of Reporting Facility [540].
Codes [only valid NPI assigned 10-digit numeric codes (9-digit number plus 1 check digit). The check digit algorithm is available at: https://nppes.cms.hhs.gov/NPPES/NPIRegistryHome.do]
OCCUPATION SOURCE
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
2901NPCR215 - 215
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Code that best describes the source of occupation information provided on this patient. 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).
Rationale
Occupation information may come from a variety of sources. The most valid and reliable source of occupation information for patients has not yet been determined.
Codes
0Unknown occupation/no occupation available
1Reporting facility records
2Death certificate
3Interview
7Other source
8Not applicable, patient less than 14 years of age at diagnosis
9Unknown source
BlankNot collected
OVER-RIDE ACSN/CLASS/SEQ
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
19851CoC200191891 - 1891
Alternate Name:Over-ride Accession/Class of Case/Sequence
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Some computer edits identify errors. Others indicate possible errors that require manual review for resolution. To eliminate the need to review the same cases repeatedly, over-ride flags have been developed to indicate that data in a record (or records) have been reviewed and, while unusual, are correct.

This over-ride is used with the following edit in the NAACCR Metafile of the EDITS software: Accession Number, Class of Case, Seq Number (CoC).
Rationale
Some edits check for code combinations that are possible, but quite rare. If the code combination generates an error message and review of the case indicates that the codes are correct for the case, then the over-ride flag is used to skip the edit in the future. See Chapter IV, Recommended Data Edits and Software Coordination of Standards.

Over-ride Flag as Used in the EDITS Software Package
The edit, Accession Number, Class of Case, Seq Number (CoC), checks the following:
  1. If the case is the only case or the first of multiple cases diagnosed at the facility (Sequence Number--Hospital = 00, 01, 60, or 61, and Class of Case = 00, 10-14, or 40), then the first 4 characters of the Accession Number--Hosp must equal the year of the Date of 1st Contact.
  2. If the case is first diagnosed at autopsy (Class of Case = 38) and the case is the only case or the first of multiple cases for a patient (Sequence Number--Hospital = 00, 01, 60, or 61), then the first 4 characters of the Accession Number--Hosp must equal the year of the Date of Last Contact AND must equal the year of the Date of 1st Contact.
  3. If the case is first diagnosed at autopsy (Class of Case = 38) and the case is not the first case for a patient (Sequence Number--Hospital) greater than 01 or greater than 61), then the year of the Date of 1st Contact must equal the year of Date of Last Contact.
There are some exceptions to the above rules. Over-ride Acsn/Class/Seq may be used to override the edit when the circumstances fit the following situation or one similar to it:
The case may be the only or the first of multiple malignant cases for a patient (Sequence Number--Hospital = 00 or 01), but there is an earlier benign case (with an earlier year of the Date of 1st Contact) to which the Accession Number--Hosp applies.
Instructions for Coding
  1. If edit generates an error or warning message, verify that the Accession Number--Hosp, Sequence Number--Hospital, and Class of Case are correct.
  2. Leave blank if the program does not generate an error message for the edit Accession Number, Class of Case, Seq Number (CoC).
  3. Leave blank and correct any errors for the case if an item is discovered to be incorrect.
  4. Code 1 if review of accession number, sequence number and class of case verifies that they have been coded correctly and there is an unusual combination of these data items.
Codes
BlankNot reviewed or reviewed and corrected
1Reviewed and confirmed as reported
OVER-RIDE AGE/SITE/MORPH
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
19901SEER1896 - 1896
Alternate Name:Age/Site/Histology Interfield Review (Interfield Edit 15) (SEER #3)
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Some computer edits identify errors. Others indicate possible errors that require manual review for resolution. To eliminate the need to review the same cases repeatedly, over-ride flags have been developed to indicate that data in a record (or records) have been reviewed and, while unusual, are correct.
This over-ride is used with the following edits in the NAACCR Metafile of the EDITS software:
Age, Primary Site, Morphology ICDO2 (SEER IF15)
Age, Primary Site, Morphology ICDO3 (SEER IF15)
Age, Primary Site, Morph ICDO3--Adult (SEER)
Age, Primary Site, Morph ICDO3--Pediatric (NPCR)
Rationale
Some edits check for code combinations that are possible, but quite rare. If the code combination generates an error message and review of the case indicates that the codes are correct for the case, then the over-ride flag is used to skip the edit in the future. See Chapter IV, Recommended Data Edits and Software Coordination of Standards.

Over-ride Flag as Used in the EDITS Software Package
Some cancers occur almost exclusively in certain age groups.

Edits of the type Age, Primary Site, Morphology require review if a site/morphology combination occurs in an age group for which it is extremely rare. The edit Age, Primary Site, Morph ICDO3--Adult (SEER) edits cases with an Age at Diagnosis of 15 and older. The edit Age, Primary Site, Morph ICDO3--Pediatric (NPCR) edits cases with an Age at Diagnosis of less than 15. The edits Age, Primary Site, Morphology ICDO2 (SEER IF15) and Age, Primary Site, Morphology ICDO3 (SEER IF15) contain logic for all ages.

Instructions for Coding
  1. Leave blank if the program does not generate an error message (and if the case was not diagnosed in utero) for the edits of the type Age, Primary Site, Morphology.
  2. Correct any errors for the case if an item is discovered to be incorrect.
  3. Code 1 or 3 as indicated if review of items in the error or warning message confirms that all are correct.
Codes
1Reviewed and confirmed that age/site/histology combination is correct as reported
2Reviewed and confirmed that case was diagnosed in utero
3Reviewed and confirmed that conditions 1 and 2 both apply
BlankNot reviewed or reviewed and corrected.
OVER-RIDE COC-SITE/TYPE
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
19871CoC200191893 - 1893
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Some computer edits identify errors. Others indicate possible errors that require manual review for resolution. To eliminate the need to review the same cases repeatedly, over-ride flags have been developed to indicate that data in a record (or records) have been reviewed and, while unusual, are correct.

This over-ride is used with the following edits in the NAACCR Metafile of the EDITS software:
      Primary Site, Morphology-Type ICDO2 (CoC)
      Primary Site, Morphology-Type ICDO3 (CoC)
      Primary Site, Morphology-Type, Behavior ICDO3 (CoC)
Rationale
Some edits check for code combinations that are possible, but quite rare. If the code combination generates an error message and review of the case indicates that the codes are correct for the case, then the over-ride flag is used to skip the edit in the future. See Chapter IV, Recommended Data Edits and Software Coordination of Standards.

Over-ride Flag as Used in the EDITS Software Package

Multiple versions of edits of the type Primary Site, Morphology-Type check for "usual" combinations of site and ICD-O-2 or ICD-O-3 histology. The SEER version of the edit is more restrictive than the CoC edit, and thus, uses a different over-ride flag. The CoC version of the edit will accept Over-ride CoC Site/Type or Over-ride Site/Type (the SEER edit) as equivalent.

The Site/Histology validation list (available on the SEER web site) contains those histologies commonly found in the specified primary site. Histologies that occur only rarely or never are not included. These edits require review of all combinations not listed.

Since basal and squamous cell carcinomas of non-genital skin sites are not reportable to SEER, these site/histology combinations do not appear on the SEER validation list. For the CoC version of the edit, if primary site is in the range C440-C449 (skin), and ICD-O-2 histology is in the range 8000-8004 (neoplasms, malignant, NOS), 8010-8045 (epithielial carcinomas), 8050-8082 (papillary and squamous cell carcinomas), or 8090-8110 (basal cell carcinomas), or ICD-O-3 histology is in the range 8000-8005 (neoplasms, malignant, NOS), 8010-8046 (epithelial carcinomas), 8050-8084 (papillary and squamous cell carcinomas), or 8090-8110 (basal cell carcinomas), no further editing is done. No over-ride is necessary for these cases in the CoC version of the edit.

Review of these cases requires investigating whether the combination is biologically plausible or whether cancer registry coding conventions would allow different codes for the diagnosis. Review of these rare combinations often results in a change to either the site or histology.

Instructions for Coding

  1. Leave blank if the program does not generate an error message for the CoC edits of the type Primary Site, Morphology-Type.
  2. Leave blank and correct any errors for the case if an item is discovered to be incorrect.
  3. Code 1 if review of all items in the error or warning message confirms they are correct and coded in conformance with coding rules.
Codes
BlankNot reviewed or reviewed and corrected
1Reviewed and confirmed as reported
OVER-RIDE CS 1Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
37501AJCC201112.12016 - 2016
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Some computer edits identify errors. Others indicate possible errors that require manual review for resolution. To eliminate the need to review the same cases repeatedly, over-ride flags have been developed to indicate that data in a record (or records) have been reviewed and, while unusual, are correct.
Rationale
Some edits check for code combinations that are possible, but quite rare. If the code combination generates an error message and review of the case indicates that the codes are correct for the case, then the over-ride flag is used to skip the edit in the future.
Codes
1Reviewed and confirmed as reported
BlankNot reviewed or reviewed and corrected
OVER-RIDE CS 10Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
37591AJCC201112.12025 - 2025
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Some computer edits identify errors. Others indicate possible errors that require manual review for resolution. To eliminate the need to review the same cases repeatedly, over-ride flags have been developed to indicate that data in a record (or records) have been reviewed and, while unusual, are correct.
Rationale
Some edits check for code combinations that are possible, but quite rare. If the code combination generates an error message and review of the case indicates that the codes are correct for the case, then the over-ride flag is used to skip the edit in the future.
Codes
1Reviewed and confirmed as reported
BlankNot reviewed or reviewed and corrected
OVER-RIDE CS 11Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
37601AJCC201112.12026 - 2026
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Some computer edits identify errors. Others indicate possible errors that require manual review for resolution. To eliminate the need to review the same cases repeatedly, over-ride flags have been developed to indicate that data in a record (or records) have been reviewed and, while unusual, are correct.
Rationale
Some edits check for code combinations that are possible, but quite rare. If the code combination generates an error message and review of the case indicates that the codes are correct for the case, then the over-ride flag is used to skip the edit in the future.
Codes
1Reviewed and confirmed as reported
BlankNot reviewed or reviewed and corrected
OVER-RIDE CS 12Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
37611AJCC201112.12027 - 2027
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Some computer edits identify errors. Others indicate possible errors that require manual review for resolution. To eliminate the need to review the same cases repeatedly, over-ride flags have been developed to indicate that data in a record (or records) have been reviewed and, while unusual, are correct.
Rationale
Some edits check for code combinations that are possible, but quite rare. If the code combination generates an error message and review of the case indicates that the codes are correct for the case, then the over-ride flag is used to skip the edit in the future.
Codes
1Reviewed and confirmed as reported
BlankNot reviewed or reviewed and corrected
OVER-RIDE CS 13Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
37621AJCC201112.12028 - 2028
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Some computer edits identify errors. Others indicate possible errors that require manual review for resolution. To eliminate the need to review the same cases repeatedly, over-ride flags have been developed to indicate that data in a record (or records) have been reviewed and, while unusual, are correct.
Rationale
Some edits check for code combinations that are possible, but quite rare. If the code combination generates an error message and review of the case indicates that the codes are correct for the case, then the over-ride flag is used to skip the edit in the future.
Codes
1Reviewed and confirmed as reported
BlankNot reviewed or reviewed and corrected
OVER-RIDE CS 14Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
37631AJCC201112.12029 - 2029
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Some computer edits identify errors. Others indicate possible errors that require manual review for resolution. To eliminate the need to review the same cases repeatedly, over-ride flags have been developed to indicate that data in a record (or records) have been reviewed and, while unusual, are correct.
Rationale
Some edits check for code combinations that are possible, but quite rare. If the code combination generates an error message and review of the case indicates that the codes are correct for the case, then the over-ride flag is used to skip the edit in the future.
Codes
1Reviewed and confirmed as reported
BlankNot reviewed or reviewed and corrected
OVER-RIDE CS 15Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
37641AJCC201112.12030 - 2030
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Some computer edits identify errors. Others indicate possible errors that require manual review for resolution. To eliminate the need to review the same cases repeatedly, over-ride flags have been developed to indicate that data in a record (or records) have been reviewed and, while unusual, are correct.
Rationale
Some edits check for code combinations that are possible, but quite rare. If the code combination generates an error message and review of the case indicates that the codes are correct for the case, then the over-ride flag is used to skip the edit in the future.
Codes
1Reviewed and confirmed as reported
BlankNot reviewed or reviewed and corrected
OVER-RIDE CS 16Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
37651AJCC201112.12031 - 2031
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Some computer edits identify errors. Others indicate possible errors that require manual review for resolution. To eliminate the need to review the same cases repeatedly, over-ride flags have been developed to indicate that data in a record (or records) have been reviewed and, while unusual, are correct.
Rationale
Some edits check for code combinations that are possible, but quite rare. If the code combination generates an error message and review of the case indicates that the codes are correct for the case, then the over-ride flag is used to skip the edit in the future.
Codes
1Reviewed and confirmed as reported
BlankNot reviewed or reviewed and corrected
OVER-RIDE CS 17Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
37661AJCC201112.12032 - 2032
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Some computer edits identify errors. Others indicate possible errors that require manual review for resolution. To eliminate the need to review the same cases repeatedly, over-ride flags have been developed to indicate that data in a record (or records) have been reviewed and, while unusual, are correct.
Rationale
Some edits check for code combinations that are possible, but quite rare. If the code combination generates an error message and review of the case indicates that the codes are correct for the case, then the over-ride flag is used to skip the edit in the future.
Codes
1Reviewed and confirmed as reported
BlankNot reviewed or reviewed and corrected
OVER-RIDE CS 18Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
37671AJCC201112.12033 - 2033
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Some computer edits identify errors. Others indicate possible errors that require manual review for resolution. To eliminate the need to review the same cases repeatedly, over-ride flags have been developed to indicate that data in a record (or records) have been reviewed and, while unusual, are correct.
Rationale
Some edits check for code combinations that are possible, but quite rare. If the code combination generates an error message and review of the case indicates that the codes are correct for the case, then the over-ride flag is used to skip the edit in the future.
Codes
1Reviewed and confirmed as reported
BlankNot reviewed or reviewed and corrected
OVER-RIDE CS 19Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
37681AJCC201112.12034 - 2034
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Some computer edits identify errors. Others indicate possible errors that require manual review for resolution. To eliminate the need to review the same cases repeatedly, over-ride flags have been developed to indicate that data in a record (or records) have been reviewed and, while unusual, are correct.
Rationale
Some edits check for code combinations that are possible, but quite rare. If the code combination generates an error message and review of the case indicates that the codes are correct for the case, then the over-ride flag is used to skip the edit in the future.
Codes
1Reviewed and confirmed as reported
BlankNot reviewed or reviewed and corrected
OVER-RIDE CS 2Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
37511AJCC201112.12017 - 2017
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Some computer edits identify errors. Others indicate possible errors that require manual review for resolution. To eliminate the need to review the same cases repeatedly, over-ride flags have been developed to indicate that data in a record (or records) have been reviewed and, while unusual, are correct.
Rationale
Some edits check for code combinations that are possible, but quite rare. If the code combination generates an error message and review of the case indicates that the codes are correct for the case, then the over-ride flag is used to skip the edit in the future.
Codes
1Reviewed and confirmed as reported
BlankNot reviewed or reviewed and corrected
OVER-RIDE CS 20Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
37691AJCC/NPCR201112.12035 - 2035
Alternate Name:Direct Summary Stage 2000 Flag
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Some computer edits identify errors. Others indicate possible errors that require manual review for resolution. To eliminate the need to review the same cases repeatedly, over-ride flags have been developed to indicate that data in a record (or records) have been reviewed and, while unusual, are correct.

Over-ride CS 20 has been designated as a flag for directly coded SEER Summary Stage 2000 [759] to support CDC's National Program of Cancer Registries (NPCR) requirements.
Rationale
Some edits check for code combinations that are possible, but quite rare. If the code combination generates an error message and review of the case indicates that the codes are correct for the case, then the over-ride flag is used to skip the edit in the future. For diagnosis years 2012 and later, NPCR permits the use of SEER Summary Stage 2000 [759] in those cases where collection of Collaborative Stage version 2 data items is not feasible due to a lack of data or staffing and time constraints at the local or central cancer registry. Over-ride CS 20 has been designated as a special-purpose flag to identify cases where SEER Summary Stage 2000 [759] is directly coded and reported in lieu of Derived SS2000 [3020], in accordance with NPCR reporting requirements.

The Over-ride CS 20 value of "1", set by the user, identifies a record with NAACCR data item 759 used to report Summary Stage 2000 as permitted by NPCR requirements only; Over-ride CS 20 is left blank for all other cases.
Codes
1Directly coded SEER Summary Stage 2000 [759] used to report Summary Stage; Derived Summary Stage 2000 [3020] must be blank.
BlankDerived Summary Stage 2000 [3020] reported using Collaborative Stage Data Collection System or case diagnosed prior to 2012.
OVER-RIDE CS 3Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
37521AJCC201112.12018 - 2018
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Some computer edits identify errors. Others indicate possible errors that require manual review for resolution. To eliminate the need to review the same cases repeatedly, over-ride flags have been developed to indicate that data in a record (or records) have been reviewed and, while unusual, are correct.
Rationale
Some edits check for code combinations that are possible, but quite rare. If the code combination generates an error message and review of the case indicates that the codes are correct for the case, then the over-ride flag is used to skip the edit in the future.
Codes
1Reviewed and confirmed as reported
BlankNot reviewed or reviewed and corrected
OVER-RIDE CS 4Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
37531AJCC201112.12019 - 2019
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Some computer edits identify errors. Others indicate possible errors that require manual review for resolution. To eliminate the need to review the same cases repeatedly, over-ride flags have been developed to indicate that data in a record (or records) have been reviewed and, while unusual, are correct.
Rationale
Some edits check for code combinations that are possible, but quite rare. If the code combination generates an error message and review of the case indicates that the codes are correct for the case, then the over-ride flag is used to skip the edit in the future.
Codes
1Reviewed and confirmed as reported
BlankNot reviewed or reviewed and corrected
OVER-RIDE CS 5Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
37541AJCC201112.12020 - 2020
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Some computer edits identify errors. Others indicate possible errors that require manual review for resolution. To eliminate the need to review the same cases repeatedly, over-ride flags have been developed to indicate that data in a record (or records) have been reviewed and, while unusual, are correct.
Rationale
Some edits check for code combinations that are possible, but quite rare. If the code combination generates an error message and review of the case indicates that the codes are correct for the case, then the over-ride flag is used to skip the edit in the future.
Codes
1Reviewed and confirmed as reported
BlankNot reviewed or reviewed and corrected
OVER-RIDE CS 6Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
37551AJCC201112.12021 - 2021
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Some computer edits identify errors. Others indicate possible errors that require manual review for resolution. To eliminate the need to review the same cases repeatedly, over-ride flags have been developed to indicate that data in a record (or records) have been reviewed and, while unusual, are correct.
Rationale
Some edits check for code combinations that are possible, but quite rare. If the code combination generates an error message and review of the case indicates that the codes are correct for the case, then the over-ride flag is used to skip the edit in the future.
Codes
1Reviewed and confirmed as reported
BlankNot reviewed or reviewed and corrected
OVER-RIDE CS 7Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
37561AJCC201112.12022 - 2022
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Some computer edits identify errors. Others indicate possible errors that require manual review for resolution. To eliminate the need to review the same cases repeatedly, over-ride flags have been developed to indicate that data in a record (or records) have been reviewed and, while unusual, are correct.
Rationale
Some edits check for code combinations that are possible, but quite rare. If the code combination generates an error message and review of the case indicates that the codes are correct for the case, then the over-ride flag is used to skip the edit in the future.
Codes
1Reviewed and confirmed as reported
BlankNot reviewed or reviewed and corrected
OVER-RIDE CS 8Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
37571AJCC201112.12023 - 2023
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Some computer edits identify errors. Others indicate possible errors that require manual review for resolution. To eliminate the need to review the same cases repeatedly, over-ride flags have been developed to indicate that data in a record (or records) have been reviewed and, while unusual, are correct.
Rationale
Some edits check for code combinations that are possible, but quite rare. If the code combination generates an error message and review of the case indicates that the codes are correct for the case, then the over-ride flag is used to skip the edit in the future.
Codes
1Reviewed and confirmed as reported
BlankNot reviewed or reviewed and corrected
OVER-RIDE CS 9Revised
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
37581AJCC201112.12024 - 2024
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Some computer edits identify errors. Others indicate possible errors that require manual review for resolution. To eliminate the need to review the same cases repeatedly, over-ride flags have been developed to indicate that data in a record (or records) have been reviewed and, while unusual, are correct.
Rationale
Some edits check for code combinations that are possible, but quite rare. If the code combination generates an error message and review of the case indicates that the codes are correct for the case, then the over-ride flag is used to skip the edit in the future.
Codes
1Reviewed and confirmed as reported
BlankNot reviewed or reviewed and corrected
OVER-RIDE HISTOLOGY
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
20401SEER1901 - 1901
Alternate Name:Histology/Behavior Interfield Review (Field Item Edit Morph)
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Some computer edits identify errors. Others indicate possible errors that require manual review for resolution. To eliminate the need to review the same cases repeatedly, over-ride flags have been developed to indicate that data in a record (or records) have been reviewed and, while unusual, are correct.
This over-ride is used with the following edits in the NAACCR Metafile of the EDITS software:
      Diagnostic Confirmation, Behavior ICDO2 (SEER IF31)
      Diagnostic Confirmation, Behavior ICDO3 (SEER IF31)
      Morph (1973-91) ICD-O-1 (SEER MORPH)
      Morphology--Type/Behavior ICDO2 (SEER MORPH)
      Morphology--Type/Behavior ICDO3 (SEER MORPH)
Rationale
Some edits check for code combinations that are possible, but quite rare. If the code combination generates an error message and review of the case indicates that the codes are correct for the case, then the over-ride flag is used to skip the edit in the future. See Chapter IV, Recommended Data Edits and Software Coordination of Standards.

Over-ride Flags as Used in the EDITS Software Package

Edits of the type Diagnostic Confirmation, Behavior differ in the use of ICD-O-2 or ICD-O-3 and check that, for in situ cases (Behavior = 2), Diagnostic Confirmation specifies microscopic confirmation (1, 2, or 4).

The distinction between in situ and invasive is very important to a registry, since prognosis is so different. Since the determination that a neoplasm has not invaded surrounding tissues, i.e., in situ, is made microscopically, cases coded in situ in behavior should have a microscopic confirmation code. However, very rarely, a physician will designate a case noninvasive or in situ without microscopic evidence.
If an edit of the type, Diagnostic Confirmation, Behavior, gives an error message or warning, check that Behavior and Diagnostic Confirmation have been coded correctly. Check carefully for any cytologic or histologic evidence that may have been missed in coding.
Edits of the type, Morphology--Type/Behavior, perform the following check:
  1. Codes listed in ICD-O-2 or ICD-O-3 with behavior codes of only 0 or 1 are considered valid, since the behavior matrix of ICD-O-2 and ICD-O-3 allows for the elevation of the behavior of such histologies when the tumor is in situ or malignant. This edit forces review of these rare cases to verify that they are indeed in situ or malignant.

  2. The following histologies are generally not accepted as in situ: ICD-O-2 histologies 8000-8004, 8020, 8021, 8331, 8332, 8800-9054, 9062, 9082, 9083, 9110-9491, 9501-9989, ICD-O-3 histologies 8000-8005, 8020, 8021, 8331, 8332, 8800-9055, 9062, 9082, 9083, 9110-9493, 9501-9989. This edit forces review of these cases.

  3. If a Morphology-Type/Behavior edit produces an error or warning message and the case is one in which the 4-digit morphology code is one that appears in ICD-O-2 or ICD-O-3 only with behavior codes of 0 or 1, or the case is one in which the 4-digit morphology code is not generally accepted with a behavior code of 2, verify the coding of morphology and that the behavior should be coded malignant or in situ. The registrar may need to consult a pathologist or medical advisor in problem cases.

    Exceptions:
    If year of Date of Diagnosis &gt; 2000, then a behavior code of 1 is valid for the following ICD-O-2 histologies and no over-ride flag is needed: 8931, 9393, 9538, 9950, 9960-9962, 9980-9984, and 9989. Similarly, the following ICD-O-3 histologies are valid with a behavior code of 1: 8442, 8451, 8462, 8472, and 8473.If year of Date of Diagnosis &gt; 2003, the following ICD-O-3 benign histologies will pass without review: 8146, 8271, 8861, 8897, 9121, 9122, 9131, 9161, 9350, 9351, 9352, 9360, 9361, 9383, 9384, 9394, 9412, 9413, 9444, 9492, 9493, 9506, 9531, 9532, 9533, 9534, 9537, 9541, 9550, 9562, and 9570.

  4. Grade 5-8 with histologies not in the range of 9590-9948 is impossible.

  5. Some terms in ICD-O-2 and ICD-O-3 carry an implied statement of grade. These histologies must be reported with the correct grade as stated below. An error of this type cannot be over-ridden.
     
    ICD-O-2
    8020/34 Carcinoma, undifferentiated
    8021/34 Carcinoma, anaplastic
    8331/31 Follicular adenocarcinoma, well differentiated
    8851/31 Liposarcoma, well differentiated
    9062/34 Seminoma, anaplastic
    9082/34 Malignant teratoma, undifferentiated
    9083/32 Malignant teratoma, intermediate type
    9401/34 Astrocytoma, anaplastic
    9451/34 Oligodendroglioma, anaplastic
    9511/31 Retinoblastoma, differentiated
    9512/34 Retinoblastoma, undifferentiated

    ICD-O-3
    8020/34 Carcinoma, undifferentiated
    8021/34 Carcinoma, anaplastic
    8331/31 Follicular adenocarcinoma, well differentiated
    9082/34 Malignant teratoma, undifferentiated
    9083/32 Malignant teratoma, intermediate type
    9401/34 Astrocytoma, anaplastic
    9451/34 Oligodendroglioma, anaplastic
    9511/31 Retinoblastoma, differentiated
    9512/34 Retinoblastoma, undifferentiated

Instructions for Coding

  1. Leave blank if the program does not generate an error message for the edits of the types, Diagnostic Confirmation, Behav Code or Morphology--Type/Behavior.
  2. Leave blank and correct any errors for the case if an item is discovered to be incorrect.
  3. Code 1, 2, or 3 as indicated if review of all items in the error or warning message confirms that all are correct.
Codes
1Reviewed and confirmed that the pathologist states the primary to be “in situ” or “malignant” although the behavior code of the histology is designated as “benign” or “uncertain” in ICD-O-2 or ICD-O-3
2Reviewed and confirmed that the behavior code is “in situ,” but the case is not microscopically confirmed
3Reviewed and confirmed that conditions 1 and 2 both apply
BlankNot reviewed or reviewed and corrected
OVER-RIDE HOSPSEQ/DXCONF
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
19861CoC200191892 - 1892
Alternate Name:Over-ride Hospital Sequence/Diagnostic Confirmation
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Some computer edits identify errors. Others indicate possible errors that require manual review for resolution. To eliminate the need to review the same cases repeatedly, over-ride flags have been developed to indicate that data in a record (or records) have been reviewed and, while unusual, are correct.

This over-ride is used with the following edit in the NAACCR Metafile of the EDITS software:
      Diagnostic Confirm, Seq Num--Hosp (CoC)
Rationale
Some edits check for code combinations that are possible, but quite rare. If the code combination generates an error message and review of the case indicates that the codes are correct for the case, then the over-ride flag is used to skip the edit in the future. See Chapter IV, Recommended Data Edits and Software Coordination of Standards.

Over-ride Flag as Used in the EDITS Software Package

The edit, Diagnostic Confirm, Seq Num--Hosp (CoC), does the following:
  1. If any case is one of multiple primaries and is not microscopically confirmed or lacks a positive lab test/marker study, i.e., Diagnostic Confirmation &gt; 5 and Sequence Number--Hospital &gt; 00 (more than one primary), review is required.
  2. If Primary Site specifies an ill-defined or unknown primary (C760-C768, C809), no further checking is done.
  3. If Sequence Number--Hospital is in the range of 60-88, this edit is skipped.

It is important to verify that the non-microscopically confirmed case is indeed a separate primary from any others that may have been reported. This edit forces review of multiple primary cancers when one of the primaries is coded to a site other than ill-defined or unknown and is not microscopically confirmed or confirmed by a positive lab test/marker study.

  1. If the suspect case is confirmed accurate as coded and if the number of primaries is correct, set the Over-ride HospSeq/DxConf to 1. Do not set the over-ride flag on the patient's other primary cancers.
  2. If it turns out that the non-microscopically confirmed cancer is considered a manifestation of one of the patient's other cancers, delete the non-microscopically confirmed case. Check the sequence numbers of remaining cases, correcting them if necessary. Also check for other data items on the remaining cases that may need to be changed as a result of the corrections, such as stage and treatment.

Instructions for Coding

  • Leave blank if the program does not generate an error message for the edit Diagnostic Confirm, Seq Num--Hosp (CoC).
  • Leave blank and correct any errors for the case if an item is discovered to be incorrect.
  • Code 1 if review of all items in the error or warning message confirms that all are correct.
Codes
1Reviewed and confirmed as reported
BlankNot reviewed or reviewed and corrected
OVER-RIDE HOSPSEQ/SITE
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
19881CoC200191894 - 1894
Alternate Name:Over-ride Hospital Sequence/Site
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Some computer edits identify errors. Others indicate possible errors that require manual review for resolution. To eliminate the need to review the same cases repeatedly, over-ride flags have been developed to indicate that data in a record (or records) have been reviewed and, while unusual, are correct.

This over-ride is used with the following edits in the NAACCR Metafile of the EDITS software:
      Seq Num--Hosp, Primary Site, Morph ICDO2 (CoC)
      Seq Num--Hosp, Primary Site, Morph ICDO3 (CoC)
Rationale
Some edits check for code combinations that are possible, but quite rare. If the code combination generates an error message and review of the case indicates that the codes are correct for the case, then the over-ride flag is used to skip the edit in the future. See Chapter IV, Recommended Data Edits and Software Coordination of Standards.

Over-ride Flag as Used in the EDITS Software Package
Edits of the type Seq Num--Hosp, Primary Site, Morph differ in use of ICD-O-2 or ICD-O-3 morphology. They force review of multiple primary cancers when one of the primaries is coded to a site/morphology combination that could indicate a metastatic site rather than a primary site.
  1. If Sequence Number--Hospital indicates the person has had more than one primary, then any case with one of the following site/histology combinations requires review:
    • C760-C768 (ill-defined sites) or C809 (unknown primary) and ICD-O-2 or ICD-O-3 histology &lt; 9590. Look for evidence that the unknown or ill-defined primary is a secondary site from one of the patient’s other cancers. For example, a clinical discharge diagnosis of “abdominal carcinomatosis” may be attributable to the patient’s primary ovarian cystadenocarcinoma already in the registry, and should not be entered as a second primary.
    • C770-C779 (lymph nodes) and ICD-O-2 histology not in range 9590-9717 or ICD-O-3 histology not in the range 9590-9729; or C420-C424 and ICD-O-2 histology not in range 9590-9941 or ICD-O-3 histology not in the range 9590-9989. That combination is most likely a metastatic lesion. Check whether the lesion could be a manifestation of one of the patient’s other cancers.
    •  Any site and ICD-O-2 histology in the range 9720-9723, 9740-9741 or ICD-O-3 histology in the range 9740-9758. Verify that these diagnoses are coded correctly and are indeed separate primaries from the others.
  2. If it turns out that the suspect tumor is a manifestation of one of the patient's other cancers, delete the metastatic or secondary case, re-sequence remaining cases, and correct the coding on the original case as necessary.
Instructions for Coding
  • Leave blank if the program does not generate an error message for an edit of the type Seq Num--Hosp, Primary Site, Morph.
  • Leave blank and correct any errors for the case if an item is discovered to be incorrect.
  • Code 1 if review of all items in the error or warning message confirms that hospital sequence number and site are both correct.
Codes
1Reviewed and confirmed as reported
BlankNot reviewed or reviewed and corrected
OVER-RIDE ILL-DEFINE SITE
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
20601SEER1903 - 1903
Alternate Name:Sequence Number/Ill-defined Site Interfield Review (Interfield Edit 22)
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Some computer edits identify errors. Others indicate possible errors that require manual review for resolution. To eliminate the need to review the same cases repeatedly, over-ride flags have been developed to indicate that data in a record (or records) have been reviewed and, while unusual, are correct.

This over-ride is used with the following edits in the NAACCR Metafile of the EDITS software:
      Seq Num--Central, Prim Site, Morph ICDO2 (SEER IF22)
      Seq Num--Central, Prim Site, Morph ICDO3 (SEER IF22)
Rationale
Some edits check for code combinations that are possible, but quite rare. If the code combination generates an error message and review of the case indicates that the codes are correct for the case, then the over-ride flag is used to skip the edit in the future. See Chapter IV, Recommended Data Edits and Software Coordination of Standards.

Over-ride Flag as Used in the EDITS Software Package

Edits of the type Seq Num--Central, Primary Site, Morph differ in use of ICD-O-2 or ICD-O-3 morphology. They force review of multiple primary cancers when one of the primaries is coded to a site/morphology combination that could indicate a metastatic site rather than a primary site.
  1. If Sequence Number-Central indicates the person has had more than one primary, then any case with one of the following site/histology combinations requires review:
    • C760-C768 (ill-defined sites) or C809 (unknown primary) and ICD-O-2 or ICD-O-3 histology &lt; 9590. Look for evidence that the unknown or ill-defined primary is a secondary site from one of the patient’s other cancers. For example, a clinical discharge diagnosis of “abdominal carcinomatosis” may be attributable to the patient’s primary ovarian cystadenocarcinoma already in the registry, and should not be entered as a second primary.
    • C770-C779 (lymph nodes) and ICD-O-2 histology not in the range 9590-9717 or ICD-O-3 histology not in the range 9590-9729; or C420-C424 and ICD-O-2 histology not in the range 9590-9941 or ICD-O-3 histology not in the range 9590-9989. That combination is most likely a metastatic lesion. Check whether the lesion could be a manifestation of one of the patient’s other cancers.
    • Any site and ICD-O-2 histology in the range 9720-9723, 9740-9741 or ICD-O-3 histology in the range 9740-9758. Verify that these diagnoses are coded correctly and are indeed separate primaries from the others.
  2. If it turns out that the suspect tumor is a manifestation of one of the patient's other cancers, delete the metastatic or secondary case, re-sequence remaining cases, and correct the coding on the original case as necessary.
Instructions for Coding
  • Code 1 can be used if a second or subsequent primary reporting with an ill-defined primary site has been reviewed and is indeed an independent primary.
  • Leave blank and correct any errors for the case if an item is discovered to be incorrect.
Codes
1Reviewed and confirmed as reported: a second or subsequent primary reported with an ill-defined primary site (C76.0-C76.8, C80.9) has been reviewed and is an independent primary
BlankNot reviewed or reviewed and corrected
OVER-RIDE LEUK, LYMPHOMA
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
20701SEER1904 - 1904
Alternate Name:Leukemia or Lymphoma/Diagnostic Confirmation Interfield Review (Interfield Edit 48)
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Some computer edits identify errors. Others indicate possible errors that require manual review for resolution. To eliminate the need to review the same cases repeatedly, over-ride flags have been developed to indicate that data in a record (or records) have been reviewed and, while unusual, are correct.

This over-ride is used with the following edits in the NAACCR Metafile of the EDITS software:
      Diagnostic Confirmation, Histology ICDO2 (SEER IF48)
      Diagnostic Confirmation, Histology ICDO3 (SEER IF48)
Rationale
Some edits check for code combinations that are possible, but quite rare. If the code combination generates an error message and review of the case indicates that the codes are correct for the case, then the over-ride flag is used to skip the edit in the future. See Chapter IV, Recommended Data Edits and Software Coordination of Standards.

Over-ride Flag as Used in the EDITS Software Package

Edits of the type Diagnostic Confirmation, Histology differ in use of ICD-O-2 or ICD-O-3 and check the following:
  1. Since lymphoma and leukemia are almost exclusively microscopic diagnoses, this edit forces review of any cases of lymphoma that have diagnostic confirmation of direct visualization or clinical, and any leukemia with a diagnostic confirmation of direct visualization.
  2. If histology = 9590-9717 for ICD-O-2 or 9590-9729 for ICD-O-3 (lymphoma) then Diagnostic Confirmation cannot be 6 (direct visualization) or 8 (clinical).
  3. If histology = 9720-9941 for ICD-O-2 or 9731-9948 for ICD-O-3 (leukemia and other) then Diagnostic Confirmation cannot be 6 (direct visualization).
Instructions for Coding
  • Leave blank if the program does not generate an error message for the edits of the type Diagnostic Confirmation, Histology.
  • Leave blank and correct any errors for the case if an item is discovered to be incorrect.
  • If the edit produces an error or warning message, verify that the ICD-O-2 or ICD-O-3 histology and diagnostic confirmation are correctly coded. Remember that positive hematologic findings and bone marrow specimens are included as histologic confirmation (code 1 in Diagnostic Confirmation) for leukemia. Code 1 indicates that a review has taken place and histologic type and diagnostic confirmation are correctly coded.
Codes
BlankNot reviewed or reviewed and corrected
1Reviewed and confirmed as reported
OVER-RIDE REPORT SOURCE
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
20501SEER1902 - 1902
Alternate Name:Type of Reporting Source/Sequence Number Interfield Review (Interfield Edit 04) (Seer #7)
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Some computer edits identify errors. Others indicate possible errors that require manual review for resolution. To eliminate the need to review the same cases repeatedly, over-ride flags have been developed to indicate that data in a record (or records) have been reviewed and, while unusual, are correct.

This over-ride is used with the following edits in the NAACCR Metafile of the EDITS software:
      Type of Rep Srce(DC), Seq Num--Cent, ICDO2 (SEER IF04)
      Type of Rep Srce(DC), Seq Num--Cent, ICDO3 (SEER IF04)


 

Rationale
Some edits check for code combinations that are possible, but quite rare. If the code combination generates an error message and review of the case indicates that the codes are correct for the case, then the over-ride flag is used to skip the edit in the future. See Chapter IV, Recommended Date Edits and Software Coordination of Standards.

Over-ride Flag as Used in the EDITS Software Package

Edits of the type 'Type of Rep Srce(DC), Seq Num--Cent' checks that if the case is a death-certificate-only case and the histology is not a lymphoma, leukemia, immunoproliferative or myeloproliferative disease (ICD-O-2 or ICD-O-3 histology is less than 9590), then the tumor sequence number must specify one primary only (sequence '00').

Instructions for Coding
  • Leave blank if the program does not generate an error message for the report source edit.
  • Code 1 if review of type of reporting source, histologic type and tumor sequence number verified that a second or subsequent primary with a reporting source of death-certificate-only has been reviewed and is indeed an independent primary.
Codes
BlankNot reviewed or reviewed and corrected
1Reviewed and confirmed as reported
OVER-RIDE SEQNO/DXCONF
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
20001SEER1897 - 1897
Alternate Name:Sequence Number/Diagnostic Confirmation Interfield Review (Interfield Edit 23)
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Some computer edits identify errors. Others indicate possible errors that require manual review for resolution. To eliminate the need to review the same cases repeatedly, over-ride flags have been developed to indicate that data in a record (or records) have been reviewed and, while unusual, are correct.

This over-ride is used with the following edits in the NAACCR Metafile of the EDITS software:
      Diagnostic Confirm, Seq Num--Central (SEER IF23)
Rationale
Some edits check for code combinations that are impossible, but quite rare. If the code combination generates an error message and review of the case indicates that the codes are correct for the case, then the over-ride flag is used to skip the edit in the future. See Chapter IV, Recommended Data Edits and Software Coordination of Standards.

Over-ride Flag as Used in the EDITS Software Package
  • The edit checks if the case is one of multiple primaries and is not microscopically confirmed or has only positive lab test/marker studies (i.e., Diagnostic Confirmation &gt;5) and tumor sequence number &gt;00 (more than one primary).
  • The edit is skipped if the Sequence Number--Central is in the range of 60-99.
Instructions for Coding
  • Leave blank if the program does not generate an error message for the Diagnostic Confirmation and Sequence Number Central edit.
  • Code 1 if the cases have been reviewed and it is verified that there are multiple primaries of specific sites in which at least one diagnosis has not been microscopically confirmed.
Codes
BlankNot reviewed or reviewed and corrected
1Reviewed and confirmed as reported
OVER-RIDE SITE/BEHAVIOR
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
20711SEER19975.11905 - 1905
Alternate Name:Over-ride Flag for Site/Behavior (IF39)
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Some computer edits identify errors. Others indicate possible errors that require manual review for resolution. To eliminate the need to review the same cases repeatedly, over-ride flags have been developed to indicate that data in a record (or records) have been reviewed and, while unusual, are correct.

This over-ride is used with the following edits in the NAACCR Metafile of the EDITS software:
      Primary Site, Behavior Code ICDO2 (SEER IF39)
      Primary Site, Behavior Code ICDO3 (SEER IF39)
Rationale
Some edits check for code combinations that are possible, but quite rare. If the code combination generates an error message and review of the case indicates that the codes are correct for the case, then the over-ride flag is used to skip the edit in the future. See Chapter IV, Recommended Data Edits and Software Coordination of Standards.

Over-ride Flag as Used in the EDITS Software Package

Edits of the type, Primary Site, Behavior Code, require review of the following primary sites with a behavior of in situ (ICD-O-2 or ICD-O-3 behavior = 2):

      C269                Gastrointestinal tract, NOS
      C399                Ill-defined sites within respiratory system
      C559                Uterus, NOS
      C579                Female genital tract, NOS
      C639                Male genital organs, NOS
      C689                Urinary system, NOS
      C729                Nervous system, NOS
      C759                Endocrine gland, NOS
      C760-C768      Ill-defined sites
      C809                Unknown primary site

Since the designation of in situ is very specific and almost always requires microscopic confirmation, ordinarily specific information should also be available regarding the primary site. Conversely, if inadequate information is available to determine a specific primary site, it is unlikely that information about a cancer being in situ is reliable.
If an in situ diagnosis is stated, try to obtain a more specific primary site. A primary site within an organ system can sometimes be identified based on the diagnostic procedure or treatment given or on the histologic type. If no more specific site can be determined, it is usually preferable to code a behavior code of 3. In the exceedingly rare situation in which it is certain that the behavior is in situ and no more specific site code is applicable, set Over-ride Site/Behavior to 1.
Instructions for Coding
  • Leave blank if the program does not generate an error message for the edit Primary Site, Behavior Code ICDO2 (SEER IF39) and/or the edit Primary Site, Behavior Code ICDO3 (SEER IF39).
  • Leave blank and correct any errors for the case if an item is discovered to be incorrect.
  • Code 1 if review of site and behavior verifies that the patient has an in situ cancer of a nonspecific site and no further information about the primary site is available.
Codes
1Reviewed and confirmed as reported
BlankNot reviewed or reviewed and corrected
Note: The IF 39 edit does not allowin situcases of nonspecific sites, such as gastrointestinal tract, NOS; uterus, NOS; female genital tract, NOS; male genital organs, NOS; and others. The over-ride indicates that the conflict has been reviewed.
OVER-RIDE SITE/EOD/DX DT
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
20721SEER19975.11906 - 1906
Alternate Name:Over-ride Flag for Site/EOD/Diagnosis Date (IF40) (SEER #13)
Over-ride Flag for Site/CS Extension/Diagnosis Date (IF176)
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Some computer edits identify errors. Others indicate possible errors that require manual review for resolution. To eliminate the need to review the same cases repeatedly, over-ride flags have been developed to indicate that data in a record (or records) have been reviewed and, while unusual, are correct.

This over-ride is used with the following edits in the NAACCR Metafile of the EDITS software:
      Primary Site, EOD, ICDO2 (SEER IF40)
      Primary Site, EOD, ICDO3 (SEER IF40)
      Primary Site, CS Extension (SEER IF 176)
Rationale
Some edits check for code combinations that are possible, but quite rare. If the code combination generates an error message and review of the case indicates that the codes are correct for the case, then the over-ride flag is used to skip the edit in the future. See Chapter IV, Recommended Data Edits and Software Coordination of Standards.

Over-ride Flag as Used in the EDITS Software Package

Edits of this type Primary Site, EOD do not allow “localized” disease with nonspecific sites, such as mouth, NOS; colon, NOS (except ICD-O-2 or ICD-O-3 histology 8210, 8220, 8261, or 8263); bone, NOS; female genital system, NOS; male genital organs, NOS; and others.

Instructions for Coding
  • Leave blank if the program does not generate an error message for the edit Primary Site, EOD, ICDO2 (SEER IF40) and/or the edit Primary Site, EOD, ICDO3 (SEER IF40).
  • Code 1 if the case has been reviewed and it has been verified that the patient had “localized” disease with a nonspecific site and no further information about the primary site is available.
Codes
BlankNot reviewed or reviewed and corrected
1Reviewed and confirmed as reported
OVER-RIDE SITE/LAT/EOD
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
20731SEER19975.11907 - 1907
Alternate Name:Over-ride Flag for Site/Laterality/CS Extension (IF177)
Over-ride Flag for Site/Laterality/EOD (IF41)
XML NAACCR ID:
XML PARENT ELEMENT:
Description

Some computer edits identify errors. Others indicate possible errors that require manual review for resolution. To eliminate the need to review the same cases repeatedly, over-ride flags have been developed to indicate that data in a record (or records) have been reviewed and, while unusual, are correct.

This over-ride is used with the following edits in the NAACCR Metafile of the EDITS software:
      Primary Site, Laterality, EOD, ICDO2 (SEER IF41)
      Primary Site, Laterality, EOD, ICDO3 (SEER IF41)
      Primary Site, Laterality, CS Extension (SEER IF177)

Rationale
Some edits check for code combinations that are possible, but quite rare. If the code combination generates an error message and review of the case indicates that the codes are correct for the case, then the over-ride flag is used to skip the edit in the future. See Chapter IV, Recommended Data Edits and Software Coordination of Standards.

Over-ride Flag as Used in the EDITS Software Package

Edits of this type Primary Site, Laterality, EOD apply to paired organs and do not allow EOD to be specified as in situ, localized, or regional by direct extension if laterality is coded as “bilateral, site unknown,” or “laterality unknown.”

Instructions for Coding
  • Leave blank if the program does not generate an error message for the edit Primary Site, Laterality, EOD, ICDO2 (SEER IF41) and/or Primary Site, Laterality, EOD, ICDO3 (SEER IF41).
  • Code 1 if the case has been reviewed and it has been verified that the patient had laterality coded nonspecifically and EOD coded specifically.
Codes
1Reviewed and confirmed as reported
BlankNot reviewed or reviewed and corrected
OVER-RIDE SITE/LAT/MORPH
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
20741SEER19975.11908 - 1908
Alternate Name:Over-ride Flag for Site/Laterality/Morphology (IF42)
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Some computer edits identify errors. Others indicate possible errors that require manual review for resolution. To eliminate the need to review the same cases repeatedly, over-ride flags have been developed to indicate that data in a record (or records) have been reviewed and, while unusual, are correct.

This over-ride is used with the following edits in the NAACCR Metafile of the EDITS software:
      Laterality, Primary Site, Morph ICDO2 (SEER IF42)
      Laterality, Primary Site, Morph ICDO3 (SEER IF42)
Rationale
Some edits check for code combinations that are possible, but quite rare. If the code combination generates an error message and review of the case indicates that the codes are correct for the case, then the over-ride flag is used to skip the edit in the future. See Chapter IV, Recommended Data Edits and Software Coordination of Standards.

Over-ride Flag as Used in the EDITS Software Package

Edits of the type Laterality, Primary Site, Morph differ in use of ICD-O-2 or ICD-O-3 morphology and do the following:
  1. If the Primary Site is a paired organ and ICD-O-2 or ICD-O-3 behavior is in situ (2), then laterality must be 1, 2, or 3.
  2. If diagnosis year less than 1988 and ICD-O-2 or ICD-O-3 histology = 9590, no further editing is performed.
  3. If diagnosis year greater than 1987 and ICD-O-2 or ICD-O-3 histology = 9140, 9700, 9701, 9590-9980, no further editing is performed.
The intent of this edit is to force review of in situ cases for which laterality is coded 4 (bilateral) or 9 (unknown laterality) as to origin.In rare instances when the tumor is truly midline (9) or the rare combination is otherwise confirmed correct, enter a code 1 for Override Site/Lat/Morph.

Instructions for Coding
  • Leave blank if the program does not generate an error message for the edit Laterality, Primary site, Morph ICDO2 (SEER IF 42) and/or the edit Laterality, Primary site, Morph ICDO3 (SEER IF42).
  • Leave blank and correct any errors for the case if an item is discovered to be incorrect.
  • Code 1 if review of site, laterality and morphology verifies that the case had behavior code of “in situ” and laterality is not stated as “right: origin of primary;” “left: origin of primary;” or “only one side involved, right or left origin not specified”.
Codes
BlankNot reviewed or reviewed and corrected
1Reviewed and confirmed as reported
OVER-RIDE SITE/LAT/SEQNO
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
20101SEER1898 - 1898
Alternate Name:Site/Histology/Laterality/Sequence Number Interrecord Review (Interrecord Edit 09)
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Some computer edits identify errors. Others indicate possible errors that require manual review for resolution. To eliminate the need to review the same cases repeatedly, over-ride flags have been developed to indicate that data in a record (or records) have been reviewed and, while unusual, are correct.

This over-ride is used with the following Interrecord Edit from the SEER Program:          Verify Same Primary Not Reported Twice for a Person (SEER IR09)

Presently, documentation on interrecord edits is not included in the EDITS software.

Rationale
Some edits check for code combinations that are possible, but quite rare. If the code combination generates an error message and review of the case indicates that the codes are correct for the case, then the over-ride flag is used to skip the edit in the future. See Chapter IV, Recommended Data Edits and Software Coordination of Standards.

Over-ride Flag as Used in the EDITS Software Package

Verify Same Primary Not Reported Twice for a Person (SEER IR09) applies to paired organs and does not allow two cases with the same primary site group, laterality and three digit histology code. This edit verifies that the same primary is not reported twice for a person.Instructions for Coding
  • Leave blank if the program does not generate an error message for the edit Verify Same Primary Not Reported Twice for a Person (SEER IR09).
  • Code 1 if the case has been reviewed and it has been verified that the patient had multiple primaries of the same histology (3 digit) in the same primary site group.
Codes
1Reviewed and confirmed as reported
BlankNot reviewed or reviewed and corrected
OVER-RIDE SITE/TNM-STGGRP
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
19891CoC200191895 - 1895
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Some computer edits identify errors. Others indicate possible errors that require manual review for resolution. To eliminate the need to review the same cases repeatedly, over-ride flags have been developed to indicate that data in a record (or records) have been reviewed and, while unusual, are correct.

This over-ride is used with the following edits in the NAACCR Metafile of the EDITS software:
        Primary Site, AJCC Stage Group - Ed 6, (NAACCR)
          Primary Site, AJCC Stage Group - Ed 6, ICDO3 (CoC)
          Primary Site, AJCC Stage Group - Ed 7, ICDO3 (CoC)
          Primary Site, AJCC Stage Group - Ed 7, ICDO3 (NPCR)
Rationale
Some edits check for code combinations that are possible, but quite rare. If the code combination generates an error message and review of the case indicates that the codes are correct for the case, then the override flag is used to skip the edit in the future. See Chapter IV, Recommended Data Edits and Software Coordination of Standards.

Over-ride Flag as Used in the EDITS Software Package

Edits of the type Primary Site, AJCC Stage Group - Ed 6 and Primary Site, AJCC Stage Group - Ed 7 check that the pathologic and clinical AJCC stage group codes are valid for the site and histology group according to the AJCC Cancer Staging Manual Sixth Edition and AJCC Cancer Staging Manual Seventh Edition, using the codes described for the items TNM Clin Stage Group [970] and TNM Path Stage Group [910]. Combinations of site and histology not represented in any AJCC schema must be coded 88. Unknown stage groups must be coded 99. Blanks are not permitted.

Since pediatric cancers whose sites and histologies have an AJCC scheme may be coded according to a pediatric scheme instead, Override Site/TNM-Stage Group is used to indicate pediatric cases not coded according to the AJCC manual. Pediatric Stage groups should not be recorded in the TNM Clin Stage Group or TNM Path Stage Group items. When neither clinical nor pathologic AJCC staging is used for pediatric cases, code all AJCC items 88. When any components of either is used to stage a pediatric case, follow the instructions for coding AJCC items and leave Override Site/TNM-Stage Group blank.

Instructions for Coding
  • Leave blank if the program does not generate an error message for the edits of the type Primary Site, AJCC Stage Group - Ed 6 and Primary Site, AJCC Stage Group - Ed 7.
  • Leave blank and correct any errors for the case if an item is discovered to be incorrect.
  • Code 1 if the case is confirmed to be a pediatric case that was coded using a pediatric coding system.
Codes
BlankNot reviewed or reviewed and corrected
1Reviewed and confirmed as reported
OVER-RIDE SITE/TYPE
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
20301SEER1900 - 1900
Alternate Name:Site/Type Interfield Review (Interfield Edit 25)
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Some computer edits identify errors. Others indicate possible errors that require manual review for resolution. To eliminate the need to review the same cases repeatedly, over-ride flags have been developed to indicate that data in a record (or records) have been reviewed and, while unusual, are correct.

This over-ride is used with the following edits in the NAACCR Metafile of the EDITS software:
      Primary Site, Morphology-Type ICDO2 (CoC)
      Primary Site, Morphology-Type ICDO3 (CoC)
      Primary Site, Morphology-Type ICDO2 (SEER IF25)
      Primary Site, Morphology-Type ICDO3 (SEER IF25)
      Primary Site, Morphology-Type, Behavior ICDO3 (SEER IF25)
      Primary Site, Morphology-Type, Behavior ICDO3 (CoC)
Rationale
Some edits check for code combinations that are possible, but quite rare. If the code combination generates an error message and review of the case indicates that the codes are correct for the case then the over-ride flag is used to skip the edit in the future. See Chapter IV, Recommended Data Edits and Software Coordination of Standards.

Over-ride Flag as Used in the EDITS Software Package

Multiple versions of edits of the type Primary site, Morphology-Type check for "usual" combinations of site and ICD-O-2 or ICD-O-3 histology. The SEER version of the edit is more restrictive than the CoC edit, and thus uses a different over-ride flag. The CoC version of the edit will accept Over-ride CoC-Site/Type or Over-ride Site/Type as equivalent.
  1. The Site/Histology validation list (available on the SEER web site) contains those histologies commonly found in the specified primary site. Histologies that occur only rarely or never are not included. These edits require review of all combinations not listed.
  2. Since basal and squamous cell carcinomas of non-genital skin sites are not reportable to SEER, these site/histology combinations do not appear on the SEER validation list. For the CoC version of the edit, if Primary Site is in the range C440-C449 (skin), and ICD-O-2 histology is in the range 8000-8004 (neoplasms, malignant, NOS), 8010-8045 (epithelial carcinomas), 8050-8082 (papillary and squamous cell carcinomas), or 8090-8110 (basal cell carcinomas), or ICD-O-3 histology is in the range 8000-8005 (neoplasms, malignant, NOS), 8010-8046 (epithelial carcinomas), 8050-8084 (papillary and squamous cell carcinomas), or 8090-8110 (basal cell carcinomas), no further editing is done. No over-ride is necessary for these cases in the CoC version of the edit.
Review of these cases requires investigating whether a) the combination is biologically implausible, or b) there are cancer registry coding conventions that would dictate different codes for the diagnosis. Review of these rare combinations often results in changes to the primary site and/or morphology, rather than a decision that the combination is correct.

Instructions for Coding
  • Leave blank if the program does not generate an error message for the edits of the type Primary Site, Morphology-Type.
  • Leave blank and correct any errors for the case if an item is discovered to be incorrect.
  • Code 1 if the case has been reviewed and both the site and histology are correct.
Codes
1Reviewed and confirmed as reported
BlankNot reviewed or reviewed and corrected
OVER-RIDE SS/NODESPOS
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
19811NAACCR200191888 - 1888
Alternate Name:Over-ride Summary Stage/Nodes Positive
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Some computer edits identify errors. Others indicate possible errors that require manual review for resolution. To eliminate the need to review the same cases repeatedly, over-ride flags have been developed to indicate that data in a record (or records) have been reviewed and, while unusual, are correct.

This over-ride is used with the following edits in the NAACCR Metafile of the EDITS software:
      Summary Stage 1977, Regional Nodes Pos (NAACCR)
      Summary Stage 2000, Regional Nodes Pos (NAACCR)
Rationale
Some edits check for code combinations that are possible, but quite rare. If the code combination generates an error or warning message and review of the case indicates that the codes are correct for the case, then the over-ride flag is used to skip the edit in the future. See Chapter IV, Recommended Data Edits and Software Coordination of Standards.

Over-ride Flag as Used in the EDITS Software Package

The edit Summary Stage 1977, Regional Nodes Pos (NAACCR) checks SEER Summary Stage 1977 against Regional Nodes Positive and generates an error or warning if there is an incompatibility between the two data items. The edit Summary Stage 2000, Regional Nodes Pos (NAACCR) checks SEER Summary Stage 2000 against Regional Nodes Positive and generates an error or warning if there is an incompatibility between the two data items.

Instructions for Coding
  • Leave blank if the program does not generate an error message for the edit Summary Stage 1977, Regional Nodes Pos (NAACCR) or the edit Summary Stage 2000, Regional Nodes Pos (NAACCR).
  • Leave blank and correct any errors for the case if an item is discovered to be incorrect.
  • Code 1 if the case has been reviewed and it has been verified that the case has both SEER Summary Stage 1977 and Nodes Positive coded correctly or SEER Summary Stage 2000 and Nodes Positive coded correctly.
Codes
1Reviewed and confirmed as reported
BlankNot reviewed or reviewed and corrected
OVER-RIDE SS/TNM-M
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
19831NAACCR200191890 - 1890
Alternate Name:Over-ride Summary Stage/TNM-M
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Some computer edits identify errors. Others indicate possible errors that require manual review for resolution. To eliminate the need to review the same cases repeatedly, over-ride flags have been developed to indicate that data in a record (or records) have been reviewed and, while unusual, are correct.

This over-ride is used with the following edits in the NAACCR Metafile of the EDITS software:
      Summary Stage 1977, TNM-M (NAACCR)
      Summary Stage 2000, TNM-M (NAACCR)
Rationale
Some edits check for code combinations that are possible, but quite rare. If the code combination generates an error or warning message and review of the case indicates that the codes are correct for the case, then the over-ride flag is used to skip the edit in the future. See Chapter IV, Recommended Data Edits and Software Coordination of Standards.

Over-ride Flag as Used in the EDITS Software Package

The edit Summary Stage 1977, TNM-M (NAACCR) checks the SEER Summary Stage 1977 against the TNM-M and generates a warning if the SEER Summary Stage 1977 is ‘distant’ and the TNM-M is ‘0’. (TNM-M is derived from TNM Path M and TNM Clin M, with TNM Path M having precedence.) It also checks if the SEER Summary Stage 1977 is not ‘distant’ and the TNM-M is greater than or equal to ‘1’ and generates an error or a warning. The edit Summary Stage 2000, TNM-M (NAACCR) checks the SEER Summary Stage 2000 against the TNM-M and generates a warning if the SEER Summary Stage 2000 is ‘distant’ and the TNM-M is ‘0’. It also checks if the SEER Summary Stage 2000 is not ‘distant’ and the TNM-M is greater than or equal to ‘1’ and generates an error or a warning.

Instructions for Coding
  • Leave blank if the program does not generate an error message for the edit Summary Stage 1977, TNM-M (NAACCR) or the edit Summary Stage 2000, TNM-M (NAACCR).
  • Leave blank and correct any errors for the case if an item is discovered to be incorrect.
  • Code 1 if the case has been reviewed and it has been verified that both SEER Summary Stage 1977 and TNM-M have been coded correctly or that SEER Summary Stage 2000 and TNM-M have been coded correctly.
Codes
1Reviewed and confirmed as reported
BlankNot reviewed or reviewed and corrected
OVER-RIDE SS/TNM-N
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
19821NAACCR1889 - 1889
Alternate Name:Over-ride Summary Stage/TNM-N
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Some computer edits identify errors. Others indicate possible errors that require manual review for resolution. To eliminate the need to review the same cases repeatedly, over-ride flags have been developed to indicate that data in a record (or records) have been reviewed and, while unusual, are correct.

This over-ride is used with the following edits in the NAACCR Metafile of the EDITS software:
      Summary Stage 1977, TNM-N (NAACCR)
      Summary Stage 2000, TNM-N (NAACCR)
Rationale
Some edits check for code combinations that are possible, but quite rare. If the code combination generates an error message and review of the case indicates that the codes are correct for the case, then the over-ride flag is used to skip the edit in the future. See Chapter IV, Recommended Data Edits and Software Coordination of Standards.

Over-ride Flag as Used in the EDITS Software Package

The edit Summary Stage 1977, TNM-N (NAACCR) checks SEER Summary Stage 1977 against the TNM-N and generates an error if the SEER Summary Stage 1977 indicates regional nodal involvement and the TNM-N does not. (TNM-N is derived from TNM Path N and TNM Clin N, with TNM Path N having precedence.) It also generates an error if the SEER Summary Stage 1977 is ‘in situ’ or ‘localized’ and the TNM-N is greater than or equal to ‘1’. The edit Summary Stage 2000, TNM-N (NAACCR) checks SEER Summary Stage 2000 against the TNM-N and generates an error if the SEER Summary Stage 2000 indicates regional nodal involvement and the TNM-N does not. It also generates an error if the SEER Summary Stage 2000 is ‘in situ’ or ‘localized’ and the TNM-N is greater than or equal to ‘1’.

Instructions for Coding
  • Leave blank if the program does not generate an error message for the edit Summary Stage 1977, TNM-N (NAACCR) or the edit Summary Stage 2000, TNM-N (NAACCR).
  • Leave blank and correct any errors for the case if an item is discovered to be incorrect.
  • Code 1 if the case has been reviewed and it has been verified that both SEER Summary Stage 1977 and TNM-N or both SEER Summary Stage 2000 and TNM-N have been coded correctly.
Codes
BlankNot reviewed or reviewed and corrected
1Reviewed and confirmed as reported
OVER-RIDE SURG/DXCONF
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
20201SEER1899 - 1899
Alternate Name:Surgery/Diagnostic Confirmation Interfield Review (Interfield Edit 46)
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Some computer edits identify errors. Others indicate possible errors that require manual review for resolution. To eliminate the need to review the same cases repeatedly, over-ride flags have been developed to indicate that data in a record (or records) have been reviewed and, while unusual, are correct.

This over-ride is used with the following edits in the NAACCR Metafile of the EDITS software:
      RX Summ--Surg Prim Site, Diag Conf (SEER IF76)
      RX Summ--Surg Site 98-02, Diag Conf (SEER IF106)
      RX Summ--Surgery Type, Diag Conf (SEER IF46)
Rationale
Some edits check for code combinations that are possible, but quite rare. If the code combination generates an error message and review of the case indicates that the codes are correct for the case, then the over-ride flag is used to skip the edit in the future. See Chapter IV, Recommended Data Edits and Software Coordination of Standards.

Over-ride Flag as Used in the EDITS Software Package
Edits of the type RX Summ--Surg Prim Site, Diag Conf check that cases with a primary site surgical procedure coded 20-90 are histologically confirmed.If the patient had a surgical procedure, most likely there was a microscopic examination of the cancer. Verify the surgery and diagnostic confirmation codes, and correct any errors. Sometimes there are valid reasons why no microscopic confirmation is achieved with the surgery; for example, the tissue removed may be inadequate for evaluation.

Instructions for Coding
  • Leave blank if the program does not generate an error message for edits of the type, RX Summ--Surg Prim Site, Diag Conf.
  • Leave blank and correct any errors for the case if an item is discovered to be incorrect.
  • Code 1 if review confirms that they are correct. The patient had surgery, but the tissue removed was not sufficient for microscopic confirmation.
Codes
BlankNot reviewed or reviewed and corrected
1Reviewed and confirmed as reported
PATH DATE SPEC COLLECT 1
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
732014HL72010124580 - 4593
Alternate Name:OBR-7 Observation Date/Time #00241 (HL7)
Path--Date Spec Collection
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Records the date and time the specimen for the report on the cancer  was collected, not the date read, interpreted or typed.
 
This is a field to record when specimens are collected; can be used as approximate date of diagnosis in absence of other information. HL7 OBR-7 records the date and time (YYYYMMDDHHMMSS). NAACCR records the date (YYYYMMDD).
 
This data item accommodates only one path report. If additional reports were prepared, enter the date specimen collected in Path Date Spec Collect 2 through Path Date Spec Collect 5 [7321 - 7324]. Information in this data item should refer to the path report described in data items 7010, 7090, 7100, 7190 and 7480.
Rationale
Cancer registries collect cancer information from various sources including pathology laboratories. Pathology reports of different types may be sent via HL7 messages. Included here are data items coming from such a message to be included in the cancer registry database to aid in consolidating a cancer case when there is information from multiple sources. Traditionally, these data items were not part of the NAACCR Standards Volume II record layout and therefore provide a link to NAACCR Standards Volume V. http://www.naaccr.org/standardsandregistryoperations/volumev.aspx
PATH DATE SPEC COLLECT 2
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
732114HL72010124686 - 4699
Alternate Name:Path--Date Spec Collection
OBR-7 Observation Date/Time #00241 (HL7)
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Records the date and time the specimen for the report on the cancer was collected, not the date read, interpreted or typed.

This data item accommodates only one path report; if additional path reports were prepared, enter the date the specimen was collected in Path Date Spec Collect No 3 through Path Date Spec Collect No 5 [7322-7324]. Information in this data item should refer to the path report described in data items 7011, 7091, 7101, 7191, and 7481.
 
This is a field to record when specimens are collected; can be used as approximate date of diagnosis in absence of other information. HL7 OBR-7 records the date and time (YYYYMMDDHHMMSS). NAACCR records the date (YYYYMMDD).
Rationale
Cancer registries collect cancer information from various sources including pathology laboratories. Pathology reports of different types may be sent via HL7 messages. Included here are data items coming from such a message to be included in the cancer registry database to aid in consolidating a cancer case when there is information from multiple sources. Traditionally, these data items were not part of the NAACCR Standards Volume II record layout and therefore provide a link to NAACCR Standards Volume V. http://www.naaccr.org/standardsandregistryoperations/volumev.aspx
PATH DATE SPEC COLLECT 3
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
732214HL72010124792 - 4805
Alternate Name:OBR-7 Observation Date/Time #00241 (HL7)
Path--Date Spec Collection
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Records the date and time the specimen for the report on the cancer was collected, not the date read, interpreted or typed.
 
This is a field to record when specimens are collected; can be used as approximate date of diagnosis in absence of other information. HL7 OBR-7 records the date and time (YYYYMMDDHHMMSS). NAACCR records the date (YYYYMMDD).

This data item accommodates only one path report; if additional path reports were prepared, enter the date the specimen was collected in Path Date Spec Collect No 4 through Path Date Spec Collect No 5 [7323-7324]. Information in this data item should refer to the path report described in data items 7012, 7092, 7102, 7192, and 7482.

Rationale
Cancer registries collect cancer information from various sources including pathology laboratories. Pathology reports of different types may be sent via HL7 messages. Included here are data items coming from such a message to be included in the cancer registry database to aid in consolidating a cancer case when there is information from multiple sources. Traditionally, these data items were not part of the NAACCR Standards Volume II record layout and therefore provide a link to NAACCR Standards Volume V. http://www.naaccr.org/standardsandregistryoperations/volumev.aspx
PATH DATE SPEC COLLECT 4
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
732314HL72010124898 - 4911
Alternate Name:Path--Date Spec Collection
OBR-7 Observation Date/Time #00241 (HL7)
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Records the date and time the specimen for the report on the cancer was collected, not the date read, interpreted or typed.
 
This is a field to record when specimens are collected; can be used as approximate date of diagnosis in absence of other information. HL7 OBR-7 records the date and time (YYYYMMDDHHMMSS). NAACCR records the date (YYYYMMDD).
 
This data item accommodates only one path report; if additional path reports were prepared, enter the date the specimen was collected in Path Date Spec Collect No 5 [7324]. Information in this data item should refer to the path report described in data items 7013, 7093, 7103, 7193, and 7483.
Rationale
Cancer registries collect cancer information from various sources including pathology laboratories. Pathology reports of different types may be sent via HL7 messages. Included here are data items coming from such a message to be included in the cancer registry database to aid in consolidating a cancer case when there is information from multiple sources. Traditionally, these data items were not part of the NAACCR Standards Volume II record layout and therefore provide a link to NAACCR Standards Volume V. http://www.naaccr.org/standardsandregistryoperations/volumev.aspx
PATH DATE SPEC COLLECT 5
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
732414HL72010125004 - 5017
Alternate Name:OBR-7 Observation Date/Time #00241 (HL7)
Path--Date Spec Collection
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Records the date and time the specimen for the report on the cancer was collected, not the date read, interpreted or typed.
 
This is a field to record when specimens are collected; can be used as approximate date of diagnosis in absence of other information. HL7 OBR-7 records the date and time (YYYYMMDDHHMMSS). NAACCR records the date (YYYYMMDD).

This data item accommodates only one path report. Information in this data item should refer to the path report described in data items 7014, 7094, 7104, 7194, and 7484.

Rationale
Cancer registries collect cancer information from various sources including pathology laboratories. Pathology reports of different types may be sent via HL7 messages. Included here are data items coming from such a message to be included in the cancer registry database to aid in consolidating a cancer case when there is information from multiple sources. Traditionally, these data items were not part of the NAACCR Standards Volume II record layout and therefore provide a link to NAACCR Standards Volume V. http://www.naaccr.org/standardsandregistryoperations/volumev.aspx
PATH ORDER PHYS LIC NO 1
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
710020HL72010124621 - 4640
Alternate Name:OBR-16 Ordering Provider (License Number) #00226
Path Ordering Client/Phys--Lic No.
XML NAACCR ID:
XML PARENT ELEMENT:
Description
License number of physician submitting specimens for the first path report.

This data item accommodates only one path report. If additional reports were prepared, enter the license number of physician in Path Order Phys Lic No 2 through Path Order Phys Lic No 5 [7101-7104]. Information in this data item should refer to the path report described in data items 7010, 7090, 7190, 7320, and 7480.
Rationale
Cancer registries collect cancer information from various sources including pathology laboratories. Pathology reports of different types may be sent via HL7 messages. Included here are data items coming from such a message to be included in the cancer registry database to aid in consolidating a cancer case when there is information from multiple sources. Traditionally, these data items were not part of the NAACCR Standards Volume II record layout and therefore provide a link to NAACCR Standards Volume V. http://www.naaccr.org/standardsandregistryoperations/volumev.aspx
PATH ORDER PHYS LIC NO 2
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
710120HL72010124727 - 4746
Alternate Name:Path Ordering Client/Phys--Lic No.
OBR-16 Ordering Provider (License Number) #00226
XML NAACCR ID:
XML PARENT ELEMENT:
Description
License number of physician submitting specimens for the second path report.

This data item accommodates only one path report; if additional path reports were prepared, enter the license number of physician in Path Order Phys Lic No 3 through Path Order Phys Lic No 5 [7102-7104]. Information in this data item should refer to the path report described in data items 7011, 7091, 7191, 7321, and 7481.
Rationale
Cancer registries collect cancer information from various sources including pathology laboratories. Pathology reports of different types may be sent via HL7 messages. Included here are data items coming from such a message to be included in the cancer registry database to aid in consolidating a cancer case when there is information from multiple sources. Traditionally, these data items were not part of the NAACCR Standards Volume II record layout and therefore provide a link to NAACCR Standards Volume V. http://www.naaccr.org/standardsandregistryoperations/volumev.aspx
PATH ORDER PHYS LIC NO 3
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
710220HL72010124833 - 4852
Alternate Name:OBR-16 Ordering Provider (License Number) #00226
Path Ordering Client/Phys--Lic No.
XML NAACCR ID:
XML PARENT ELEMENT:
Description
License number of physician submitting specimens for the third path report.

This item accommodates only one path report; if additional path reports were prepared, enter the license number of physician in Path Order Phys Lic No 4 through Path Order Phys Lic No 5 [7103-7104]. Information in this data item should refer to the path report described in data items 7012, 7022, 7192, 7322, and 7482.
Rationale
Cancer registries collect cancer information from various sources including pathology laboratories. Pathology reports of different types may be sent via HL7 messages. Included here are data items coming from such a message to be included in the cancer registry database to aid in consolidating a cancer case when there is information from multiple sources. Traditionally, these data items were not part of the NAACCR Standards Volume II record layout and therefore provide a link to NAACCR Standards Volume V. http://www.naaccr.org/standardsandregistryoperations/volumev.aspx
PATH ORDER PHYS LIC NO 4
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
710320HL72010124939 - 4958
Alternate Name:Path Ordering Client/Phys--Lic No.
OBR-16 Ordering Provider (License Number) #00226
XML NAACCR ID:
XML PARENT ELEMENT:
Description
License number of physician submitting specimens for the fourth path report.

This data item accommodates only one path report; if an additional path report was prepared, enter the license number of physician in Path Order Phys Lic No 5 [7104]. Information in this data item should refer to the path report described in data items 7013, 7023, 7193, 7323, and 7483.
Rationale
Cancer registries collect cancer information from various sources including pathology laboratories. Pathology reports of different types may be sent via HL7 messages. Included here are data items coming from such a message to be included in the cancer registry database to aid in consolidating a cancer case when there is information from multiple sources. Traditionally, these data items were not part of the NAACCR Standards Volume II record layout and therefore provide a link to NAACCR Standards Volume V. http://www.naaccr.org/standardsandregistryoperations/volumev.aspx
PATH ORDER PHYS LIC NO 5
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
710420HL72010125045 - 5064
Alternate Name:
XML NAACCR ID:
XML PARENT ELEMENT:
Description
License number of physician submitting specimens for the fifth path report.

Information in this data item should refer to the path report described in data items 7014, 7024, 7194, 7324, and 7484.
Rationale
Cancer registries collect cancer information from various sources including pathology laboratories. Pathology reports of different types may be sent via HL7 messages. Included here are data items coming from such a message to be included in the cancer registry database to aid in consolidating a cancer case when there is information from multiple sources. Traditionally, these data items were not part of the NAACCR Standards Volume II record layout and therefore provide a link to NAACCR Standards Volume V. http://www.naaccr.org/standardsandregistryoperations/volumev.aspx
PATH ORDERING FAC NO 1
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
719025HL72010124596 - 4620
Alternate Name:ORC-21 Ordering Facility Name #01311 (HL7)
Path Ordering Facility Number (AHA Number)
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Facility ID number of the facility where the specimen described in the first path report was removed/collected.

Use the National Provider Identifier (NPI) if possible. Otherwise, use a number defined by the American Hospital Association (AHA), or some other standard-setting organization such as the American College of Surgeons (ACoS) or Clinical Laboratory Improvement Amendments (CLIA).

This item accommodates only one path report; if additional path reports were prepared, enter the facility ID number(s) in Path Ordering Fac No 2 through Path Ordering Fac No 5 [7191-7194]. Information in this data item should refer to the path report described in data items 7010, 7090, 7100, 7320, and 7480.
Rationale
The facility where the specimen was obtained is most likely the location of the medical record for the patient as well as any residual tissue.

Cancer registries collect cancer information from various sources including pathology laboratories. Pathology reports of different types may be sent via HL7 messages. Included here are data items coming from such a message to be included in the cancer registry database to aid in consolidating a cancer case when there is information from multiple sources. Traditionally, these data items were not part of the NAACCR Standards Volume II record layout and therefore provide a link to NAACCR Standards Volume V. http://www.naaccr.org/standardsandregistryoperations/volumev.aspx
PATH ORDERING FAC NO 2
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
719125HL72010124702 - 4726
Alternate Name:Path Ordering Facility Number (AHA Number)
ORC-21 Ordering Facility Name #01311 (HL7)
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Facility ID number of the facility where the specimen described in the second path report was removed/collected. Use the National Provider Identifier (NPI) if possible. Otherwise, use a number defined by the American Hospital Association (AHA), or some other standard-setting organization such as the American College of Surgeons (ACoS) or Clinical Laboratory Improvement Amendments (CLIA).This item accommodates only one path report; if additional path reports were prepared, enter the facility ID number(s) in Path Ordering Fac No 3 through Path Ordering Fac No 5 [7192-7194]. Information in this data item should refer to the path report described in data items 7011, 7091, 7101, 7321, and 7481.
Rationale
The facility where the specimen was obtained is most likely the location of the medical record for the patient as well as any residual tissue.

Cancer registries collect cancer information from various sources including pathology laboratories. Pathology reports of different types may be sent via HL7 messages. Included here are data items coming from such a message to be included in the cancer registry database to aid in consolidating a cancer case when there is information from multiple sources. Traditionally, these data items were not part of the NAACCR Standards Volume II record layout and therefore provide a link to NAACCR Standards Volume V. http://www.naaccr.org/standardsandregistryoperations/volumev.aspx
PATH ORDERING FAC NO 3
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
719225HL72010124808 - 4832
Alternate Name:ORC-21 Ordering Facility Name #01311 (HL7)
Path Ordering Facility Number (AHA Number)
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Facility ID number of the facility where the specimen described in the third path report was removed/collected.

Use the National Provider Identifier (NPI) if possible. Otherwise, use a number defined by the American Hospital Association (AHA), or some other standard-setting organization such as the American College of Surgeons (ACoS) or Clinical Laboratory Improvement Amendments (CLIA).

This item accommodates only one path report; if additional path reports were prepared, enter the facility ID number(s) in Path Ordering Fac No 4 through Path Ordering Fac No 5 [7193-7194]. Information in this data item should refer to the path report described in data items 7012, 7092, 7102, 7322, and 7482.
Rationale
The facility where the specimen was obtained is most likely the location of the medical record for the patient as well as any residual tissue.

Cancer registries collect cancer information from various sources including pathology laboratories. Pathology reports of different types may be sent via HL7 messages. Included here are data items coming from such a message to be included in the cancer registry database to aid in consolidating a cancer case when there is information from multiple sources. Traditionally, these data items were not part of the NAACCR Standards Volume II record layout and therefore provide a link to NAACCR Standards Volume V. http://www.naaccr.org/standardsandregistryoperations/volumev.aspx
PATH ORDERING FAC NO 4
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
719325HL72010124914 - 4938
Alternate Name:Path Ordering Facility Number (AHA Number)
ORC-21 Ordering Facility Name #01311 (HL7)
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Facility ID number of the facility where the specimen described in the fourth path report was removed/collected.

Use the National Provider Identifier (NPI) if possible. Otherwise, use a number defined by the American Hospital Association (AHA), or some other standard-setting organization such as the American College of Surgeons (ACoS) or Clinical Laboratory Improvement Amendments (CLIA).

This item accommodates only one path report; if an additional path report was prepared, enter the facility ID number in Path Ordering Fac No 5 [7194]. Information in this data item should refer to the path report described in data items 7013, 7093, 7103, 7323, and 7483.
Rationale
The facility where the specimen was obtained is most likely the location of the medical record for the patient as well as any residual tissue.

Cancer registries collect cancer information from various sources including pathology laboratories. Pathology reports of different types may be sent via HL7 messages. Included here are data items coming from such a message to be included in the cancer registry database to aid in consolidating a cancer case when there is information from multiple sources. Traditionally, these data items were not part of the NAACCR Standards Volume II record layout and therefore provide a link to NAACCR Standards Volume V. http://www.naaccr.org/standardsandregistryoperations/volumev.aspx
PATH ORDERING FAC NO 5
Item #LengthSource of StandardYear ImplementedVersion ImplementedYear RetiredVersion RetiredColumn #
719425HL72010125020 - 5044
Alternate Name:ORC-21 Ordering Facility Name #01311 (HL7)
Path Ordering Facility Number (AHA Number)
XML NAACCR ID:
XML PARENT ELEMENT:
Description
Facility ID number of the facility where the specimen described in the fifth path report was removed/collected.

Use the National Provider Identifier (NPI) if possible. Otherwise, use a number defined by the American Hospital Association (AHA), or some other stand