Webbie Mascot

NAACCR Item Lookup

771 items

771 results (showing up to 500)
Data Item NumberData Item NameXML NAACCR IDLengthDescriptionAllowable ValuesAlternate NamesCCCR CollectClarificationCoC CollectCode NotesData Descriptor NoteData Descriptor Table NoteData Dictionary Code NoteData Dictionary Description NoteData Dictionary Rationale NoteData TypeFormatGeneral NotesInstructions for CodingNPCR CollectParent XML ElementRationaleRecord Layout NoteRecord Layout Table NoteRecord TypeRequired Status NoteRequired Status Table NoteSection NameSEER CollectSource of StandardVersion ImplementedVersion RetiredYear ImplementedYear Retired
10Record TyperecordType1Generated field that identifies which of the six NAACCR data exchange record types is being used in a file of data exchange records. A file should have records of only one type.I, C, A, U, M, LR.textRNaaccrDataA,C,I,MRecord ID.NAACCRpre V4
20Patient ID NumberpatientIdNumber8Unique number assigned to an individual patient by the central registry. The central registry will assign this same number to all of the patient’s subsequent tumors (records). Patient ID Number will only differ when multiple central registries accession the same patient. Each central registry will assign their unique Patient ID Number. NAACCR recommends that the registry should not reissue or reuse this number when a patient’s record is deleted from the files. In the transmit file (data exchange) this number will be the Patient ID Number assigned by the sending registry as defined in Registry ID [40].R*.digitsRight justified, zero filledRPatientProvides the central registry with a unique identification number that will link all records (multiple tumors) for the same patient. The unique number also allows the central registry to identify the patient when there are multiple reports from different hospitals.A,C,I,MRecord IDRReporting Registry
21Patient System ID-HosppatientSystemIdHosp8The unique, non-repeating number automatically assigned to patients by the hospital tumor registry software system. The same number is used for all the patient's subsequent tumors. This Patient System ID-Hosp number should not be reused when a patient is deleted. This number is different from Accession Number-Hosp [550]. While Accession Number-Hosp [550] is subject to change, the Patient System ID-Hosp number is created and maintained by the hospital tumor registry’s software system, and requires no key entry. Because the Patient System ID-Hosp number is unchanging, it affords an absolute linkage between a hospital patient record and a central registry’s patient record...digitsRight justified, zero filled.TumorThis provides a stable identifier to link back to all reported tumors for a patient. It also serves as a reliable linking identifier; useful when central registries send follow-up information back to hospitals. Other identifiers such as social security number and medical record number, while useful, are subject to change and are thus less useful for this type of record linkage.A,C,I,MRecord ID.NAACCR112006
30Registry TyperegistryType1A computer-generated code that best describes the type of registry generating the record; used when cases are pooled from multiple registries (a hospital-based registry reporting to a state should have a “3” in this field).1-3..digits.NaaccrDataFacilitates tracking of data sources when data from multiple registries are pooled.A,C,I,MRecord ID.NAACCR
40Registry IDregistryId10A unique code that represents the data transmission source. This item should be used for central registries and non-US health care providers. Refer to Registry ID table in Appendix B. For cases diagnosed on or after 2008, this item may be blank if NPI--Registry ID (item 45) is used to represent the data transmission source. 10-digit number. Reference to EDITS table REGID.DBF in Appendix BR.*Note:* Prior to 2008, this field may contain data from reporting facilities.digitsRight justified, zero filledIn addition to CoC assigned codes or NAACCR assigned codesRNaaccrDataUsed to track data submission flow and to resolve transmission issues.A,C,I,MRecord IDRNAACCR
45NPI--Registry IDnpiRegistryId10The 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.10-digit NPI code (9-digit integer plus 1 check digit), blank..digitsOnly 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>.NaaccrDataThe NPI equivalent of Registry ID [40].A,C,I,MRecord IDR*CMS11.12007
50NAACCR Record VersionnaaccrRecordVersion3This 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.120, 121, 122, 130, 140, 150, 160, 180, 210, 220, 230, 240, 250, 260..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.RevisedRevisedReviseddigitsRNaaccrDataThe 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.A,C,I,MRecord IDRNAACCR
60Tumor Record NumbertumorRecordNumber2A system-generated number that, together with Patient ID Number \[20\], can be used to uniquely identify a tumor over time. Tumor Record Number is assigned to each of a patient’s tumors sequentially in the order in which the tumor record is created by the central registry. A patient’s first tumor record is assigned Tumor Record Number 01. Tumor Record Number is assigned to each of a patient’s tumors sequentially in the order in which the tumor record is created by the central registry and may not match timing based on Diagnosis Date.  For example, the first tumor created in the database is diagnosed 12/2022 and is assigned Tumor Record Number = 01; the registry later learns the patient had a separate tumor diagnosed 5/2020, this is the second tumor created in the database and assigned Tumor Record Number = 02. If a tumor is deleted or replaced, the Tumor Record Number associated with the deleted case is not reused. For example, Patient has three cancers, Tumor Record Numbers = 01, 02 and 03. Upon review, it is determined that the cancer assigned Tumor Record Number 02 is actually a recurrence of 01 and it is deleted. Patient now has two cancers, Tumor Record Numbers = 01 and 03. If a new tumor is created for this patient, 02 will never be reused and Tumor Record Number will be assigned as 04. Unlike Sequence Number, behavior code has no effect on how Tumor Record Number is assigned.01-99R*.digitsRTumorIt is important to be able to track a specific de-identified tumor over time for linkage purposes. Sequence Number—Central \[380\] and Sequence Number—Hospital \[560\] can change as more information becomes available about a case (i.e., diagnosis of a second primary changes sequence number 00 to 01, or discovery of a prior diagnosis may change sequence number 02 to 03). Sequence numbers are also reused if a tumor is deleted. Therefore, sequence number cannot be used to uniquely link a specific tumor. Tumor Record Number, together with Patient ID Number, provide the continuity to uniquely identify a specific tumor over time.A,C,I,MSEER RevisedRevisedRecord IDRNAACCR12.22011
70Addr at DX--CityaddrAtDxCity50Name 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.City name or UNKNOWNCity or Town (pre-96 CoC), City/Town at Diagnosis (CoC)R*RtextMixed case letters, special characters only as allowed by USPS, embedded spaces allowed, left justified, blank filledIn addition to valid CityRTumorA,C,I,MDemographicRCoC
80Addr at DX--StateaddrAtDxState2Identifies the patient’s state or province of residence at the time of diagnosis as identified by the Reporting Source. For consolidated records, the state may be based on reported or corrected residential address information.Refer to EDITS table STATE.DBF in Appendix B; CD, US, XX, YY, ZZState (pre-96 CoC), State at Diagnosis (CoC).RalphaUpper caseIn addition to USPS abbreviationsRTumorThe state of residence is part of the patient's demographic data and has multiple uses. It can be used to evaluate referral patterns, allows for the analysis of cancer cluster concerns, and supports epidemiological studies that use area-based social measures.     **Instructions for Coding** * This field is intended to store residential state for the patient's physical, residential address. The state for PO Box mailing address should not be entered into this data item except in the infrequent case when no other address information is available. * If the patient has multiple tumors, state at diagnosis may be different for each tumor. * Do not update this item if the patient's residential address changes. Store address update information in the affiliated current address data items. Only update based on improved information on the residential address at time of diagnosis. For instance, it is appropriate to correct a state during the geocoding or consolidation process. * Use the U.S. Postal Service abbreviation (for the state, territory, commonwealth, U.S. possession) or Canada Post abbreviation (for the Canadian province/territory) in which the patient resides at the time the reportable tumor is diagnosed. * If the patient is a foreign resident, then code either XX or YY depending on the circumstance.A,C,I,MDemographicRCoC12.22011
81State at DX Geocode 1970/80/90stateAtDxGeocode197080902Code for the state of the patient's residence at the time the tumor was diagnosed is a derived (geocoded) variable based on Census Boundary files from 1970, 1980, or 1990 Decennial Census.01-95, BlankState at DX Geocode1990.._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.text**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 the [**FIPS Codes for Counties and Equivalent Entities Section**](https://apps.naaccr.org/data-dictionary/data-dictionary/version=24/chapter-view/fips-codes-for-counties-and-equivalent-entities/). * It is recommended that geocoding be performed using the NAACCR geocoder. * It is recommended that all cases diagnosed through 1999 should have a State at DX Geocode 70/80/90 \[81\] based on 1990 Census. * At a minimum, all cases diagnosed through 1995-1999 should have a geocoded State at DX Geocode 1990 \[81\]. Some cases, such as those diagnosed in 1999, must have both State at DX Geocode 1990 \[81\] and State at DX Geocode 2000 \[82\] codes for proper assignment of the Census Tr Poverty Indicatr \[145\]. * Do not update this item if the patient's 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. * If the patient has multiple tumors, the county codes may be different for each tumor.RH*TumorPopulating the GeoLocationID 70/80/90 \[351\] correctly requires FIPS code for state and not the USPS abbreviations. Also, on rare occasions, the boundaries of states do change (North Carolina and South Carolina border, for example).A,C,I,MDemographicRNAACCR182018
82State at DX Geocode 2000stateAtDxGeocode20002Code for the state 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.01-95, Blank.._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.text**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 the [FIPS Codes for Counties and Equivalent Entities Section](https://apps.naaccr.org/data-dictionary/data-dictionary/version=24/chapter-view/fips-codes-for-counties-and-equivalent-entities/). * It is recommended that geocoding be performed using the NAACCR geocoder. * It is recommended that all cases diagnosed through 2009 should have a State at DX Geocode 2000 \[82\]. * At a minimum, all cases diagnosed through 1995-2009 should have a State at DX Geocode 2000. Some cases, such as those diagnosed in 2009, must have both State at DX Geocode 2000 \[82\] and State at DX Geocode 2010 \[353\] codes for proper assignment of the Census Tr Poverty Indicatr \[145\]. * Do not update this item if the patient’s 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. * If the patient has multiple tumors, the county codes may be different for each tumor.DTumorPopulating the GeoLocationID - 2000 \[352\] correctly requires FIPS code for state and not the USPS abbreviations. Also, on rare occasions, the boundaries of states do change (North Carolina and South Carolina border, for example).A,C,I,MDemographicDNAACCR182018
83State at DX Geocode 2010stateAtDxGeocode20102Code for the state 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.01-95, Blank..textDTumorPopulating the GeoLocationID 2010 \[353\] correctly requires FIPS code for state and not the USPS abbreviations. Also, on rare occasions, the boundaries of states do change (North Carolina and South Carolina border, for example).     **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 the [**FIPS Codes for Counties and Equivalent Entities Section**](https://apps.naaccr.org/data-dictionary/data-dictionary/version=24/chapter-view/fips-codes-for-counties-and-equivalent-entities/). * It is recommended that geocoding be performed using the NAACCR geocoder. * It is recommended that all cases diagnosed through 2019 should have a State at DX Geocode 2010 \[83\]. * At a minimum, all cases diagnosed through 2005-2019 should have a State at DX Geocode 2010 \[83\]. Some cases, such as those diagnosed 2015-2019, must have both State at DX Geocode 2010 \[83\] and State at DX Geocode 2020 \[354\] codes for proper assignment of the Census Tr Poverty Indicatr \[145\]. * Do not update this item if the patient's 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. * If the patient has multiple tumors, the county codes may be different for each tumor.A,C,I,MDemographicDNAACCR182018
84State at DX Geocode 2020stateAtDxGeocode20202Code for the state 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.01-95, Blank.._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.textDTumorPopulating the GeoLocationID 2020 \[354\] correctly requires FIPS code for state and not the USPS abbreviations. Also, on rare occasions, the boundaries of states do change (North Carolina and South Carolina border, for example).   **Instruction 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 state 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 the **FIPS Codes for Counties and Equivalent Entities Section.** * It is recommended that geocoding be performed using the NAACCR geocoder. * It is recommended that all cases diagnosed through 2029 should have a State at DX Geocode 2020 \[84\]. * At a minimum, all cases diagnosed 2015-2029 should have a State at DX Geocode 2010 \[83\]. Some cases, such as those diagnosed in 2029, must have both State at DX Geocode 2020 \[84\] and State at DX 2030 codes for proper assignment of the Census Tr Poverty Indicatr \[145\]. * Do not update this item if the patient's 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. * If the patient has multiple tumors, the state codes may be different for each tumor.A,C,I,MDemographicDNAACCR182018
86Geocoding Quality CodegeocodingQualityCode1Spatial analysis of cancer data often requires identifying case records that were geocoded. Researchers and registry staff can use this code to select geocoded records and determine which records need to be reviewed and geocoded again.  Historically, Census Tract Certainty \[369\] and NAACCR GIS Coordinate Quality \[366\] codes have been used to determine which geocoded cases require manual review. However, this code represents an improvement over these variables and is based on the geocoded data's precision and accuracy.  Code describing the quality of the geocoding match. The code indicates whether an address run through the NAACCR geocoder matched, failed to match, or needs to be reviewed.  This measure is referred to as Micro Match Status in the NAACCR geocoder documentation and has been in use since July 2017.M,I,R,F..This variable is not coded directly. The code is directly output by the NAACCR/AGGIE Geocoder or MI GeoCorrect Tool.alpha**Application:** * Cases in the “M” or “I” categories are considered high quality matches for state, county, or sub-county (small area) uses.  * Cases in the “R” category require manual review prior to using the data for geospatial analysis below county (small area), but can be used for county-based uses. These “Review” cases should be run through the NAACCR Geocoder as a separate batch run using “Exhaustive Search.” NAACCR has made an interface available, MI GeoCorrect Tool, to assist users in manually selecting among multiple potential addresses (or label as “Fail”).  * Cases in the “F” or “Fail” category geocoding will need to be reviewed, possibly corrected, and geocoded again before use.D*TumorA,C,I,MRevisedDemographicDNAACCR242024
87Geocoding Quality Code DetailgeocodingQualityCodeDetail14This variable is an extension of the **GEOCODING QUALITY CODE \[86\]** and is comprised of details about multiple elements related to the quality of a geocode. Each digit of this code represents an element of the input address along with a hexadecimal score indicating either a full match (M) or a number corresponding to a type of error in the element. There are a total of 14 elements that are given codes to describe a full match (M) or an error in the element. The elements include: Input Type, Street Type, Street, ZIP, City, City Refs, Directionals, Qualifiers, Distance, Outliers, Census Block Groups, Census Tracts, Census Counties, Ref Match Count. This measure is currently referred to as Penalty Code in the NAACCR geocoder documentation and has been in use since November 2017.A-G, 1-9..**Application:** These codes provide researchers and registry staff a detailed assessment of the address components geocoded and the quality of the geocode. The codes provide a way to assess input reference data agreement, geographic accuracy, and micro-scale fitness for use at the sub-county level. This code is intended to be used by researchers or registry staff when manually reviewing geocoded cases in MI GeoCorrect Tool (for cases with an R or F code in the Geocoding Quality Measure). This variable is not coded directly. The code is directly output by the NAACCR/AGGIE Geocoder or MI GeoCorrect Tool.  <table style="border-color:hsl(0, 0%, 0%);border-style:solid;"><tbody><tr><td style="border:1.0pt solid windowtext;padding:0in 5.4pt;vertical-align:top;width:40.25pt;">XXXXXXXXXXXXXX</td><td style="border-bottom-style:solid;border-color:windowtext;border-left-style:none;border-right-style:solid;border-top-style:solid;border-width:1.0pt;padding:0in 5.4pt;vertical-align:top;width:355.25pt;"><strong>Interactive MMMMMMMMMMMMMM.&nbsp;</strong>Geocoding was completed and the address matched after manual review in MI GeoCorrect Tool.</td></tr><tr><td style="border-bottom-style:solid;border-color:windowtext;border-left-style:solid;border-right-style:solid;border-top-style:none;border-width:1.0pt;padding:0in 5.4pt;vertical-align:top;width:40.25pt;">14 digit Combination of M and/or F</td><td style="border-bottom:1.0pt solid windowtext;border-left-style:none;border-right:1.0pt solid windowtext;border-top-style:none;padding:0in 5.4pt;vertical-align:top;width:355.25pt;">Each of the 14 positions has ‘M’ when the match for that element is good. Other alphanumeric codes describe any issues with the match. Codes meanings are specific to each of the 14 geocoding elements. For instance, ‘1’ for Input Type is ‘street only’ match but ‘1’ for Street Type is “PO Box”. See website for full details:&nbsp;<a href="https://geo.naaccr.org/Services/Geocode/About/TechnicalDetails.aspx">https://geo.naaccr.org/Services/Geocode/About/TechnicalDetails.aspx</a>&nbsp;</td></tr></tbody></table>mixed14 character combination of A-G,1-9D*TumorA,C,I,MRevisedDemographicDNAACCR242024
89County at DX AnalysiscountyAtDxAnalysis3County at Diagnosis Analysis Code for the county of the patient's residence at the time the tumor was diagnosed is a derived variable to be used for county and county-based (such as PRCDA, or historically CHSDA) rates and analysis for all cases regardless of year of diagnosis.001-997, 998, 999.._Note_: For U.S. residents, historically, standard codes are those of the FIPS publication _Counties and Equivalent Entities of the United States, Its Possessions, and Associated Areas._ These FIPS codes (FIPS 6-4) have been replaced by INCITS standard codes; however, there is no impact on this variable as the codes align with the system the Census used for each decennial census and changes will automatically be accounted for during geocoding. County codes issued by the Federal Information Processing Standards (FIPS) publication, _Counties and Equivalent Entities of the United States, Its Possessions, and Associated Areas_ is available in the [**FIPS Codes for Counties and Equivalent Entities Section**](https://apps.naaccr.org/data-dictionary/data-dictionary/version=24/chapter-view/fips-codes-for-counties-and-equivalent-entities/).digitsDTumorHistorically, we had a single County at DX \[90\]. However, counties change over time (which impacts our derived variables such as poverty code indicator which don’t directly align with year of diagnosis), and the county reported by the facility does not always match the geocoded county. In the vast majority of cases where geocoded county and reported county differ, the geocoded county is correct. Including additional geocoded county codes for each census year addresses the accuracy of geocoded fields, however, it is cumbersome to pull data from different variables in order to generate county-level rates. Use of this variable ensures the most accurate and appropriate county data is used for calculating county-level rates. **Instructions for Coding** * This variable can be generated using a standard, NAACCR supplied SAS code (or the logic below). At a minimum, this field should be derived prior to release of data for county-level analysis or rates. Ideally, the variable should be updated whenever there is a change to any county field. * If the County At DX Reported \[90\] AND the County At DX Geocoded associated with the year of diagnosis are the same, the County At DX Analysis county can be pulled from either field. * If the County At DX Reported \[90\] is "999" or NULL AND County At DX Geocoded associated with the year of diagnosis is geocoded (Census Tr Cert \[364\] for cases diagnosed through 1999, \[365\] for cases diagnosed 2000-2009, or \[367\] for cases diagnosed 2010-2019\] = is not null and less than 9), pull the County At DX Geocode associated with the year of diagnosis. Cases diagnosed 1990-1999, pull from County At DX Geocode 1990. Cases diagnosed 2000-2009, pull from County At DX Geocode 2000. Cases diagnosed 2010-2019, pull from County At DX Geocode 2010. Cases diagnosed 2020-2029, pull from County At DX Geocode 2020. * If the County At DX Geocoded associated with the year of diagnosis does not equal County At DX Reported \[90\] AND is a high quality geocode (Census Tr Cert \[364 \]for cases diagnosed through 1999, \[365\] for cases diagnosed 2000-2009, or \[367\] for cases diagnosed 2010-2019\] = 1), pull the County At DX Geocode associated with the year of diagnosis. Cases diagnosed 1990-1999, pull from County At DX Geocode 1990. Cases diagnosed 2000-2009, pull from County At DX Geocode 2000. Cases diagnosed 2010-2019, pull from County At DX Geocode 2010. Cases diagnosed 2020-2029, pull from County At DX Geocode 2020. * If the County At DX Geocoded associated with the year of diagnosis does not equal County At DX Reported \[90\] AND is based on a PO Box address (Census Tr Cert \[364 \]for cases diagnosed through 1999, \[365\] for cases diagnosed 2000-2009, or \[367\] for cases diagnosed 2010-2019\] = 5), the derived county equals the County At DX Reported \[90\]. * If the County At DX Geocoded associated with the year of diagnosis is ungeocoded (Census Tr Cert \[364\] for cases diagnosed through 1999, #365 for cases diagnosed 2000-2009, or \[367\] for cases diagnosed 2010-2019\] = blank or 9), the derived county equals the County At DX Reported \[90\]. * If the County At DX Geocoded associated with the year of diagnosis does not match County At DX Reported \[90\] AND a geocode is based on residential addresses but geocoded to the centroid of a zip code (Census Tr Cert \[364\] for cases diagnosed through 1999, \[365\] for cases diagnosed 2000-2009, or \[367\] for cases diagnosed 2010-2019\] = 2-4), manual review is required to resolve the discrepancy. Until manual review can be done, use the County At DX Reported \[90\]. * If the patient has multiple tumors, the county codes may be different for each tumor. * Detailed standards have not been set for Canadian provinces/territories. Use code 998 for Canadian residents.A,C,I,MDemographicDNAACCR182018
90County at DX ReportedcountyAtDx3Code for the county of the patients residence at the time of diagnosis as identified by the Reporting Source. For U.S. residents, standard codes are those of the FIPS publication _Counties and Equivalent Entities of the United States, Its Possessions, and Associated Areas_ or their equivalent INCITS codes. Calculating county and county-based variable rates using this item is **not** recommended. The more specific, geocoded county items should be used when available.001-999County (pre-96 SEER/CoC), County at DX, County at Diagnosis (CoC).R_Note_: For U.S. residents, historically, standard codes are those of the FIPS publication _Counties and Equivalent Entities of the United States, Its Possessions, and Associated Areas_. These FIPS codes (FIPS 6-4) have been replaced by INCITS standard codes; however, there is no impact on this variable as the codes align with the system the Census used for each decennial census and changes will automatically be accounted for during geocoding. County codes issued by the Federal Information Processing Standards (FIPS) publication _Counties and Equivalent Entities of the United States, Its Possessions, and Associated Areas_ is available in the **FIPS Codes for Counties and Equivalent Entities Section**.digitsRight justified, zero filled_Note:_ See the [**FIPS Codes for Counties and Equivalent Entities Section**](https://apps.naaccr.org/data-dictionary/data-dictionary/version=24/chapter-view/fips-codes-for-counties-and-equivalent-entities/) 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.In addition to FIPS and GeocodesRTumorThis data item may be used for epidemiological purposes. For example, to measure cancer incidence in a particular geographic area. **Instructions for Coding** * This field is intended to store address information for the patient's physical, residential address. All efforts should be made to find the patient's true street address and postal code, including reviewing relevant sources outside the medical record if available. The county for a PO Box mailing address should only be recorded when no other address information is available in the medical record and no other information sources are available. * If the patient has multiple tumors, county at diagnosis may be different for each tumor. * Do not update this item if the patient's county of residence changes. Store updated address information in the affiliated current address data items. Only update based on improved information on the residential address at time of diagnosis. For instance, it is appropriate to correct county during a consolidation process. * This variable is coded at time of abstracting and is considered less accurate than the derived, geocoded county at diagnosis variables: County at Diagnosis 1990, 2000, 2010, & 2020. * Detailed standards have not been set for Canadian provinces/territories. Use code 998 for Canadian residents.A,C,I,MDemographicRFIPS/SEER
94County at DX Geocode 1970/80/90countyAtDxGeocode19903County at Diagnosis 1990 Code for the county of the patient’s residence at the time the tumor was diagnosed is a derived (geocoded) variable based on Census Boundary files from 1990 Decennial Census. This code should be used for county and county-based (such as PRCDA, or historically CHSDA) rates and analysis for all cases diagnosed prior to 2000.000-999County at DX Geocode1990.._Note_: For U.S. residents, historically, standard codes are those of the FIPS publication "Counties and Equivalent Entities of the United States, Its Possessions, and Associated Areas." These FIPS codes (FIPS 6-4) have been replaced by INCITS standard codes; however, there is no impact on this variable as the codes align with the system the Census used for each decennial census and changes will automatically be accounted for during geocoding. County codes issued by the Federal Information Processing Standards (FIPS) publication _Counties and Equivalent Entities of the United States, Its Possessions, and Associated Areas_ is available in the [**FIPS Codes for Counties and Equivalents Section**](https://apps.naaccr.org/data-dictionary/data-dictionary/version=24/chapter-view/fips-codes-for-counties-and-equivalent-entities/).digitsRH*TumorCensus tracts are areas geographically nested within counties and designated with a 6-digit number code. This 6-digit code is commonly repeated within a state in different counties. Census tract numbers are only unique when paired with the state and the county. Therefore, a tract cannot be accurately identified without knowing the county. Example from Massachusetts: Rural Franklin County contains a tract 040600 with 2010 population 4,612 people. Urban Suffolk County contains a tract 040600 with 2,444 people. The county must be known in order to distinguish between the two tract codes. Because we historically used a single variable for county at diagnosis \[90\] correct tract codes were frequently paired with the wrong county due to incorrect county assignment during abstracting or a change of county over time. Also, some variables, such as the Census Tr Poverty Indicatr \[145\] require the use of the decennial Census County codes closest to year of diagnosis and not the decade of year of diagnosis. Using a single county at diagnosis, and using the reported versus geocoded data, may result in erroneous assignment of geographic location as well as invalid links with census data (i.e., population, poverty category, urban/rural designation). **Instructions for Coding** * This variable is generated through the process of geocoding either during abstracting or at the central registry level. * At a minimum, all cases diagnosed through diagnosis year 1999 should have a geocoded County at Diagnosis 1990. Cases diagnosed 1996-1999 must have both County at Diagnosis 1990 and County at Diagnosis 2000 codes for proper assignment of the Census Tract Poverty Indicator \[145\]. * If the patient has multiple tumors, geocoded county may be different for each tumor. * Do not update this item if the patient's residential county changes. Store updated address information in the affiliated current address data items. Only update based on improved information on the residential address at time of diagnosis. For instance, it is appropriate to correct a county during manual geocoding or a consolidation process. * Refer to _STORE_ for residency rules. * PO Box address information should not be used to geocode this data item except in the infrequent case when no other address information is available. * Detailed standards have not been set for Canadian provinces/territories. Use code 998 for Canadian residents. * Blank "Not geocoded" is allowable for cases diagnosed after 1999. However, it is recommended to have all cases geocoded to a 1990 Census County to allow for both retrospective and cross-sectional analyses.A,C,I,MDemographicDNAACCR162016
95County at DX Geocode2000countyAtDxGeocode20003Code for the county of the patient's residence at the time the tumor was diagnosed is a derived (geocoded) variable based on Census Boundary files from 2000 Decennial Census. **This code should be used for county and county-based (such as PRCDA, or historically CHSDA) rates and analysis for all cases diagnosed in 2000-2009.**001-999.._Note_: For U.S. residents, historically, standard codes are those of the FIPS publication "Counties and Equivalent Entities of the United States, Its Possessions, and Associated Areas." These FIPS codes (FIPS 6-4) have been replaced by INCITS standard codes; however, there is no impact on this variable as the codes align with the system the Census used for each decennial census and changes will automatically be accounted for during geocoding. County codes issued by the Federal Information Processing Standards (FIPS) publication _Counties and Equivalent Entities of the United States, Its Possessions, and Associated Areas_ is available in the [**FIPS Codes for Counties and Equivalents Section**](https://apps.naaccr.org/data-dictionary/data-dictionary/version=24/chapter-view/fips-codes-for-counties-and-equivalent-entities/).digitsDTumorCensus tracts are areas geographically nested within counties and designated with a 6-digit number code. This 6-digit code is commonly repeated within a state in different counties. Census tract numbers are only unique when paired with the state and the county. Therefore, a tract cannot be accurately identified without knowing the county. Example from Massachusetts: Rural Franklin County contains a tract 040600 with 2010 population 4,612 people. Urban Suffolk County contains a tract 040600 with 2,444 people. The county must be known in order to distinguish between the two tract codes. Because we historically used a single variable for county at diagnosis \[90\], correct tract codes were frequently paired with the wrong county due to incorrect county assignment during abstracting or a change of county over time. Also, some variables, such as the Census Tr Poverty Indicatr \[145\] require the use of the decennial Census County codes closest to year of diagnosis and not the decade of year of diagnosis. Using a single county at diagnosis, and using the reported versus geocoded data, may result in erroneous assignment of geographic location as well as invalid links with census data (i.e., population, poverty category, urban/rural designation). **Instructions for Coding** * This variable is generated through the process of geocoding either during abstracting or at the central registry level. * It is recommended that all cases diagnosed through 2009 have a geocoded County at Diagnosis 2000. * At a minimum, all cases diagnosed through 1996-2009 should have a geocoded County at Diagnosis 2000. Cases diagnosed 1996-1999 must have both County at Diagnosis 1990 and County at Diagnosis 2000 codes for proper assignment of the Census Tract Poverty Indicator \[145\]. Cases diagnosed 2006-2009 must have both County at Diagnosis 2000 and County at Diagnosis 2010 codes for proper assignment of the Census Tract Poverty Indicator \[145\]. * If the patient has multiple tumors, geocoded county may be different for each tumor. * Do not update this item if the patient’s county of residence changes. Store updated address information in the affiliated current address data items. Only update based on improved information on the residential address at time of diagnosis. For instance, it is appropriate to correct a county during manual geocoding or a consolidation process. * PO Box address information should not be used to geocode this data item except in the infrequent case when no other address information is available. * Detailed standards have not been set for Canadian provinces/territories. Use code 998 for Canadian residents. * Blank "Not geocoded" is allowable for cases diagnosed before 1995 and after 2009. However, it is recommended to have all cases geocoded to a 2000 Census County to allow for both retrospective and cross-sectional analyses.A,C,I,MDemographicDNAACCR162016
96County at DX Geocode2010countyAtDxGeocode20103County at Diagnosis 2010 Code for the county of the patient's residence at the time the tumor was diagnosed is a derived (geocoded) variable based on Census Boundary files from 2010 Decennial Census. This code should be used for county and county-based (such as PRCDA, or historically CHSDA) rates and analysis for all cases diagnosed in 2010-2019.000-999.._Note_: For U.S. residents, historically, standard codes are those of the FIPS publication “Counties and Equivalent Entities of the United States, Its Possessions, and Associated Areas.” These FIPS codes (FIPS 6-4) have been replaced by INCITS standard codes; however, there is no impact on this variable as the codes align with the system the Census used for each decennial census and changes will automatically be accounted for during geocoding. County codes issued by the Federal Information Processing Standards (FIPS) publication _Counties and Equivalent Entities of the United States, Its Possessions, and Associated Areas_ is available in the [**FIPS Codes for Counties and Equivalents Section**](https://apps.naaccr.org/data-dictionary/data-dictionary/version=24/chapter-view/fips-codes-for-counties-and-equivalent-entities/).digitsDTumorCensus tracts are areas geographically nested within counties and designated with a 6-digit number code. This 6-digit code is commonly repeated within a state in different counties. Census tract numbers are only unique when paired with the state and the county. Therefore, a tract cannot be accurately identified without knowing the county. Example from Massachusetts: Rural Franklin County contains a tract 040600 with 2010 population 4,612 people. Urban Suffolk County contains a tract 040600 with 2,444 people. The county must be known in order to distinguish between the two tract codes. Because we historically used a single variable for county at diagnosis \[90\], correct tract codes were frequently paired with the wrong county due to incorrect county assignment during abstracting or a change of county over time. Also, some variables, such as the Census Tr Poverty Indicatr \[145\] require the use of the decennial Census County codes closest to year of diagnosis and not the decade of year of diagnosis. Using a single county at diagnosis, and using the reported versus geocoded data, may result in erroneous assignment of geographic location as well as invalid links with census data (i.e., population, poverty category, urban/rural designation). **Instructions for Coding** * This variable is generated through the process of geocoding either during abstracting or at the central registry level. * It is recommended that all cases diagnosed through 2019 should have a geocoded County at Diagnosis 2010. * At a minimum, all cases diagnosed through 2006-2019 should have a geocoded County at Diagnosis 2010. Cases diagnosed 2006-2009 must have both County at Diagnosis 2000 and County at Diagnosis 2010 codes for proper assignment of the Census Tract Poverty Indicator \[145\]. Cases diagnosed 2016-2019 must have both County at Diagnosis 2010 and County at Diagnosis 2020 codes for proper assignment of the Census Tract Poverty Indicator \[145\]. * If the patient has multiple tumors, geocoded county may be different for each tumor. * Do not update this item if the patient's county of residence changes. Store updated address information in the affiliated current address data items. Only update based on improved information on the residential address at time of diagnosis. For instance, it is appropriate to correct a county during manual geocoding or a consolidation process. * PO Box address information should not be used to geocode this data item except in the infrequent case when no other address information is available. * Detailed standards have not been set for Canadian provinces/territories. Use code 998 for Canadian residents. * Blank "Not geocoded" is allowable for cases diagnosed before 2005 and after 2019. However, it is preferred to have all cases geocoded to a 2010 Census County to allow for both retrospective and cross-sectional analyses.A,C,I,MDemographicDNAACCR162016
97County at DX Geocode2020countyAtDxGeocode20203Code for the county of the patient's residence at the time the tumor was diagnosed is a derived (geocoded) variable based on Census Boundary files from 2020 Decennial Census. **This code should be used for county and county-based (such as PRCDA, or historically CHSDA) rates and analysis for all cases diagnosed in 2020-2029.**001-999.._Note_: For U.S. residents, historically, standard codes are those of the FIPS publication "Counties and Equivalent Entities of the United States, Its Possessions, and Associated Areas." These FIPS codes (FIPS 6-4) have been replaced by INCITS standard codes; however, there is no impact on this variable as the codes align with the system the Census used for each decennial census and changes will automatically be accounted for during geocoding. County codes issued by the Federal Information Processing Standards (FIPS) publication _Counties and Equivalent Entities of the United States, Its Possessions, and Associated Areas_ is available in the [**FIPS Codes for Counties and Equivalents Section**](https://apps.naaccr.org/data-dictionary/data-dictionary/version=24/chapter-view/fips-codes-for-counties-and-equivalent-entities/).digitsDTumorCensus tracts are areas geographically nested within counties and designated with a 6-digit number code. This 6-digit code is commonly repeated within a state in different counties. Census tract numbers are only unique when paired with the state and the county. Therefore, a tract cannot be accurately identified without knowing the county. Example from Massachusetts: Rural Franklin County contains a tract 040600 with 2010 population 4,612 people. Urban Suffolk County contains a tract 040600 with 2,444 people. The county must be known in order to distinguish between the two tract codes. Because we historically used a single variable for County at DX \[90\], correct tract codes were frequently paired with the wrong county due to incorrect county assignment during abstracting or a change of county over time. Also, some variables, such as the Census Tr Poverty Indicatr \[145\] require the use of the decennial Census County codes closest to year of diagnosis and not the decade of year of diagnosis. Using a single county at diagnosis, and using the reported versus geocoded data, may result in erroneous assignment of geographic location as well as invalid links with census data (i.e., population, poverty category, urban/rural designation). **Instructions for Coding** * This variable is generated through the process of geocoding either during abstracting or at the central registry level. * It is recommended that all cases diagnosed through 2029 should have a geocoded County at Diagnosis 2020. * At a minimum, all cases diagnosed through 2016-2029 should have a geocoded County at Diagnosis 2020. Cases diagnosed in 2016-2019, must have both County at Diagnosis 2010 and County at Diagnosis 2020 codes for proper assignment of the Census Tr Poverty Indicatr \[145\]. * If the patient has multiple tumors, geocoded county may be different for each tumor. * Do not update this item if the patient's county of residence changes. Store updated address information in the affiliated current address data items. Only update based on improved information on the residential address at time of diagnosis. For instance, it is appropriate to correct a county during manual geocoding or a consolidation process. * PO Box address information should not be used to geocode this data item except in the infrequent case when no other address information is available. * If the patient has multiple tumors, the county codes may be different for each tumor. * Detailed standards have not been set for Canadian provinces/territories. Use code 998 for Canadian residents. * Blank "Not geocoded" is allowable for cases diagnosed before 2015 and after 2029. However, it is preferred to have all cases geocoded to a 2020 Census County to allow for both retrospective and cross-sectional analyses.A,C,I,MDemographicDNAACCR162016
100Addr at DX--Postal CodeaddrAtDxPostalCode9Identifies the postal code of the patient’s address at diagnosis. For consolidated records, postal code may be based on reported or corrected residential address information.5-digit or 9-digit U.S. ZIP codes; 6-character Canadian postal codes; valid postal codes from other countries, 888888888, 999999999, 88888+4 blanks (U.S.), 99999+4 blanks (U.S.), 999999+3 blanks (Canada)Postal Code (CCCR), Postal Code at Diagnosis (CoC), Zip Code (pre-CoC)R*RtextNumbers or upper case letters. No special characters or embedded spaces allowed. Left justified, blank filledIn addition to known US and Canadian or other postal codesRTumorThe postal code is part of the patient’s demographic data and has multiple uses. It can be used to evaluate referral patterns, allows for the analysis of cancer cluster concerns, and supports epidemiological studies that use area-based social measures. **Instructions for Coding** * This field is intended to store ZIP Code or other postal code for the patient's physical, residential address. The postal code for PO Box mailing address should not be entered into this data item except in the infrequent case when no other address information is available. * If the patient has multiple tumors, the postal code at diagnosis may be different for each tumor. * Do not update this item if the patient's residential address changes. Store address update information in the affiliated current address data items. Only update based on improved information on the residential address at time of diagnosis. For instance, it is appropriate to correct a ZIP Code during the geocoding or consolidation process. * For U.S. residents, use either the 5-digit or the extended 9-digit ZIP code. Blanks follow the 5-digit code if the 4-digit extension is not collected. * For Canadian residents, use the 6-character alphanumeric postal code. * When available, enter the postal code for other countries for out-of-country addresses.A,C,I,MDemographicRCoC
102Addr at DX--CountryaddrAtDxCountry3Country 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].International Standards Organization (ISO) 3166-1 Country Three Character Codes and custom codes: ZZN, ZZC, ZZS, ZZP, ZZE, ZZF, ZZA, ZZX, ZZU, XNI, XCB, XEN, XSC, XGR, XSL, CSK, YUG, XUM, XNF, XSD, XWF, XSF, XEF, XIF, XET, XAP, XIS, XCR, XOR, XSE, XMS, XCH, XML, XMC, XPL.RalphaUpper caseUse 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.TumorCountry 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.A,C,I,MDemographicRNAACCR132013
110Census Tract 1970/80/90censusTract197080906Identifies the patient's census tract of residence at the time the tumor was diagnosed. Census Tract 70/80/90 is a derived (geocoded) variables based on the Census Boundary files from 1970, 1980, 1990 Decennial Census. See Census Tract 2000 \[130\]; Census Tract 2010 \[135\]; Census Tract 2020 \[125\]. Codes are those used by the U.S. Census Bureau for the Year 1970, 1980 or 1990 Census. Refer to Census Cod Sys 1970/80/90 \[120\] to ascertain the decade of reference. For consolidated records, the geocoded state should be based on the best address at diagnosis information identified.Valid FIPS Codes: 000100-999998, 000000, 999999, BlankCensus Tract, Census Tract/Block Numbering Area (BNA) (SEER).._Note:_ For U.S. residents, historically, standard codes are those of the FIPS publication "Counties and Equivalent Entities of the United States, Its Possessions, and Associated Areas." These FIPS codes (FIPS 6-4) have been replaced by INCITS standard codes; however, there is no impact on this variable as the codes align with the system the Census used for each decennial census and changes will automatically be accounted for during geocoding. County codes issued by the Federal Information Processing Standards (FIPS) publication _Counties and Equivalent Entities of the United States, Its Possessions, and Associated Areas_ is available in the [**FIPS Codes for Counties and Equivalents Section**](https://apps.naaccr.org/data-dictionary/data-dictionary/version=24/chapter-view/fips-codes-for-counties-and-equivalent-entities/).digitsRight justified, zero filledRH*TumorCensus tract codes allow central registries to calculate incidence rates for geographical areas having population estimates. This field allows a central registry to add Year 2020 Census tracts to tumors diagnosed in previous years, without losing the codes in data items Census Tract 2000 \[130\]; Census Tract 2010 \[135\]; Census Tract 2020 \[125\]. The Census Bureau provides population and other demographic data for census tracts. This allows for small area analysis for general surveillance or special geographical and socioeconomic analysis. **Instructions for Coding** * This variable is generated through the process of geocoding either during abstracting or at the central registry level. * Census tract codes have a 4-digit basic number and also may have a 2-digit suffix. Census tract numbers range from 0001.00 to 9999.98, but the decimal should not be retained in the NAACCR layout. * At a minimum, all cases diagnosed through diagnosis year 1999 should have a Census Tract 1970/80/90. Cases diagnosed 1996-1999 must have both State at DX Geocode 1970/80/90 \[81\] and State at DX Geocode 2000 \[82\] codes for proper assignment of the Census Tr Poverty Indicatr \[145\]. * If the patient has multiple tumors, geocoded state at diagnosis may be different for each tumor. * Do not update this item if the patient's tract of residence changes. Store updated address information in the affiliated current address data items. Only update based on improved information on the residential address at time of diagnosis. For instance, it is appropriate to correct a tract during manual geocoding or a consolidation process. * PO Box address information should not be used to geocode this data item except in the infrequent case when no other address information is available. * Blank "Not geocoded" is allowable for cases diagnosed after 1999. However, it is recommended to have all cases geocoded to a Census Tract 1970/80/90 to allow for both retrospective and cross-sectional analyses.A,C,I,MDemographicRHSEER
120Census Cod Sys 1970/80/90censusCodSys197080901Identified 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.0-3, blankCensus Coding System (CoC), Coding System for Census Tract (pre-96 SEER/CoC).. | | | | --- | --- | | **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.digitsRH*TumorAllows 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.A,C,I,MDemographicRHSEER
125Census Tract 2020censusTract20206Identifies the patient's census tract of residence at the time the tumor was diagnosed. Census Tract 2020 is a derived (geocoded) variables based on the Census Boundary files from 2020 See Census Tract 1970/80/90 \[110\]; Census Tract 2000 \[130\]; Census Tract 2010 \[135\]. Codes are those used by the U.S. Census Bureau for the Year 2020 Census. Census tract codes have a 4-digit basic number and also may have a 2-digit suffix. Census tract numbers range from 0001.00 to 9999.98, but the decimal should not be retained in the NAACCR layout.Census Tract Codes 000100-999998, 000000, 999999, Blank..Note: For U.S. residents, historically, standard codes are those of the FIPS publication "Counties and Equivalent Entities of the United States, Its Possessions, and Associated Areas." These FIPS codes (FIPS 6-4) have been replaced by INCITS standard codes; however, there is no impact on this variable as the codes align with the system the Census used for each decennial census and changes will automatically be accounted for during geocoding. County codes issued by the Federal Information Processing Standards (FIPS) publication _Counties and Equivalent Entities of the United States, Its Possessions, and Associated Areas_ is available in the [**FIPS Codes for Counties and Equivalents Section**](https://apps.naaccr.org/data-dictionary/data-dictionary/version=24/chapter-view/fips-codes-for-counties-and-equivalent-entities/).digitsRight justified, zero filledDTumorCensus tract codes allow central registries to calculate incidence rates for geographical areas having population estimates. This field allows a central registry to add Year 2020 Census tracts to tumors diagnosed in previous years, without losing the codes in data items \[110\], \[130\] and \[135\]. The Census Bureau provides population and other demographic data for census tracts. This allows for small area analysis for general surveillance or special geographical and socioeconomic analysis. **Instructions for Coding** * This variable is generated through the process of geocoding either during abstracting or at the central registry level. * Census tract codes have a 4-digit basic number and also may have a 2-digit suffix. Census tract numbers range from 0001.00 to 9999.98, but the decimal should not be retained in the NAACCR layout. * It is recommended that all cases diagnosed through 2029 should have a geocoded Census Tract 2020. * At a minimum, all cases diagnosed through 2016-2029 should have a geocoded Census Tract 2020. Cases diagnosed 2016-2019 must have both Geocoded State at DX 2010 and Geocoded State at DX 2020 codes for proper assignment of the Census Tr Poverty Indicatr \[145\]. * If the patient has multiple tumors, geocoded state at diagnosis may be different for each tumor. * Do not update this item if the patient's tract of residence changes. Store updated address information in the affiliated current address data items. Only update based on improved information on the residential address at time of diagnosis. For instance, it is appropriate to correct a tract during manual geocoding or a consolidation process. * PO Box address information should not be used to geocode this data item except in the infrequent case when no other address information is available. * Blank "Not geocoded" is allowable for cases diagnosed before 2015 and after 2029. However, it is preferred to have all cases geocoded to a 2020 Census Tract to allow for both retrospective and cross-sectional analyses.A,C,I,MDemographicDNAACCR182018
130Census Tract 2000censusTract20006Identifies the patient's census tract of residence at the time the tumor was diagnosed. Census Tract 2000 is a derived (geocoded) variables based on the Census Boundary files from 2000. See Census Tract 70/80/90 \[110\]; Census Tract 2010 \[135\]; Census Tract 2020 \[125\]. Codes are those used by the U.S. Census Bureau for the Year 2000 Census. For consolidated records, the geocoded state should be based on the best address at diagnosis information identified.Valid FIPS Codes: 000100-999998, 000000, 999999, blankCensus Tract--Alternate (pre-2003).._Note_: For U.S. residents, historically, standard codes are those of the FIPS publication "Counties and Equivalent Entities of the United States, Its Possessions, and Associated Areas." These FIPS codes (FIPS 6-4) have been replaced by INCITS standard codes; however, there is no impact on this variable as the codes align with the system the Census used for each decennial census and changes will automatically be accounted for during geocoding. County codes issued by the Federal Information Processing Standards (FIPS) publication Counties and Equivalent Entities of the United States, Its Possessions, and Associated Areas is available in the [**FIPS Codes for Counties and Equivalents Section**](https://apps.naaccr.org/data-dictionary/data-dictionary/version=24/chapter-view/fips-codes-for-counties-and-equivalent-entities/).digitsRight justified, zero filledRHTumorCensus tract codes allow central registries to calculate incidence rates for geographical areas having population estimates. This field allows a central registry to add Year 2020 Census tracts to tumors diagnosed in previous years, without losing the codes in data items \[110\], \[130\] and \[135\]. The Census Bureau provides population and other demographic data for census tracts. This allows for small area analysis for general surveillance or special geographical and socioeconomic analysis. **Instructions for Coding** * This variable is generated through the process of geocoding either during abstracting or at the central registry level. * Census tract codes have a 4-digit basic number and also may have a 2-digit suffix. Census tract numbers range from 0001.00 to 9999.98, but the decimal should not be retained in the NAACCR layout. * It is recommended that all cases diagnosed through 2009 should have a geocoded Census Tract 2000. * At a minimum, all cases diagnosed through 1996-2009 should have a geocoded Census Tract 2000. Cases diagnosed 1996-1999 must have both State at DX Geocode 70/80/90 \[82\] and State at DX 2000 Geocode \[83\] codes for proper assignment of the Census Tr Poverty Indicatr \[145\]. Cases diagnosed 2006-2009 must have both State at DX 2000 Geocode \[83\] and State at DX Geocode 2010 \[84\] codes for proper assignment of the Census Tr Poverty Indicatr \[145\]. * If the patient has multiple tumors, geocoded state at diagnosis may be different for each tumor. * Do not update this item if the patient's tract of residence changes. Store updated address information in the affiliated current address data items. Only update based on improved information on the residential address at time of diagnosis. For instance, it is appropriate to correct a tract during manual geocoding or a consolidation process. * PO Box address information should not be used to geocode this data item except in the infrequent case when no other address information is available. * Blank "Not geocoded" is allowable for cases diagnosed before 1995 and after 2009. However, it is recommended to have all cases geocoded to a 2000 Census Tract to allow for both retrospective and cross-sectional analyses.A,C,I,MDemographicRHNAACCR
135Census Tract 2010censusTract20106Identifies the patient's census tract of residence at the time the tumor was diagnosed. Census Tract 2010 is a derived (geocoded) variables based on the Census Boundary files from 2010. See Census Tract 1970/80/90 \[110\]; Census Tract 2000 \[130\]; Census Tract 2020 \[125\]. Codes are those used by the U.S. Census Bureau for the Year 2010 Census. For consolidated records, the geocoded state should be based on the best address at diagnosis information identified.Census Tract Codes 000100-999998, 000000, 999999, blank.._Note_: For U.S. residents, historically, standard codes are those of the FIPS publication "Counties and Equivalent Entities of the United States, Its Possessions, and Associated Areas." These FIPS codes (FIPS 6-4) have been replaced by INCITS standard codes; however, there is no impact on this variable as the codes align with the system the Census used for each decennial census and changes will automatically be accounted for during geocoding. County codes issued by the Federal Information Processing Standards (FIPS) publication Counties and Equivalent Entities of the United States, Its Possessions, and Associated Areas is available in the [**FIPS Codes for Counties and Equivalents Section**](https://apps.naaccr.org/data-dictionary/data-dictionary/version=24/chapter-view/fips-codes-for-counties-and-equivalent-entities/).digitsRight justified, zero filledRTumorCensus tract codes allow central registries to calculate incidence rates for geographical areas having population estimates. This field allows a central registry to add Year 2020 Census tracts to tumors diagnosed in previous years, without losing the codes in data items \[110\], \[130\] and \[135\]. The Census Bureau provides population and other demographic data for census tracts. This allows for small area analysis for general surveillance or special geographical and socioeconomic analysis. **Instructions for Coding** * This variable is generated through the process of geocoding either during abstracting or at the central registry level. * Census tract codes have a 4-digit basic number and also may have a 2-digit suffix. Census tract numbers range from 0001.00 to 9999.98, but the decimal should not be retained in the NAACCR layout. * It is recommended that all cases diagnosed through 2019 should have a geocoded Census Tract 2010. * At a minimum, all cases diagnosed through 2006-2019 should have a geocoded Census Tract 2010. Cases diagnosed 2006-2009 must have both State at DX Geocode 2000 \[82\] and State at DX Geocode 2010 \[83\] codes for proper assignment of the Census Tr Poverty Indicatr \[145\]. Cases diagnosed 2016-2019 must have both State at DX Geocode 2010 \[83\] and State at DX Geocode 2020 \[84\] codes for proper assignment of the Census Tr Poverty Indicatr \[145\]. * If the patient has multiple tumors, geocoded state at diagnosis may be different for each tumor. * Do not update this item if the patient's tract of residence changes. Store updated address information in the affiliated current address data items. Only update based on improved information on the residential address at time of diagnosis. For instance, it is appropriate to correct a tract during manual geocoding or a consolidation process. * PO Box address information should not be used to geocode this data item except in the infrequent case when no other address information is available. * Blank “Not geocoded” is allowable for cases diagnosed before 2005 and after 2019. However, it is preferred to have all cases geocoded to a 2010 Census Tract to allow for both retrospective and cross-sectional analyses.A,C,I,MDemographicRNAACCR12.12011
145Census Tr Poverty IndictrcensusTrPovertyIndictr1Assigns 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.1-4, 9..digitsDTumorMany 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.A,C,I,MDemographicDNAACCR132013
150Marital Status at DXmaritalStatusAtDx1Code 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.1-6, 9Marital Status at Diagnosis (SEER/CoC), Marital Status at Initial Diagnosis (pre-96 CoC)..digits.TumorIncidence and survival with certain cancers vary by marital status. The item also helps in patient identification.A,C,I,MDemographicRSEER
160Race 1race12Code the patient’s race. Race is coded separately from Spanish/Hispanic Origin [190]. All tumors for the same patient should have the same race codes. If the patient is multiracial, code all races using RACE 2 through RACE 5 [161-164]. For coding instructions and race code history see the current *SEER Program Coding and Staging Manual*^3^. Reference to Census 2000 definitions for ethnicity and race: <http://www.census.gov/prod/cen2000/doc/sf2.pdf> (Appendix G).01-08, 10-17, 20-22, 25-28, 30-32, 96-99Race.R\*Code 09 was retired effective with Version 12. See codes 15-17.digitsRight justified, zero filledRPatientBecause race has a significant association with cancer rates and outcomes, a comparison between areas with different racial distributions may require an analysis of race to interpret the findings. The race codes listed correspond closely to race categories used by the U.S. Census Bureau to allow calculation of race-specific incidence rates. The full coding system should be used to allow accurate national comparison and collaboration, even if the state population does not include many of the race categories.A,C,I,MDemographicRSEER/CoC
161Race 2race22Code the patient’s race. Race is coded separately from Spanish/Hispanic Origin [190]. All tumors for the same patient should have the same race codes. If the patient is multiracial, code all races using RACE 2 through RACE 5 [161-164]. For coding instructions and race code history see the current *SEER Program Coding and Staging Manual*^3^. Reference to Census 2000 definitions for ethnicity and race: <http://www.census.gov/prod/cen2000/doc/sf2.pdf> (Appendix G).01-08, 10-17, 20-22, 25-28, 30-32, 88, 96-99, blank..*\*Code 09 was retired effective with Version 12. See codes 15-17. Note:* If diagnosed prior to 2000 and any race code (Race 2, 3, 4, or 5) is blank, all subsequent race codes must be blank. If diagnosed after 1999 and any race code (for Race 2, 3, 4, and 5) is 88 (no further race documented), then all subsequent race codes also must be 88. If any race equals 99, then all race codes (Race 1, 2, 3, 4, and 5) must be 99.digitsRight justified, zero filledRPatientBecause race has a significant association with cancer rates and outcomes, a comparison between areas with different racial distributions may require an analysis of race to interpret the findings. The race codes listed correspond closely to race categories used by the U.S. Census Bureau to allow calculation of race-specific incidence rates. The full coding system should be used to allow accurate national comparison and collaboration, even if the state population does not include many of the race categories.A,C,I,MDemographicRSEER
162Race 3race32Code the patient’s race. Race is coded separately from Spanish/Hispanic Origin [190]. All tumors for the same patient should have the same race codes. If the patient is multiracial, code all races using RACE 2 through RACE 5 [161-164]. For coding instructions and race code history see the current *SEER Program Coding and Staging Manual*^3^.   Reference to Census 2000 definitions for ethnicity and race: <http://www.census.gov/prod/cen2000/doc/sf2.pdf> (Appendix G).01-08, 10-17, 20-22, 25-28, 30-32, 88, 96-99, blank..\*Code 09 was retired effective with Version 12. See codes 15-17. *Note:* If diagnosed prior to 2000 and any race code (Race 2, 3, 4, or 5) is blank, all subsequent race codes must be blank. If diagnosed after 1999 and any race code (for Race 2, 3, 4, and 5) is 88 (no further race documented), then all subsequent race codes also must be 88. If any race equals 99, then all race codes (Race 1, 2, 3, 4, and 5) must be 99.digitsRight justified, zero filledRPatientBecause race has a significant association with cancer rates and outcomes, a comparison between areas with different racial distributions may require an analysis of race to interpret the findings. The race codes listed correspond closely to race categories used by the U.S. Census Bureau to allow calculation of race-specific incidence rates. The full coding system should be used to allow accurate national comparison and collaboration, even if the state population does not include many of the race categories.A,C,I,MDemographicRSEER
163Race 4race42Code the patient’s race. Race is coded separately from Spanish/Hispanic Origin [190]. All tumors for the same patient should have the same race codes. If the patient is multiracial, code all races using RACE 2 through RACE 5 [161-164]. For coding instructions and race code history see the current *SEER Program Coding and Staging Manual*^3^. Reference to Census 2000 definitions for ethnicity and race: <http://www.census.gov/prod/cen2000/doc/sf2.pdf> (Appendix G).01-08, 10-17, 20-22, 25-28, 30-32, 88, 96-99, blank..*\* Code 09 was retired effective with Version 12. See codes 15-17., Codes Note:* If diagnosed prior to 2000 and any race code (Race 2, 3, 4, or 5) is blank, all subsequent race codes must be blank. If diagnosed after 1999 and any race code (for Race 2, 3, 4, and 5) is 88 (no further race documented), then all subsequent race codes also must be 88. If any race equals 99, then all race codes (Race 1, 2, 3, 4, and 5) must be 99.digitsRight justified, zero filledRPatientBecause race has a significant association with cancer rates and outcomes, a comparison between areas with different racial distributions may require an analysis of race to interpret the findings. The race codes listed correspond closely to race categories used by the U.S. Census Bureau to allow calculation of race-specific incidence rates. The full coding system should be used to allow accurate national comparison and collaboration, even if the state population does not include many of the race categories.A,C,I,MDemographicRSEER
164Race 5race52Code the patient’s race. Race is coded separately from Spanish/Hispanic Origin [190]. All tumors for the same patient should have the same race codes. If the patient is multiracial, code all races using RACE 2 through RACE 5 [161-164]. For coding instructions and race code history see the current *SEER Program Coding and Staging Manual*^3^. Reference to Census 2000 definitions for ethnicity and race: <http://www.census.gov/prod/cen2000/doc/sf2.pdf> (Appendix G).01-08, 10-17, 20-22, 25-28, 30-32, 88, 96-99, blank..\*Code 09 was retired effective with Version 12. See codes 15-17. *Note:* If diagnosed prior to 2000 and any race code (Race 2, 3, 4, or 5) is blank, all subsequent race codes must be blank. If diagnosed after 1999 and any race code (for Race 2, 3, 4, and 5) is 88 (no further race documented), then all subsequent race codes also must be 88. If any race equals 99, then all race codes (Race 1, 2, 3, 4, and 5) must be 99digitsRight justified, zero filled.RPatientBecause race has a significant association with cancer rates and outcomes, a comparison between areas with different racial distributions may require an analysis of race to interpret the findings. The race codes listed correspond closely to race categories used by the U.S. Census Bureau to allow calculation of race-specific incidence rates. The full coding system should be used to allow accurate national comparison and collaboration, even if the state population does not include many of the race categories.A,C,I,MDemographicRSEER
190Spanish/Hispanic OriginspanishHispanicOrigin1Code identifying persons of Spanish or Hispanic origin. This code is used by hospital and central registries to show the “best guess” as to whether or not the person should be classified as Hispanic for purposes of calculating cancer rates. If the patient has multiple tumors, all records should have the same code. All information resources should be used to determine the correct code, including: * Stated ethnicity in the medical record * Stated Hispanic origin on the death certificate * Birthplace * Information about life history and/or language spoken found during the abstracting process * Patient’s last name \[2230\] or maiden name \[2390\] found on a list of Hispanic names Some registries code the information from the medical record, others code ethnicity based on Spanish names, and others use a combination of methods. Persons of Spanish or Hispanic origin may be of any race, but these categories generally are not used for Native Americans, Filipinos, etc., who may have Spanish names. If a patient has an Hispanic name, but there is reason to believe they are not Hispanic (e.g., the patient is Filipino, or the patient is a woman known to be non-Hispanic who has a Hispanic married name), the code in this field should be 0 (non-Spanish, non-Hispanic). The code in item Computed Ethnicity \[200\], however, would reflect the Hispanic name. Assign code 7 if Hispanic ethnicity is based strictly on a computer list or algorithm (unless contrary evidence is available) and also code in Computed Ethnicity \[200\]. See also Computed Ethnicity \[200\]. _Note:_ NAACCR recognizes that available definitions and abstracting instructions for Name--Last \[2230\] and Name--Maiden \[2390\] 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 that abstracting and coding practice for these items varies across registries. Limitations inherent in these definitions should be kept in mind when using the data.0-8, 9Spanish Origin--All Sources (96 CoC), Spanish Surname or Origin (SEER).R_Note:_ Code 7 was adopted for use effective with 1994 diagnosis and modified December 1994. _Note:_ Code 8 was added in Standards Volume II Version 10.2, effective January 2005, however, abstractors may assign code 8 to tumors diagnosed prior to 2005.digitsRPatientSee the rationales for the Race 1-5 \[160-164\] and Computed Ethnicity \[200\]. Ethnic origin has a significant association with cancer rates and outcomes. Hispanic populations have different patterns of occurrence of cancer from other populations that may be included in the “white” category of Race \[160\].A,C,I,MDemographicRSEER/CoC
191NHIA Derived Hisp OriginnhiaDerivedHispOrigin1The 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 Assigned at Birth \[221\]. 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: \<[https://www.naaccr.org/analysis-and-data-improvement-tools/#1694105514557-1c34e1d6-0712](https://www.naaccr.org/analysis-and-data-improvement-tools/#1694105514557-1c34e1d6-0712)\>.0-8, blank.._Note:_ Code 8 was added in Standards Volume II Version 10.2 effective January 2005.Revised Description to reflect new Sex Assigned at Birth [221] data item. Updated link.digitsDPatientSometimes 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.A,C,I,MDemographicDNAACCR10.22005
193Race--NAPIIA(derived API)raceNapiia2NAPIIA is an acronym for NAACCR Asian and Pacific Islander Identification Algorithm. Race--NAPIIA(derived API) recodes some single-race cases with a Race 1 [160] code of 96 to a more specific Asian race category, based on an algorithm that makes use of the birthplace and name fields (first, last, and birth-surname). For single-race cases with a Race 1 code other than 96, it returns the Race 1 code. Multiple-race cases (those with information in Race 2 through Race 5, [161-164]) are handled variously; for greater detail please refer to the technical documentation: <http://www.naaccr.org/LinkClick.aspx?fileticket=3HnBhlmhkBs%3d&tabid=118&mid=458> In Version 1.1 of the algorithm, birthplace can be used to indirectly assign a specific race to one of eight Asian race groups (Chinese, Japanese, Vietnamese, Korean, Asian Indian, Filipino, Thai, and Cambodian), and names can be used to indirectly assign a specific race to one of seven Asian groups (Chinese, Japanese, Vietnamese, Korean, Asian Indian, Filipino, and Hmong). Subsequent versions of NAPIIA may incorporate Pacific Islanders and may potentially incorporate name lists for Thai, Cambodian, and Laotians.01-08, 10-17, 20-22, 25-28, 30-32, 96, 99, blankRace--NAPIIA..\* Code 09 was retired effective with Version 12. See codes 15-17.digitsRight justified, zero filledRPatientThe use of more specific Asian and Pacific Islander codes will enhance surveillance and research activities focused on specific API subgroups.A,C,I,MDemographic.NAACCR11.32009
194IHS Purchased/Referred Care Delivery AreaihsPurchRefCareDeliveryArea1IHS Purchased/Referred Care Delivery Areas (PRCDA) consist of counties which include all or part of an American Indian/Alaska Native (AI/AN) reservation and any county or counties which have a common boundary with a reservation. This derived data item facilitates the production of the most accurate and reliable incidence rates for the AI/AN population and was previously known as IHS Contract Health Service Delivery Area (CHSDA). The PRCDA data item is derived using NAACCR\*Prep based on state and county at the time of diagnosis, according to the Indian Health Service (IHS) PRCDA definition in the most recent definition in the Federal Register.0, 1, 9..textDTumorData analyses restricted to areas where the IHS provides health care services improves the accuracy of cancer statistics among American Indian and Alaska Native people.A,C,I,MDemographicDNPCR222022
200Computed EthnicitycomputedEthnicity1Code 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].0-7, blank.. *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.digits.PatientOne 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.A,C,I,MDemographicDSEER41995
210Computed Ethnicity SourcecomputedEthnicitySource1Code identifying the method used to determine ethnicity as recorded in Computed Ethnicity [200].0-9, blank..*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.digits.PatientA,C,I,MDemographicRSEER
225Sex Assigned at BirthsexAssignedAtBirth1This new data item will replace existing data item Sex \[220\] for all cases regardless of diagnosis year. Existing data in Sex \[220\] will be converted and used to populate the new data item.1, 2, 9RRNewNewNewNewNewdigits**Coding Instructions** 1. Assign the sex of the patient assigned at birth. 2. When the patient’s sex is documented as male or female, and there is no other information to indicate the patient was assigned a different sex at birth, assign code 1 or 2, respectively. 3. When sex is not known. a. Assign code 1 when the primary site is C600-C639. b. Assign code 2 when the primary site is C510-C589. c. Assign code 9 for primary sites not included above. 4. Assign code 9 when sex is unknown (excluding number 3a and 3b above) or sex is not yet determined. a. Do not assign code 9 when sex is documented as male or female and there is no other information about sex assigned at birth. 5. Assign code 9 if patient is born with Disorders of Sexual Development (DSD) and sex is not clearly defined. 6. Assign code 9 when patient’s sex is documented as other than male or female (e.g., non-binary, transsexual), and there is no additional information about sex assigned at birth.RPatientNewNewA,C,I,MNewNewDemographicRNAACCR262026
230Age at DiagnosisageAtDiagnosis3Age of the patient at diagnosis in complete years. Different tumors for the same patient may have different values.000-120, 999DRdigitsRight justified, zero filledRTumorA,C,I,MDemographicRSEER/CoC
240Date of BirthdateOfBirth8Date of birth of the patient. See [**Data Descriptor Table**](https://apps.naaccr.org/data-dictionary/data-dictionary/version=24/chapter-view/data-descriptor-table/) 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.Valid dateBirth Date(SEER/CoC/CCCR)RRdateYYYYMMDDRPatientA,C,I,MDemographicRSEER/CoC
252Birthplace--StatebirthplaceState2USPS 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].USPS abbreviations and CanadaPost abbreviations; also a few local codes to capture legacy definitions, including unknowns, consistent with the codes allowable for Addr at Dx--State [80].RRSee 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](http://seer.cancer.gov/tools/codingmanuals/index.html)).alphaUpper caseR*PatientThis 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.A,C,I,MDemographicRNAACCR132013
254Birthplace--CountrybirthplaceCountry3Code 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].International Standards Organization (ISO) 3166-1 Country Three Character Codes; custom codes:ZZN, ZZC, ZZS, ZZP, ZZE, ZZF, ZZA, ZZX, ZZU, XNI, XCB, XEN, XSC, XGR, XSL, CSK, YUG, XUM, XNF, XSD, XWF, XSF, XEF, XIF, XET, XAP, XIS, XCR, XOR, XSE, XMS, XCH, XML, XMC, XPL. See Appendix B for complete list of country names and corresponding three character alpha codes.RRSee 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](http://seer.cancer.gov/tools/codingmanuals/index.html)).alphaUpper caseR*PatientPlace 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.A,C,I,MDemographicRNAACCR132013
272Census Ind Code CDCcensusIndCode20104Code for the patient’s usual industry, using the [North American Industry Classification System](https://www.census.gov/naics) (NAICS), Standard [Occupational Classification System](https://www.bls.gov/soc) (SOC), and/or [Census Industry and Occupation Classification System](https://www.census.gov/topics/employment/industry-occupation/guidance/code-lists.html). Additional information on collecting and using this data are available from the [National Institute for Occupational Safety and Health](https://www.cdc.gov/niosh/topics/coding/code.html) (NIOSH). The automated coding system available from NIOSH, Industry and Occupation Computerized Coding System (NIOCCS), is the preferred resource. NIOCCS is a free auto-coder that codes large files of industry and occupation free-text descriptions to Census industry and occupation codes, NAICS codes, and SOC 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.Valid 4 digit numbers, BlankCensus Ind Code 2010 CDC, Census Industry Code--2010..The Division of Safety Research at CDC’s National Institute for Occupational Safety and Health (NIOSH) has developed new web-based software for automated coding of industry and occupation to appropriate year Census (1990, 2000, or 2010) classifications. This system also includes the NIOSH non-paid worker codes. See the following website for the NIOSH Industry and Occupation Computerized Coding System (NIOCCS) to look up a single industry and occupation code, crosswalk a single record, or create an account to perform batch processing: \<https://www.cdc.gov/niosh/topics/coding/code.html\>. For more information related to the U.S. Census Bureau codes, see the following websites: * Overview: \<https://www.census.gov/topics/employment/industry-occupation/guidance.html\> * Crosswalk: \<https://www.census.gov/topics/employment/industry-occupation/guidance/code-lists.html\> * Index: [https://www.census.gov/topics/employment/industry-occupation/guidance/indexes.html](https://www.census.gov/topics/employment/industry-occupation/guidance/indexes.html)digitsUse the [NIOSH Industry and Occupation Computerized Coding System (NIOCCS)](https://csams.cdc.gov/nioccs/Default.aspx) to assign codes for paid and non-paid workers. NIOCCS is regularly updated as classification systems changeR*TumorThe usual (longest-held) occupation and industry of workers can reveal the national cancer burden by industry and occupation. Such information can also be used to help discover jobs that may have a high risk for cancer or other diseases and for which prevention efforts can be concentrated (or targeted). Coding the data allows public health officials and other researchers to assess patterns and trends in work-related diseases, injuries, and exposures.A,C,I,MDemographic.Census/NPCR132013
282Census Occ Code CDCcensusOccCode20104Code for the patient’s usual occupation, using the [North American Industry Classification System](https://www.census.gov/naics) (NAICS), [Standard Occupational Classification System](https://www.bls.gov/soc) (SOC), and/or [Census Industry and Occupation Classification System](https://www.census.gov/topics/employment/industry-occupation/guidance/code-lists.html). Additional information on collecting and using this data are available from [the National Institute for Occupational Safety and Health](https://www.cdc.gov/niosh/topics/coding/code.html) (NIOSH). The automated coding system available from NIOSH, Industry and Occupation Computerized Coding System (NIOCCS), is the preferred resource. NIOCCS is a free auto-coder that codes large files of industry and occupation free-text descriptions to Census industry and occupation codes, NAICS codes, and SOC 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 lifeValid 4-digit numbers, BlankCensus Occ Code 2010, Census Occ Code 2010 CDC..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](mailto:sxn1@cdc.gov) or (513) 841-4467.   For more information related to the U.S. Census Bureau codes, see the following websites: * Overview: \<https://www.census.gov/topics/employment/industry-occupation/guidance.html\> * Crosswalk: \<https://www.census.gov/topics/employment/industry-occupation/guidance/code-lists.html\>. The 2002 Census codes are the same as the 2000 codes with a “0” added to the end of the number due to the change from a 3-digit to 4-digit field. * Index: \<https://www.census.gov/topics/employment/industry-occupation/guidance/indexes.html\>digitsUse the [NIOSH Industry and Occupation Computerized Coding System (NIOCCS)](https://csams.cdc.gov/nioccs/Default.aspx) to assign codes for paid and non-paid workers. NIOCCS is regularly updated as classification systems changeR*TumorThe usual (longest-held) occupation and industry of workers can reveal the national cancer burden by industry and occupation. Such information can also be used to help discover jobs that may have a high risk for cancer or other diseases and for which prevention efforts can be concentrated (or targeted). Coding the data allows public health officials and other researchers to assess patterns and trends in work-related diseases, injuries, and exposures.A,C,I,MDemographic.Census/NPCR132013
284Urban Indian Organization (UIO)urbanIndianHealthOrganization1UIO is derived using NAACCR\*Prep based on the state and county at the time of diagnosis according to the Urban Indian Health Institute Community Health Profile, National Aggregate of Urban Indian Organization Service Areas.0, 1, 9..textDTumorData analyses restricted to UIO service areas improve the accuracy of cancer statistics for urban American Indian and Alaska Native (AI/AN) people. UIO service areas consist of counties where AI/AN people originally lived, or where they migrated because of the Indian Relocation Act of 1956. These counties are served by the Urban Indian Health Program and other Urban Indian Organizations. This derived data item facilitates the production of incidence rates for urban American Indian and Alaska Native people.A,C,I,MDemographicDNPCR222022
285Urban Indian Organization (UIO) Service AreauihoFacility2UIO Service Area is derived using NAACCR\*Prep based on the state and county at the time of diagnosis. It includes Urban Indian Organization service areas that contain Urban Indian Health Programs and other Urban Indian Organizations that provide health care to urban American Indian and Alaska Native people.00-52UIHO City, Urban Indian Health Organization City..textNumericDTumorData analyses restricted to UIO service areas improve the accuracy of cancer statistics for urban American Indian and Alaska Native (AI/AN) people. This derived data item facilitates the production of incidence rates for urban American Indian and Alaska Native people.A,C,I,MDemographicDNPCR
290Occupation SourceoccupationSource1Code 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).0-3, 7-9, blank..digitsR*TumorOccupation information may come from a variety of sources. The most valid and reliable source of occupation information for patients has not yet been determined.A,C,I,MDemographic.NPCR
300Industry SourceindustrySource1Code 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).0-3, 7-9, blank..digitsR*TumorIndustry information may come from a variety of sources. The most valid and reliable source of industry information for patients has not yet been determined.A,C,I,MDemographic.NPCR
310Text--Usual OccupationtextUsualOccupation100Text area for information about the patient’s usual occupation, also known as usual type of job or work.Neither carriage return nor line feed characters allowed..textFree textR*TumorUsed to identify new work-related health hazards; serves as an additional measure of socioeconomic status; identifies occupational groups in which cancer screening or prevention activities may be beneficial. The data item “usual occupation” is defined identically as on death certificates and conforms to the 1989 revision of the U.S. Standard Certificate of Death.^25^ See related materials in reference list, Chapter VII.  **Abstracting Instructions** Record the patient’s usual occupation (i.e., the kind of work performed during most of the patient’s working life before diagnosis of this tumor). Do not record “retired.” If usual occupation is not available or is unknown, record the patient’s current or most recent occupation, or any available occupation. If later documentation in the patient’s record provides an occupation that is more likely to be the usual occupation than what was originally recorded, facility registrars are encouraged to update the abstract with the new information. However, it is not the responsibility of the facility registrars to update abstracts with occupation information provided on death certificates. Comparison with death certificate information should be the function of a central or regional registry. If the patient was a homemaker and also worked outside the home during most of his/her adult life, record the usual occupation outside the home; if the patient was a homemaker and did not work outside the home for most of his/her adult life, record “homemaker.” If the patient was not a student or homemaker and had never worked, record “never worked” as the usual occupation. If no information is available, record “unknown.” This data item usually is collected only for patients who are age 14 years or older at the time of diagnosis.A,C,I,MDemographic.NPCR
320Text--Usual IndustrytextUsualIndustry100Text area for information about the patient’s usual industry, also known as usual kind of business/industry.Neither carriage return nor line feed characters allowed..textFree textR*TumorUsed to identify new work-related health hazards; serves as an additional measure of socioeconomic status; identifies industrial groups or worksite-related groups in which cancer screening or prevention activities may be beneficial. The data item “usual industry” is defined identically as on death certificates and conforms to the 1989 revision of the U.S. Standard Certificate of Death.^25^ See related materials in reference list, Chapter VII.  **Abstracting Instructions** Record the primary type of activity carried on by the business/industry at the location where the patient was employed for the most number of years before diagnosis of this tumor. Be sure to distinguish among “manufacturing,” “wholesale,” “retail,” and “service” components of an industry that performs more than one of these components. If the primary activity carried on at the location where the patient worked is unknown, it may be sufficient for facility registrars to record the name of the company (with city or town) in which the patient performed his/her usual industry. In these situations, if resources permit, a central or regional registry may be able to use the employer name and city/town to determine the type of activity conducted at that location. As noted in the Text--Usual Occupation \[310\] section, in those situations where the usual occupation is not available or is unknown, the patient’s current or most recent occupation is recorded, if available. The information for industry should be based upon the information in occupation. Therefore, if current or most recent occupation rather than usual occupation was recorded, record the patient’s current or most recent business/industry. If later documentation in the patient’s record provides an industry that is more likely to be the usual industry than what was originally recorded, facility registrars are encouraged to update the abstract with the new information. However, it is not the responsibility of the facility registrars to update abstracts with industry information provided on death certificates. Comparison with death certificate information should be the function of a central or regional registry. There should be an entry for Text--Usual Industry if any occupation is recorded. If no information is available regarding the industry in which the reported occupation was carried out, record “unknown.” If the patient was not a student or homemaker and had never worked, record “never worked” as the usual industry. This data item usually is collected only for patients who are age 14 years or older at the time of diagnosis.A,C,I,MDemographic.NPCR
331Geocoding Accuracy ScoregeocodingAccuracyScore4Spatial analysis of cancer data often requires identifying case records that were geocoded. Researchers and registry staff can use this code to select geocoded records and determine which records need to be reviewed and geocoded again. This code can also be used to determine inclusion/exclusion and potential for bias for geospatial analysis of cancer data. Historically, Census Tract Certainty \[369\] and NAACCR GIS Coordinate Quality \[366\] codes have been used to determine geocoding quality. With the old NAACCR geocoder, we had additional codes, Geocoding Quality Code \[86\] and Geocoding Quality Detail \[87\], which provided more information on the geocoded data’s precision and accuracy. This data item, along with Geocoding Accuracy Type \[332\], are the new geocoder’s (Geocodio) version of quality measures.  This measure is output as the Accuracy Score by the current geocoder and has been available since July 1, 2024. This code describes the quality of the geocoding match. Additional resources on how to use the measure to identify high quality geocoded cases are available on the GIS Resources page: [https://www.naaccr.org/gis-resources/](https://www.naaccr.org/gis-resources/). This is intended to be used in conjunction with the Geocoding Accuracy Type \[332\] to assess geocoding quality.0.0-1, Blank..This item is not coded directly. This data item is generated by the Geocodio geocoding software. The score can have up to two decimal places. It is recommended that this data item is incorporated as is from Geocodio with no additional formatting. For additional information see:  [https://www.naaccr.org/gis-resources/#1718042516172-895b9fd0-c634](https://www.naaccr.org/gis-resources/#1718042516172-895b9fd0-c634)NewNewNewNewNewnumeric2 decimal places and a leading zeroD*TumorWith the switch to the new geocoder, we no longer have access to the more detailed, NAACCR designed quality measures (Geocoding Quality Code \[86\] and Geocoding Quality Detail \[87\]). However, it is crucial to reduce bias in geospatial analysis that we identify and improve the quality of the geocoded data in our registries.NewNewA,C,I,MNewNewDemographicDNAACCR262026
332Geocoding Accuracy TypegeocodingAccuracyType21Spatial analysis of cancer data often requires identifying case records that were geocoded. Researchers and registry staff can use this code to select geocoded records and determine which records need to be reviewed and geocoded again. This code can also be used to determine inclusion/exclusion and potential for bias for geospatial analysis of cancer data. Historically, Census Tract Certainty \[369\] and NAACCR GIS Coordinate Quality \[366\] codes have been used to determine geocoding quality. With the old NAACCR geocoder, we had additional codes, Geocoding Quality Code \[86\] and Geocoding Quality Detail \[87\], which provided more information on the geocoded data’s precision and accuracy. This data item, along with Geocoding Accuracy Score \[331\], are the new geocoder’s (Geocodio) version of quality measures.  This measure is output as the Accuracy Type by the current geocoder and has been available since July 1, 2024. This code describes the precision of the geocoding match to the underlying street reference files. Additional resources on how to use the measure to identify high quality geocoded cases will be available on the GIS Resources page: [https://www.naaccr.org/gis-resources/](https://www.naaccr.org/gis-resources/). This is intended to be used in conjunction with the Geocoding Accuracy Score \[331\] to assess geocoding quality.rooftop, point, range_interpolation, nearest_rooftop_match, intersection, street_center, place, county, state, Blank..This data item is an indicator of the level of precision of a geocoded result. It is not coded directly. This data item is generated by the Geocodio geocoding software. It is recommended that this data item is incorporated as is from Geocodio with no additional formatting. For additional information see:  [https://www.naaccr.org/gis-resources/#1718042516172-895b9fd0-c634.](https://www.naaccr.org/gis-resources/#1718042516172-895b9fd0-c634) Codes are listed in order of level of precision, with rooftop being the most precise.NewNewNewNewNewtextleft justifiedD*TumorWith the switch to the new geocoder, we no longer have access to the more detailed, NAACCR designed quality measures (Geocoding Quality Code \[86\] and Geocoding Quality Detail \[87\]). However, it is crucial to reduce bias in geospatial analysis that we identify and improve the quality of the geocoded data in our registries.NewNewA,C,I,MNewNewDemographicDNAACCR262026
339RUCA 2000ruca20001A measure of how accessible to an urban center a cancer patient's census tract at diagnosis is based on the USDA identification of urban and rural commuting areas. The variable is a binomial-either in an urban commuting area or not. The measure indicates proximity to large urban centers and can be an indicator of access to oncology specialists and cancer treatment facilities. Collecting the variable with each decennial census allows for retrospective and cross-sectional epidemiologic analysis.1, 2, 9, A, B, C, CRural Urban Commuting Area-Tract-level 2000.._Note_: This is a derived variable. Currently, the variable is derived during call for data. However, SAS code to derive the variable at the central registry variable for local use is available on the NAACCR website.RevisedRevisedRevised Code 9, added Codes A, B, C, DmixedDTumorStudies have shown that residents of rural areas have lower screening rates, lower rates of follow-up of abnormal screening tests, higher late-stage diagnosis rates, and differences in cancer treatment patterns. Including tract-level indicators of rural-urban residence in the NAACCR data files will facilitate research in rural-urban disparities and allow researchers to control for rural-urban differences in model-based analysis of cancer risks and outcomes. Using these codes allows cancer registries to release the area-based measure instead of more sensitive information such as address or long/lat. The measure has been tested for uniqueness and the categories selected/aggregated so that identification of individual level census tracts is not possible as long as county is not known. Therefore, unless the researcher can scientifically defend the need for county, the county identifier will not be released in the same database.A,C,I,MDemographicDNAACCR182018
341RUCA 2010ruca20101A measure of how accessible to an urban center a cancer patient's census tract at diagnosis is based on the USDA identification of urban and rural commuting areas. The variable is a binomial-either in an urban commuting area or not. The measure indicates proximity to large urban centers and can be an indicator of access to oncology specialists and cancer treatment facilities. Collecting the variable with each decennial census allows for retrospective and cross-sectional epidemiologic analysis.1, 2, 9, A, B, C, DRural Urban Commuting Area-Tract-level 2010.._Note_: This is a derived variable. Currently, the variable is derived during call for data. However, SAS code to derive the variable at the central registry variable for local use is available on the NAACCR website.RevisedRevisedRevised Code 9, added Codes A, B, C, DmixedDTumorStudies have shown that residents of rural areas have lower screening rates, lower rates of follow-up of abnormal screening tests, higher late-stage diagnosis rates, and differences in cancer treatment patterns. Including tract-level indicators of rural-urban residence in the NAACCR data files will facilitate research in rural-urban disparities and allow researchers to control for rural-urban differences in model-based analysis of cancer risks and outcomes. Using these codes allows cancer registries to release the area-based measure instead of more sensitive information such as address or long/lat. The measure has been tested for uniqueness and the categories selected/aggregated so that identification of individual level census tracts is not possible as long as county is not known. Therefore, unless the researcher can scientifically defend the need for county, the county identifier will not be released in the same database.A,C,I,MDemographicDNAACCR182018
342RUCA 2020ruca20201A measure of how accessible to an urban center a cancer patient’s census tract at diagnosis is based on the USDA identification of urban and rural commuting areas. The variable is a binomial—either in an urban commuting area or not. The measure indicates proximity to large urban centers and can be an indicator of access to oncology specialists and cancer treatment facilities. Collecting the variable with each decennial census allows for retrospective and cross-sectional epidemiologic analysis.1, 2, 9, A, B, C, D..This variable is not coded directly. This data item is generated during CFD by NAACCR\*Prep or File\*Pro at any time.NewNewNewNewNewtextDTumorThis is an update to existing fields. To allow flexibility of research questions, all years of RUCA can be collected for all cases, but cases diagnosed 2016 forward should have RUCA 2020 appended using NAACCR\*Prep or File\*Pro.NewNewA,C,I,MNewNewDemographicDNAACCR262026
344Tobacco Use Smoking StatustobaccoUseSmokingStatus1Tobacco Use Smoking Status indicates the patient’s past or current smoking use of tobacco (cigarette, cigar and/or pipe).0-3, 9.R* Record cigarette, cigar, and/or pipe use only. Tobacco Use Smoking Status does not include marijuana, chewing tobacco, e-cigarettes, or vaping devices. * Tobacco smoking history can be obtained from sections such as the Nursing Interview Guide, Flow Chart, Vital Stats or Nursing Assessment section, or other available sources from the patient's hospital medical record or physician office record. * Use code 1 if there is evidence in the medical record that the patient quit smoking within 30 days prior to diagnosis. The 30 days prior information is intended to differentiate patients who may have quit recently due to symptoms that led to a cancer diagnosis.  * Use code 2 if medical record indicates patient smoked tobacco in the past, but does not smoke now. Patient must have quit 31 or more days prior to cancer diagnosis to be coded as ‘Former smoker.’ * Use code 3 if it cannot be determined whether the patient currently smokes or formerly smoked. For example, the medical record only indicates “Yes” for smoking without further information. * Use code 9 (Unknown if ever smoked) rather than code 0 (Never smoker), if * the medical record only indicates “No” for tobacco use; * smoking status is not stated or provided; or * the method (cigarette, pipe, cigar) used cannot be verified in the chart. * This data item can be left blank for cases diagnosed prior to 1/1/2022.textR*TumorReliable registry-based tobacco use data will help public health planners and clinicians target and assess tobacco control efforts. Tobacco use data at diagnosis may help health professionals better understand how tobacco use impacts cancer outcomes, prognosis, and effectiveness of treatment. Smoking status may be a useful covariate risk factor for cancer cluster investigations.A,C,I,MCCCR from R to .DemographicR*NPCR222022
345URIC 2000uric20001A measure of how urban a cancer patient's census tract at diagnosis is based on the Census Bureau's identification of urban and rural areas (already collect at county-level). The variable is a 4 code continuum. The measure indicates of the rural nature of the place of residence and can be an indicator of access to recreation, access to food stores, exposures to pollutants, crime levels, social cohesion, etc. Collecting the variable with each decennial census allows for retrospective and cross-sectional epidemiologic analysis.1-4, 9, A, B, C, DUrban Rural Indicator Code-Tract-level 2000.._Note_: This is a derived variable. Currently, the variable is derived during call for data. However, SAS code to derive the variable at the central registry variable for local use is available on the NAACCR website.RevisedRevisedRevised Codes 3, 9; added Codes A, B, C, DmixedDTumorStudies have shown that residents of rural areas have lower screening rates, lower rates of follow-up of abnormal screening tests, higher late-stage diagnosis rates, and differences in cancer treatment patterns. Including tract-level indicators of rural-urban residence in the NAACCR data files will facilitate research in rural-urban disparities and allow researchers to control for rural-urban differences in model-based analysis of cancer risks and outcomes. Using these codes allows cancer registries to release the area-based measure instead of more sensitive information such as address or long/lat. The measure has been tested for uniqueness and the categories selected/aggregated so that identification of individual level census tracts is not possible as long as county is not known. Therefore, unless the researcher can scientifically defend the need for county, the county identifier will not be released in the same database.A,C,I,MDemographicDNAACCR182018
346URIC 2010uric20101A measure of how urban a cancer patient's census tract at diagnosis is based on the Census Bureau's identification of urban and rural areas (already collect at county-level). The variable is a 4 code continuum. The measure indicates of the rural nature of the place of residence and can be an indicator of access to recreation, access to food stores, exposures to pollutants, crime levels, social cohesion, etc. Collecting the variable with each decennial census allows for retrospective and cross-sectional epidemiologic analysis.1-4, 9, A, B, C, DUrban Rural Indicator Code-Tract-level 2010.._Note_: This is a derived variable. Currently, the variable is derived during call for data. However, SAS code to derive the variable at the central registry variable for local use is available on the NAACCR website.RevisedRevisedRevised Codes 2, 9; added Codes A, B, C, DmixedDTumorStudies have shown that residents of rural areas have lower screening rates, lower rates of follow-up of abnormal screening tests, higher late-stage diagnosis rates, and differences in cancer treatment patterns. Including tract-level indicators of rural-urban residence in the NAACCR data files will facilitate research in rural-urban disparities and allow researchers to control for rural-urban differences in model-based analysis of cancer risks and outcomes. Using these codes allows cancer registries to release the area-based measure instead of more sensitive information such as address or long/lat. The measure has been tested for uniqueness and the categories selected/aggregated so that identification of individual level census tracts is not possible as long as county is not known. Therefore, unless the researcher can scientifically defend the need for county, the county identifier will not be released in the same database.A,C,I,MDemographicDNAACCR182018
347URIC 2020uric20201A measure of how urban a cancer patient’s census tract at diagnosis is based on the Census Bureau’s identification of urban and rural areas (already collect at county-level). The variable is a 4 code continuum. The measure indicates of the rural nature of the place of residence and can be an indicator of access to recreation, access to food stores, exposures to pollutants, crime levels, social cohesion, etc. Collecting the variable with each decennial census allows for retrospective and cross-sectional epidemiologic analysis.1, 2, 3, 4, 9, A, B, C, D..This variable is not coded directly. This data item is generated during CFD by NAACCR\*Prep or File\*Pro at any time.NewNewNewNewNewtextDTumorThis is an update to existing fields. To allow flexibility of research questions, all years of URIC can be collected for all cases, but cases diagnosed 2016 forward should have URIC 2020 appended using NAACCR\*Prep or File\*Pro.NewNewA,C,I,MNewNewDemographicDNAACCR262026
361Census Block Group 2020censusBlockGroup20201This field is provided for coding the block group of patient's residence at time of diagnosis, as defined by the 2020 Census.0-9, Blank..**Comment**: Historically, some registries made the distinction between "attempted, could not be determined" and "not coded" by using a 0 for "attempted." However, 0 is a valid block group value. _Note_: The values 0 through 9 are nominal, with no hierarchy of values. This number determines the first digit of all the blocks which comprise the block group; for instance, census block group 3 would contain blocks numbered 3000 to 3999.digits.TumorA block group is a subdivision of a census tract designed to have approximately 1500, socially homogeneous people, versus census tracts which are designed to have approximately 4000 people. All land area in the United States is described by a census block group in the 2020 Census. The Census Bureau publishes detailed population and socioeconomic data at this level. Block groups thus offer a high level of specificity for geographical and socioeconomic analyses. A block group has no meaning in the absence of a census tract. Refer to Census Tr Certainty 2020 \[369\] to ascertain basis of assignment of Census Block Group 2020.A,C,I,MDemographic.Census182018
362Census Block Group 2000censusBlockGroup20001This field is provided for coding the block group of patient’s residence at time of diagnosis, as defined by the 2000 Census.0-9, blank.**Comment** Numerous registries find the distinction between “attempted, could not be determined” (zero) and “not coded” (blank) to be useful for geocoding planning purposes..digits_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..TumorA 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.A,C,I,MSEER Collect; RevisedRevisedDemographicDCensus
363Census Block Group 2010censusBlockGroup20101This field is provided for coding the block group of patient’s residence at time of diagnosis, as defined by the 2010 Census.0-9, blank.**Comment** Numerous registries find the distinction between “attempted, could not be determined” (zero) and “not coded” (blank) to be useful for geocoding planning purposes..digits_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..TumorA 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.A,C,I,MDemographicRCensus12.12011
364Census Tr Cert 1970/80/90censusTrCert197080901Code 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.1-6, 9, blankCensus Tract Certainty..**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.digitsRH*TumorA,C,I,MDemographicRHSEER5.11997
365Census Tr Certainty 2000censusTrCertainty20001Code 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.1-6, 9, blank..**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.digitsRHTumorA,C,I,MDemographicRHNAACCR102003
366GIS Coordinate QualitygisCoordinateQuality2Code 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.00-12, 98, 99, blank.._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.digitsRight justified, zero filledR*TumorSpatial 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.A,C,I,MSEER Collect; RevisedRevisedDemographicDNAACCR112011
367Census Tr Certainty 2010censusTrCertainty20101Code 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.1-6, 9, blank..**Clarification of NPCR Status** | **Census-1990 data items:** | **Census-2000 data items:** | **Census-2010 data items:** | | --- | --- | --- | | Census Tract  1970/80/90  \[110\] | Census Tract  2000  \[130\] | Census Tract  2010  \[135\] | | Census Tr Cert 1970/80/90  \[364\] | Census Tr Certainty 2000  \[365\]  | Census Tr Certainty 2010  \[367\] | | Census Tract  Cod Sys--1970/80/90 \[120\] |   |   |   Information on census tract and census tract certainty is required. Census Tract and Census Tract Certainty should be recorded in the year-appropriate data item fields in order to reflect demographic information at the time of diagnosis. Until the 2010 Census is completed and data are available for geocoding, tumors diagnosed in 2010 or later, should be coded to the 2000 census definitions and recorded in Census Tract 2000 \[130\] and Census Tr Certainty 2000 \[365\]. When the 2010 Census data are available for geocoding, tumors diagnosed in 2010 or later must be coded to the 2010 census tract definitions and recorded in Census Tract 2010 \[135\] and Census Tract Certainty 2010 \[367\]. For tumors diagnosed between January 1, 2008, and December 31, 2009, use of Census Tract 2010 \[135\] and Census Track Certainty 2010 \[367\] is recommended.digitsRTumorA,C,I,MDemographicRNAACCR12.12011
368Census Block Grp 1970/80/90censusBlockGrp1970901This 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.0-9, blankCensus Block Grp 1970-90, CensusBlockGroup 70/80/90.**Comment:** Numerous registries find the distinction between “attempted, could not be determined” (zero) and “not coded” (blank) to be useful for geocoding planning purposes..digits_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.TumorA block group is a subdivision of a census tract or block numbering area (BNA). Not all of the United States was described by a census block group or BNA prior to the 2000 Census, but for areas assigned to block groups or BNAs, the Census Bureau published detailed population and socioeconomic data. Block groups thus offer a high level of specificity for geographical and socioeconomic analyses, where available. A block group has no meaning in the absence of a census tract. Refer to Census Tr Cert 1970/80/90 \[364\] to ascertain the basis of assignment of Census Block Grp 1970/80/90 \[368\]. Refer to Census Cod Sys 1970/80/90 \[120\] to ascertain the decade of reference.A,C,I,MSEER; RevisedRevisedDemographicDCensus11.22008
369Census Tract Certainty 2020censusTractCertainty20201Code indicating basis of assignment of census tract for an individual record. Helpful in identifying cases geocoded from incomplete information or P.O. Box. This item is not coded by the hospital. Central registry staff assign the code based on the results of geocoding.1-6, 9, Blank..**Clarification of NPCR Required Status** | Census-1990 data items: | Census-2000 data items: | Census-2010 data items: | Census-2020 data items: | | --- | --- | --- | --- | | Census Tract 1970/80/90 \[110\] | Census Tract 2000 \[130\] | Census Tract 2010 \[135\] | Census Tract 2020  \[371\] | | Census Tr Cert 1970/80/90 \[364\] | Census Tr Certainty 2000 \[365\] | Census Tr Certainty 2010 \[367\] | Census Tr Certainty 2020 \[369\] | | Census Tract Cod Sys--1970/80/90 \[120\] |   |   |   | Information on census tract and census tract certainty is required. Census Tract and Census Tract Certainty should be recorded in the year-appropriate data item fields in order to reflect demographic information at the time of diagnosis. Until the 2020 Census is completed and data are available for geocoding, tumors diagnosed in 2020 or later, should be coded to the 2010 census definitions and recorded in Census Tract 2010 \[135\] and Census Tr Certainty 2000 \[367\]. When the 2020 Census data are available for geocoding, tumors diagnosed in 2020 or later must be coded to the 2020 census tract definitions and recorded in Census Tract 2020 \[371\] and Census Tract Certainty 2020 \[369\]. For tumors diagnosed between January 1, 2018, and December 31, 2019, use of Census Tract 2020 \[371\] and Census Track Certainty 2020 \[369\] is recommended.digitsDTumorA,C,I,MDemographicDNAACCR182018
380Sequence Number--CentralsequenceNumberCentral2Code indicates the sequence of all reportable neoplasms over the lifetime of the person. This data item differs from Sequence Number-Hospital \[560\], because the definitions of reportable neoplasms often vary between a hospital and a central registry. Each neoplasm is assigned a different number. Sequence Number 00 indicates that the person has had only one _in situ_ or one malignant neoplasm as defined by the Federal reportable list (regardless of central registry reference date). Sequence Number 01 indicates the first of two or more reportable neoplasms, but 02 indicates the second of two or more reportable neoplasms, and so on. Because the time period of Sequence Number is a person’s lifetime, reportable neoplasms not included in the central registry (those that occur outside the registry catchment area or before the reference date) also are allotted a sequence number. For example, a registry may contain a single record for a patient with a sequence number of 02 because the first reportable neoplasm preceded the central registry’s reference date.  **Reporting Requirements: Federally Required and State/Province Defined**  The Federal or SEER/NPCR standard defining the reportable neoplasms is described in, [**Standards For Tumor Inclusion and Reportability**](https://apps.naaccr.org/data-dictionary/data-dictionary/version=24/chapter-view/standards-for-tumor-inclusion-and-reportability/)**.** It is assumed that this shared standard is the “minimum” definition of reportability. Individual central cancer registries may define additional neoplasms as reportable. Numeric codes in the 00-59 range indicate the sequence of neoplasms of _in situ_ or malignant behavior (2 or 3) at the time of diagnosis, which SEER/NPCR standards require to be reported. Codes 60 to 87 indicate the sequence of non-malignant tumors (as defined in [**Standards For Tumor Inclusion and Reportability**](https://apps.naaccr.org/data-dictionary/data-dictionary/version=24/chapter-view/standards-for-tumor-inclusion-and-reportability/)**.**) and any other neoplasms that the central registry has defined as reportable. Neoplasms required by SEER/NPCR with an _in situ_ or malignant behavior at the time of diagnosis are sequenced completely independently of this higher-numbered category. Sequence Number-Hospital does not affect Sequence Number-Central. The two notational systems are independent but central registries should take Sequence Number-Hospital \[560\] into account when coding Sequence Number Central.00-59, 60-87, 88, 98, 99Sequence Number (pre-96 SEER)D.The table that follows shows which sequence number series to use by type of neoplasm. | **Neoplasm** | **SeqNum-Central** | | --- | --- | | _**In Situ/Malignant as Federally Required based on Diagnosis Year**_ | _**(Numeric Series)**_ | | _In Situ (behavior code = 2) (Cervix CIS/CIN III, Diagnosis Year before 1996) (includes VIN III, VAIN III, AIN III)_ | _00 -- 59_ | | _Malignant (behavior code = 3)_ | _00 -- 59_ | | _Juvenile Astrocytoma, Diagnosis Year 2001+ (\*)_ | _00 -- 59_ | | _Invasive following In Situ--New primary as defined by CoC_ | _00 -- 59_ | | _Invasive following In Situ--New primary as defined by SEER_ | _00 -- 59_ | | _Unspecified Federally Required Sequence Number  or Unknown_ | _99_ | | _**Non-malignant Tumor as Federally Required based on Diagnosis Year or State/Province Registry-Defined**_ |   | | _Examples:_ |   | | _Non-malignant Tumor/Benign Brain_ | _60 -- 87_ | | _Borderline Ovarian, Diagnosis Year 2001+_ | _60 -- 87_ | | _Other Borderline/Benign_ | _60 -- 87_ | | _Skin SCC/BCC_ | _60 -- 87_ | | _PIN III_ | _60 -- 87_ | | _Cervix CIS/CIN III, Diagnosis Year 2003+_ | _60 -- 87_ | | _Unspecified Non-malignant Tumor or Central Registry-Defined Sequence Number_ | _88_ | | _Cervix CIS/CIN III, Diagnosis Year 1996-2002_ | _98_ | Note:\* See the section on Sequence Number--Central in The _SEER Program Code Manual_.  _Note:_ Conversion Guidance: The sequence numbers for neoplasms whose histologies were associated with behavior codes that changed from _in situ_/malignant to benign/borderline or vice versa during the conversion from ICD-O-2 to ICD-O-3 should not be re-sequenced.digitsRight justified, zero filledRTumorThe purpose of sequencing based on the patient’s lifetime is to truly identify the 00s, the people who only had one malignant primary in their lifetimes for survival analysis. If a central registry sequences by just what is reported to them, then it will be unclear whether 00 means the person only had one malignant primary in his lifetime or the person had one malignant primary since the central registry started collecting data. The Federally required reportable list has changed throughout the years, so the registry must use the appropriate reportable list for the year of diagnosis. The central registry reference date will not affect Sequence Number-Central.A,C,I,MCancer IdentificationRSEER
390Date of DiagnosisdateOfDiagnosis8Date of initial diagnosis by a recognized medical practitioner for the tumor being reported whether clinically or microscopically confirmed. See [**Data Descriptor Table**](https://apps.naaccr.org/data-dictionary/data-dictionary/version=24/chapter-view/data-descriptor-table/) for date format. For more discussion on determining date of diagnosis, consult the [_SEER Program Coding and Staging Manual_](http://seer.cancer.gov/tools/codingmanuals/) or CoC [_STORE_](http://www.facs.org/cancer/coc/fordsmanual.html) manual.Valid dateDate of Initial Diagnosis (CoC)RRdateYYYYMMDDRTumorA,C,I,MCancer IdentificationRSEER/CoC
400Primary SiteprimarySite4Code for the primary site of the tumor being reported using either ICD-O-2 or ICD-O-3. NAACCR adopted ICD-O-2 as the standard coding system for tumors diagnosed beginning January 1, 1992. In addition, NAACCR recommended that tumors diagnosed prior to 1992 be converted to ICD-O-2. The topography (primary site) codes did not change between ICD-O-2 and ICD-O-3.Refer to ICD-O-3 (decimals are dropped)IDC-O-2/3 Topography (CCCR)RR*Note:* See data item Site (73-91) ICD-O-1 [1960] for ICD-O-1 cases.textC followed by 3 digits, no special characters, no embedded blanksSee ICD-O-2,^14^ or ICD-O-3,^13^ Topography Section, for the codes for primary siteRTumorA,C,I,MCancer IdentificationRSEER/CoC
410Lateralitylaterality1Code 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.0-5, 9Laterality at Diagnosis (SEER)RRdigitsRTumorA,C,I,MCancer IdentificationRSEER/CoC
420Histology (92-00) ICD-O-2histologyIcdO24Codes 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.8000-9989, Refer to ICD-0-2Histology (CoC), ICD-O-2 Histology (CCCR)RHRH**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\].digitsSee ICD-O-2,^15^ Morphology SectionRHTumorA,C,I,MCancer IdentificationRHSEER/CoC
430Behavior (92-00) ICD-O-2behaviorIcdO21Code 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.0-3, Refer to ICD-0-2ICD-O-2 Behaviour (CCCR)RH**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\].RHValid codes are 0-3. See ICD-O-2,^15^ page 22, for behavior codes and definitions.digitsRHTumorA,C,I,MCancer IdentificationRHSEER/CoC
440Gradegrade1Code 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.1-9Grade, Differentiation, or Cell Lineage Indicator (SEER/CCCR), Grade/Differentiation (CoC)RHRH_Comment:_ Use the most recent Hematopoietic and Lymphoid rules for assigning grades 5-8.digitsSee the grade tables on page 67 of [ICD-O-3](http://www.who.int/classifications/icd/adaptations/oncology/en/).^16^ See also the most recent [CoC STORE](http://www.facs.org/cancer/coc/fordsmanual.html)manual and[SEER Program Code Manual](http://seer.cancer.gov/tools/codingmanuals/), for site specific coding rules and conversionsRHTumorA,C,I,MCancer IdentificationRHSEER/CoC
441Grade Path ValuegradePathValue1Describes the actual grade according to the grading system in Grade Path System [449].1-4, blank.RHdigitsRefer to the most recent version** **of**  ***[STORE](http://www.facs.org/cancer/coc/fordsmanual.html)* for additional instructions.RH*TumorThis data item will record grade specified in Grade Path System. This does not replace Grade [440].A,C,I,MCancer IdentificationRHAJCC122010
442Ambiguous Terminology DXambiguousTerminologyDx1Identifies 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.0-2, 9Ambiguous Terminology, Ambiguous Terminology as Basis for Diagnosis.RHRefer to [**Ambiguous Terms Diagnostic of Cancer**](https://apps.naaccr.org/data-dictionary/data-dictionary/version=24/chapter-view/standards-for-tumor-inclusion-and-reportability/ambiguous-terminology/)digitsRefer to <http://seer.cancer.gov/tools/mphrules/index.html\> for additional instructions..TumorCases 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.A,C,I,MCancer IdentificationRHSEER112006
443Date Conclusive DXdateConclusiveDx8Documents 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 [**Data Descriptor Table**](https://apps.naaccr.org/data-dictionary/data-dictionary/version=24/chapter-view/data-descriptor-table/) 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.Valid dateDate of Conclusive DX, Date of Conclusive Diagnosis, Date of Conclusive Terminology.RHdateYYYYMMDDRefer to <http://seer.cancer.gov/tools/mphrules/index.html\> for additional instructions.TumorThis 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.A,C,I,MCancer IdentificationRHSEER112006
444Mult Tum Rpt as One PrimmultTumRptAsOnePrim2This 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.00, 10-12, 20, 30-32, 40, 80, 88, 99Multiple Tumors Reported as Single Primary, Type of Multiple Tumors Reported As One Primary.RHdigitsRight justified, zero filledRefer to <http://seer.cancer.gov/tools/mphrules/index.html> for additional instructions.TumorPatients 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.A,C,I,MCancer IdentificationRHSEER112006
445Date of Mult TumorsdateOfMultTumors8This 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 [**Data Descriptor Table**](https://apps.naaccr.org/data-dictionary/data-dictionary/version=24/chapter-view/data-descriptor-table/) 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.Valid dateDate of Multiple Tumors.RHdateYYYYMMDDRefer to <http://seer.cancer.gov/tools/mphrules/index.html\> for additional instructions.TumorPatients 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.A,C,I,MCancer IdentificationRHSEER112006
446Multiplicity CountermultiplicityCounter2This 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.00-89, 99, blank.RH*Note*: Codes 00 and 89 were added effective for 2011.digitsRight justified, zero filledRefer to <http://seer.cancer.gov/tools/mphrules/index.html> for additional instructions.TumorPatients 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.A,C,I,MCancer IdentificationRHSEER112006
449Grade Path SystemgradePathSystem1Indicates whether a two, three or four grade system is used.2-4, blank.RHdigitsRefer to the most recent version of *[STORE](http://www.facs.org/cancer/coc/fordsmanual.html)* for additional instructions.RH*TumorThis 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].A,C,I,MCancer IdentificationRHAJCC122010
450Site Coding Sys--CurrentsiteCodingSysCurrent1Code that best describes how the primary site currently is coded. If converted, this field shows the system to which it is converted.1-6, 9..digitsRTumorA,C,I,MCancer Identification.NAACCR
460Site Coding Sys--OriginalsiteCodingSysOriginal1Code that best describes how primary site was originally coded. If converted, this field shows the original coding system used.1-6, 9R*.digits.TumorA,C,I,MCancer Identification.NAACCR
470Morph Coding Sys--CurrentmorphCodingSysCurrent1Code that best describes how morphology is currently coded. If converted, this field shows the system it is converted to. An update or new Morphology Coding System code incorporates all previous coding updates.1-9, A, B, C, D, E.._Note:_   \* These changes were based on the terms of the World Health Organization’s (WHO) fourth edition of the following publications: * WHO Classification of Hematopoietic and Lymphoid Neoplasms (2007) * WHO Classification of Tumors of the Central Nervous System (2008) * WHO Classification of Tumors of the Digestive System (2010) For details including the list of terms included, refer to the link to the NAACCR ICD-O-3 Implementation Guidelines document, effective for 2014 cases: [https://20tqtx36s1la18rvn82wcmpn-wpengine.netdna-ssl.com/wp-content/uploads/2016/11/ICD-O-3-Implementation-Guide-FINAL.pdf](https://20tqtx36s1la18rvn82wcmpn-wpengine.netdna-ssl.com/wp-content/uploads/2016/11/ICD-O-3-Implementation-Guide-FINAL.pdf). \*\*These changes are based on the terms of the World Health Organization’s (WHO) fourth edition of the following publications: * WHO Classification of Tumors of the Breast (2012) * WHO Classification of Tumors of the Female Reproductive Organs (2013) * WHO Classification of Tumors of Soft Tissue and Bone (2013) * WHO Classification of Tumors of the Lung, Pleura, Thymus, and Heart (2015) * WHO Classification of Tumors of the Urinary System and Male Genital Organs (2016) * WHO Classifications of Tumors of the Central Nervous System, Revised 4th Ed (2016) * WHO Classifications of Tumors of the Head and Neck, Revised 4th Edition (2017) * WHO Classifications of Tumors of Endocrine Organs, Revised 4th Edition (2017) For details including the list of terms included, refer to the link to the NAACCR ICD-O-3 Implementation Guidelines document, effective for 2018 cases: \<https://20tqtx36s1la18rvn82wcmpn-wpengine.netdna-ssl.com/wp-content/uploads/2018/01/Updated-Jan-10-2018-ICD-O-3-Guidelines-v2.pdf\>.   \*\*\* These changes are based on the terms of the World Health Organization’s (WHO) fifth edition of the following publications: * WHO Classification of Breast Tumors (2019) * WHO Classification of Digestive System Tumors (2019) * WHO Classification of Female Genital Tumors (2020) * WHO Classification of Skin and Bone Tumors (2020) \*\*\*\*These changes are based on the terms of the World Health Organization’s (WHO) fifth edition of the following publication:  WHO Classification of Tumors of the Urinary and Male Genital Organs 5th Ed (2022).   For details including the list of terms included, refer to the link to the NAACCR ICD-O-3 Implementation Guidelines document, effective for 2022 cases: TBD.mixedRTumorA,C,I,MCancer Identification.NAACCR
480Morph Coding Sys--OriginlmorphCodingSysOriginl1Code that best describes how morphology was originally coded. If later converted, this field shows the original codes used. An update or new Morphology Coding System code incorporates all previous coding updates.1-9, A, B, C, D, ER*._Notes_:   \*These changes were based on the terms of the World Health Organization’s (WHO) fourth edition of the following publications: * WHO Classification of Hematopoietic and Lymphoid Neoplasms (2007) * WHO Classification of Tumors of the Central Nervous System (2008) * WHO Classification of Tumors of the Digestive System (2010) For details including the list of terms included, here is the link to the NAACCR ICD-O-3 Implementation Guidelines document, effective for 2014 cases: \<https://20tqtx36s1la18rvn82wcmpn-wpengine.netdna-ssl.com/wp-content/uploads/2016/11/ICD-O-3-Implementation-Guide-FINAL.pdf\>.   \*\*These changes are based on the terms of the World Health Organization’s (WHO) fourth edition of the following publications: * WHO Classification of Tumors of the Breast (2012) * WHO Classification of Tumors of the Female Reproductive Organs (2013) * WHO Classification of Tumors of Soft Tissue and Bone (2013) * WHO Classification of Tumors of the Lung, Pleura, Thymus, and Heart (2015) * WHO Classification of Tumors of the Urinary System and Male Genital Organs (2016) * WHO Classifications of Tumors of the Central Nervous System, Revised 4th Ed (2016) * WHO Classifications of Tumors of the Head and Neck, Revised 4th Edition (2017) * WHO Classifications of Tumors of Endocrine Organs, Revised 4th Edition (2017) For details including the list of terms included, here is the link to the NAACCR ICD-O-3 Implementation Guidelines document, effective for 2018 cases: \<https://20tqtx36s1la18rvn82wcmpn-wpengine.netdna-ssl.com/wp-content/uploads/2018/01/Updated-Jan-10-2018-ICD-O-3-Guidelines-v2.pdf\>.   \*\*\* These changes are based on the terms of the World Health Organization’s (WHO) fifth edition of the following publications: * WHO Classification of Breast Tumors (2019) * WHO Classification of Digestive System Tumors (2019) * WHO Classification of Female Genital Tumors (2020) * WHO Classification of Skin and Bone Tumors (2020) \*\*\*\*These changes are based on the terms of the World Health Organization’s (WHO) fifth edition of the following publication:  WHO Classification of Tumors of the Urinary and Male Genital Organs 5th Ed (2022).   For details including the list of terms included, refer to the link to the NAACCR ICD-O-3 Implementation Guidelines document, effective for 2022 cases: TBD.mixed.TumorA,C,I,MCancer Identification.NAACCR
490Diagnostic ConfirmationdiagnosticConfirmation1Code for the best method of diagnostic confirmation of the cancer being reported at any time in the patient’s history.1-9RR*Note:* Code 3 (used only for hematopoietic and lymphoid neoplasms M-9590/3-9992/3) was adopted for use effective with 2010 diagnoses.digitsRTumorDiagnostic 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.A,C,I,MCancer IdentificationRSEER/CoC
500Type of Reporting SourcetypeOfReportingSource1This variable codes the source documents used to abstract the majority of information on the tumor being reported. This may not be the source of original case finding (for example, if a case is identified through a pathology laboratory report review and all source documents used to abstract the case are from the physician’s office, code this item 4).1-8..digitsRTumorThe code in this field can be used to explain why information may be incomplete on a tumor. For example, death certificate only cases have unknown values for many data items, so one may want to exclude them from some analyses. The field also is used to monitor the success of non-hospital case reporting and follow-back mechanisms. All population-based registries should have some death certificate-only cases where no hospital admission was involved, but too high a percentage can imply both shortcomings in case-finding and that follow-back to uncover missed hospital reports was not complete. **Coding Instructions** Code in the following priority order: 1, 2, 8, 4, 3, 5, 6, 7. This is a change to reflect the addition of codes 2 and 8 and to prioritize laboratory reports over nursing home reports. The source facilities included in the previous code 1 (hospital inpatient and outpatient) are split between codes 1, 2, and 8. This data item is intended to indicate the completeness of information available to the abstractor. Reports from health plans (e.g., Kaiser, Veterans Administration, military facilities) in which all diagnostic and treatment information is maintained centrally and is available to the abstractor are expected to be at least as complete as reports for hospital inpatients, which is why these sources are grouped with inpatients and given the code with the highest priority. Sources coded with '2' usually have complete information on the cancer diagnosis, staging, and treatment. Sources coded with '8' would include, but would not be limited to, outpatient surgery and nuclear medicine services. A physician's office that calls itself a surgery center should be coded as a physician's office. Surgery centers are equipped and staffed to perform surgical procedures under general anesthesia. If a physician's office calls itself a surgery center, but cannot perform surgical procedures under general anesthesia, code as a physician office.A,C,I,MCancer IdentificationRSEER
501Casefinding SourcecasefindingSource2This 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.10, 20-30, 40, 50, 60, 70, 75, 80, 85, 90, 95, 99..digitsR*TumorThis 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.A,C,I,MCancer Identification.NAACCR112006
522Histologic Type ICD-O-3histologicTypeIcdO34Codes 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 publication^39^, 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](http://www.naaccr.org/LinkClick.aspx?fileticket=U-3o31G2Lik%3d&tabid=126&mid=466%20)8000-9989, Refer to ICD-O-3ICD-O-3 Histology (CCCR)RR**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\].digitsSee ICD-O-3,^14^ Morphology Section and the SEER Hematopoietic databaseRTumorA,C,I,MCancer IdentificationRSEER/CoC92001
523Behavior Code ICD-O-3behaviorCodeIcdO31Code 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.0-3, Refer to ICD-O-3Behavior Code (CoC), ICD-O-3 Behaviour (CCCR)R**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\].RValid codes are 0-3. See ICD-O-3,^14^ page 66, for behavior codes and definitions.digitsRTumorA,C,I,MCancer IdentificationRSEER/CoC92001
530EDP MDE Link DateedpMdeLinkDate8EDP MDE Link Date identifies the date when a breast, cervical, or colorectal cancer case in the registry database matched the same patient and tumor in CDC’s [National Breast and Cervical Cancer Early Detection Program](https://www.cdc.gov/cancer/nbccedp/) (NBCCEDP) data set, the CDC’s [Colorectal Cancer Control Program (CRCCP)](https://www.cdc.gov/cancer/crccp/) data set, or both, indicating that the cancer was identified through one or both early detection programs (EDPs). Use the EDP MDE Link Date variable to record results from the registry’s data linkage with the appropriate NBCCED/CRCCP program(s) in the registry’s state, territory, or jurisdiction.Valid Dates..dateYYYYMMDD\r\nFixed-length, left-justified, space filled.RSTumorThis data item records the date when a cancer was first linked with data from the early detection programs (EDPs) and allows analyses to evaluate trends, identify disparities, and evaluate program success. This linkage process can also identify cancers not reported or reported late to the central cancer registry.A,C,I,MDemographic.NPCR222022
540Reporting FacilityreportingFacility10CoC code for the facility whose data are described in the record.10-digit numberFacility Identification Number (CoC), Institution ID Number (CoC), Reporting Hospital.R_Note:_ When this special code is being used, the length in 9s should correspond to the length indicated by the code in FIN coding system \[35\]. The 9s must be right justified in the field, and the remaining spaces should be filled with leading zeroes to a total length of 10.textIn addition to CoC assigned codesRTumorThe Reporting Facility identification number or FIN is used to identify a reporting facility in the central registry database and is useful for monitoring data submission, ensuring the accuracy of data and identifying areas for special studies.A,C,I,MHospital-SpecificRCoC
545NPI--Reporting FacilitynpiReportingFacility10The 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.10-digit NPI code (9-digit NPI integer plus 1 check digit), blank.RdigitsOnly 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>R*TumorThe NPI equivalent of Reporting Facility [540].A,C,I,MHospital-SpecificR*CMS11.12007
550Accession Number--HospaccessionNumberHosp9Provides 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.9-digit numberAccession Number (CoC).Rdigits.TumorThis 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.A,C,I,MHospital-SpecificRCoC
560Sequence Number--HospitalsequenceNumberHospital2Item indicates the sequence of all malignant and non-malignant neoplasms over the lifetime of the patient. The code may differ from the Sequence Number--Central \[380\] because the definitions of reportable neoplasms often vary between a hospital and a central registry. The two items also handle some types of tumors differently. Each neoplasm is assigned a different number. Sequence Number 00 indicates that the person has only one malignant neoplasm in his lifetime (regardless of hospital registry reference date). Sequence Number 01 indicates the first of two or more malignant neoplasms, while 02 indicates the second of two or more malignant neoplasms, and so on. Because the time period of Sequence Number is a person’s lifetime, reportable neoplasms not included in the hospital registry are also allotted a sequence number. For example, a registry may contain a single record for a patient with a sequence number of 02 because the first reportable neoplasm occurred before the hospital registry’s reference date. Similarly, Sequence Number 60 indicates the patient has only one non-malignant neoplasm, and Sequence Number 61 represents the first of multiple non-malignant neoplasms. Sequence numbers should be reassigned if the facility subsequently learns of an unaccessioned tumor that affects sequencing. Sequence Number-Central \[380\] does not affect Sequence Number-Hospital. The two notational systems are independent.  **Timing Rule** If two or more malignant tumors are diagnosed at the same time, the lowest sequence number will be assigned to the diagnosis with the worst prognosis. Likewise, if two or more non-malignant tumors are diagnosed at the same time, the lowest sequence number is assigned to the diagnosis with the worse prognosis. If no difference in prognosis is evident, the decision is arbitrary.00-59, 60-87, 88, 99Sequence Number (CoC).R**The table that follows shows which sequence number series to use by type of neoplasm** _._ | **Neoplasm** | **SeqNum-Hospital** | | --- | --- | | _**In situ**_**/Malignant** | **(code range)** | | One _in situ_ (behavior code = 2) or malignant (behavior code =3) primary tumor only in the patient’s lifetime | 00 | | First of multiple _in situ_ or malignant primary tumors in the patient’s lifetime | 01 | | Actual sequence of two or more _in situ_ or malignant primary tumors | 02 -- 59 | | Unspecified malignant sequence number or unknown | 99 | | **Non-Malignant** |   | | One benign (behavior code = 0) or borderline (behavior code = 1) primary tumor only in the patient’s lifetime | 60 | | First of two or more benign or borderline primary tumors in the patient’s lifetime | 61 | | Actual sequence of two or more non-malignant primary tumors | 62 -- 87 | | Unspecified non-malignant sequence number or unknown | 88 | \*Juvenile astrocytomas should be reported as 9421/3.  _Note:_ See the section on Sequence Number in CoC (_STORE_) manual.digitsRight justified, zero filled.TumorA,C,I,MHospital-SpecificRCoC
570Abstracted ByabstractedBy3An alphanumeric code assigned by the reporting facility that identifies the individual abstracting the case.Letters and numbers.RtextNo special characters.TumorA,C,I,MHospital-SpecificRCoC
580Date of 1st ContactdateOf1stContact8Date 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 [**Data Descriptor Table**](https://apps.naaccr.org/data-dictionary/data-dictionary/version=24/chapter-view/data-descriptor-table/) 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.Valid datesDate of Adm/First Contact.RdateYYYYMMDD_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.R*TumorTimeliness 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.A,C,I,MHospital-Specific.CoC
590Date of Inpt AdmdateOfInptAdm8Date 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 [**Data Descriptor Table**](https://apps.naaccr.org/data-dictionary/data-dictionary/version=24/chapter-view/data-descriptor-table/) 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.Valid datesDate of Inpatient Adm, Date of Inpatient Admission (CoC)..dateYYYYMMDD_Note:_ This data item is no longer supported by CoC (as of January 1, 2003)..TumorA,C,I,MHospital-Specific.NAACCR
600Date of Inpt DischdateOfInptDisch8Date 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 [**Data Descriptor Table**](https://apps.naaccr.org/data-dictionary/data-dictionary/version=24/chapter-view/data-descriptor-table/) _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.Valid datesDate of Inpatient Disch, Date of Inpatient Discharge (CoC)..dateYYYYMMDD_Note:_ This data item is no longer supported by CoC (as of January 1, 2003)..TumorA,C,I,MHospital-Specific.NAACCR
610Class of CaseclassOfCase2Class 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.00, 10-14, 20-22, 30-38, 40-43, 49, 99.R_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 decisionsdigitsRight justified, zero filled_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 decisionsAnalytic Classes of Case (Required by CoC to be abstracted by accredited cancer programs; refer to [_STORE_](http://www.facs.org/cancer/coc/fordsmanual.html) for additional instructions)RTumorClass 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.A,C,I,MHospital-SpecificRCoCpre V41990
630Primary Payer at DXprimaryPayerAtDx2Primary payer/insurance carrier at the time of initial diagnosis and/or treatment at the reporting facility.01, 02, 10, 20, 21, 31, 35, 60-68, 99Primary Payer at Diagnosis (CoC).RdigitsRight justified, zero filledR*TumorThis item is used in financial analysis and as an indicator for quality and outcome analyses.A,C,I,MHospital-SpecificRCoC
668RX Hosp--Surg App 2010rxHospSurgApp20101This item is used to describe the method of surgical approach used for patients undergoing surgery of the primary site at the reporting facility. If the patient has multiple surgeries to the primary site, this item describes the approach used for the most invasive, definitive surgery0-5, 9.Rdigits.TumorThis item is used to monitor patterns and trends in the adoption and use of minimally-invasive surgical techniques. If central registries wish to study the treatment given at particular facilities, the facility-level treatment fields must be used. Facility-specific fields allow studies of detailed referral patterns and treatment by type of healthcare setting. Knowing the extent of treatment given at a particular facility also helps resolve consolidation issues.A,C,I,MHospital-Specific.CoC122010
670RX Hosp--Surg Prim Site 03-2022rxHospSurgPrimSite2Describes surgical procedures used to treat the primary site of the reportable tumor. This item records that portion of the first course of treatment given at the reporting facility. See Chapter V, Unresolved Issues, for a discussion of differences in treatment coding among groups and over time.  00, 10-80, 90, 98, 99 (site-specific)Cancer-Directed Surgery at This Facility (pre-96 CoC), RX Hosp--CA Dir Surgery (pre-96 NAACCR), RX Hosp--Surg Prim Site, Surgical Procedure of Primary Site.RdigitsRight justified, zero filledIn addition to the site-specific codes (Refer to the most recent version of *STORE* for additional instructions.).TumorThis data item can be used to compare the efficacy of treatment options. If central registries wish to study the treatment given at particular facilities, the facility-level treatment fields must be used. The summary treatment fields, conversely, combine information for all reporting facilities that provide first course of treatment for the tumor. Facility-specific fields allow studies of detailed referral patterns and treatment by type of healthcare setting. Knowing what part of the treatment was given at a particular facility also helps resolve consolidation issues.A,C,I,MHospital-SpecificRHCoC
671RX Hosp--Surg Prim Site 2023rxHospSurgPrimSite20234Records the surgical procedure(s) performed to the primary site at this facility with a diagnosis year of 2023 and forward.A000, A200-A990, B000, B200-B990, BlankSurgery of Primary Site at this Facility.RmixedAlphanumeric Blank.TumorThis data item can be used to compare the efficacy of treatment options.A,C,I,MHospital-SpecificRCoC232023
672RX Hosp--Scope Reg LN SurrxHospScopeRegLnSur1Describes the removal, biopsy, or aspiration of regional lymph node(s) performed at the reporting facility for diagnosis and/or staging or as a part of the first course of therapy.0-7, 9Scope of Regional Lymph Node Surgery at this Facility (CoC).R*Note:* One important use of registry data is the tracking of treatment patterns over time. To compare contemporary treatment to previously published treatment based on former codes, or to data unmodified from pre-1998 definitions, the ability to differentiate surgeries in which four or more regional lymph nodes are removed is desirable. However, it is very important to note that the distinction between codes 4 and 5 is made to permit comparison of current surgical procedures with procedures coded in the past when the removal of fewer than 4 nodes was not reflected in surgery codes. It is not intended to reflect clinical significance when applied to a particular surgical procedure. It is important to avoid inferring, by data presentation or other methods, that one category is preferable to another within the intent of these items.digitsRefer to the most recent version of *STORE* for instructions that should be applied to all surgically treated cases for all types of cancers. The treatment of breast and skin cancers are where the distinction between sentinel lymph node biopsies (SLNBx) and more extensive dissection of regional lymph nodes is most frequently encountered. For all other sites, non-sentinel regional node dissections are typical, and codes 2, 6 and 7 are infrequently used.TumorThis item is important for evaluating quality of care and treatment practices relating to initial diagnosis, staging and/or first course of therapy. If central registries wish to study the treatment given at particular facilities, the facility-level treatment fields must be used. The summary treatment fields, conversely, combine information for all reporting facilities that provide first course of treatment for the tumor. Facility-specific fields allow studies of detailed referral patterns and treatment by type of healthcare setting. Knowing the extent of treatment given at a particular facility also helps resolve consolidation issues. If central registries wish to study the treatment given at particular reporting facilities, the reporting facility-level treatment fields must be used. The summary treatment fields, conversely, combine information across all reporting facilities that provide first course of treatment for the tumor. Reporting facility-specific fields allow studies of detailed referral patterns and treatment by type of reporting facility. Knowing the extent of treatment given at a particular reporting facility also helps resolve coding issues.A,C,I,MHospital-SpecificRCoC5.11997
674RX Hosp--Surg Oth Reg/DisrxHospSurgOthRegDis1Records the surgical removal of distant lymph nodes or other tissue(s)/organ(s) beyond the primary site performed at this facility as a part of first course of treatment.0-5, 9Surgery of Other Regional Site(s), Distant Site(s), or Distant Lymph Node(s) at this Facility (CoC), Surgical Procedure/Other Site at this Facility.RdigitsRefer to the most recent version of *STORE* for additional instructions..TumorThe removal of non-primary tissue documents the extent of surgical treatment and is useful in evaluating the extent of metastatic involvement. If central registries wish to study the treatment given at particular facilities, the facility-level treatment fields must be used. The summary treatment fields, conversely, combine information for all reporting facilities that provide first course of treatment for the tumor. Facility-specific fields allow studies of detailed referral patterns and treatment by type of healthcare setting. Knowing what part of the treatment was given at a particular facility also helps resolve consolidation issues.A,C,I,MHospital-SpecificRCoC5.11997
676RX Hosp--Reg LN RemovedrxHospRegLnRemoved2Describes number of regional lymph nodes removed at the reporting facility as part of the first course of treatment.00-90, 95-99Number of Regional Lymph Nodes Examined at This Facility (CoC), RX Hosp--Reg LN Examined.RH*Note:* As of January 1, 2003, this data item is no longer required or recommended by CoC. However, the item was collected in the past and it is recommended that historic data be retained.digitsRight justified, zero filledRefer to ROADS for additional coding instructions..TumorIf central registries wish to study the treatment given at particular facilities, the facility-level treatment fields must be used. The summary treatment fields, conversely, combine information for all reporting facilities that provide first course of treatment for the tumor. Facility-specific fields allow studies of detailed referral patterns and treatment by type of healthcare setting. Knowing the extent of treatment given at a particular facility also helps resolve consolidation issues.A,C,I,MHospital-Specific.CoC5.11997
682Date Regional Lymph Node DissectiondateRegionalLNDissection8Records the date non-sentinel regional node dissection was performed. This data item is required for CoC-accredited facilities as of cases diagnosed 01/01/2018 and later. Valid dates.RdateYYYYMMDD.TumorIt is a known fact that sentinel lymph node biopsies have been under-reported. Additionally, the timing and results of sentinel lymph node biopsy procedures are used in quality of care measures. This data item can be used to more accurately assess the date of regional node dissection separate from the date of sentinel lymph node biopsy if performed.A,C,I,MStage/Prognostic FactorsRCNAACCR182018
690RX Hosp--RadiationrxHospRadiation1Defines the type of radiation therapy the patient received at the reporting facility as a part of the first course of treatment.0-5, 9Radiation at this Facility (CoC)..*Note*: CoC no longer requires this item effective January 1, 2002. SEER continues to support it as a historically collected and currently transmitted data item.digits.TumorIf central registries wish to study the treatment given at particular facilities, the facility-level treatment fields must be used. The summary treatment fields, conversely, combine information for all facilities that provide first course of treatment for the tumor. Facility-specific fields allow studies of detailed referral patterns and treatment by type of healthcare setting. Knowing what part of the treatment was given at a particular facility also helps resolve consolidation issues.A,C,I,MHospital-SpecificRHSEER
700RX Hosp--ChemorxHospChemo2Records the type of chemotherapy administered at the reporting facility as a part of first course therapy or the reason chemotherapy was not given.00-03, 82, 85-88, 99Chemotherapy at this Facility (CoC).RdigitsRight justified, zero filled*Note*: Prior to 2013, targeted therapies that invoke an immune response, such as Herceptin, had been coded as chemotherapy. Effective with cases diagnosed January 1, 2013, and forward these therapies are classified as biological response modifiers. Coding instructions for these changes have been added to the remarks field for the applicable drugs in the SEER\*RX Interactive Drug Database ( <http://seer.cancer.gov/tools/seerrx/>).Refer to the most recent *STORE* and SEER RX for additional complete coding directions..TumorSystemic therapy may involve the administration of one or a combination of agents. This data item allows for the evaluation of chemotherapeutic agents given as part of the first course of therapy. Furthermore, it is useful to know the reason chemotherapy was not administered when evaluating quality of care. If central registries wish to study the treatment given at particular facilities, the facility-level treatment fields must be used. The summary treatment fields, conversely, combine information for all facilities that provide first course of treatment for the tumor. Facility-specific fields allow studies of detailed referral patterns and treatment by type of healthcare setting. Knowing what part of the treatment was given at a particular facility also helps resolve consolidation issues.A,C,I,MHospital-SpecificRCoC
710RX Hosp--HormonerxHospHormone2Records whether systemic hormonal agents were administered as first-course treatment at this facility or the reason they were not given. Hormone therapy consists of a group of drugs that may affect the long-term control of a cancer’s growth. It is not usually used as a curative measure.00, 01, 82, 85-88, 99Hormone Therapy at this Facility (CoC).R*Note*: Codes 02-03 entered under the *ROADS* rules for tumors diagnosed prior to January 1, 2003, should have been converted to the appropriate code in the new field RX SUMM--Transplnt/Endocr [3250] implemented with *FORDS*. Endocrine surgery and endocrine radiation therapy are no longer coded as Hormone Therapy for tumors diagnosed on or after January 1, 2003.digitsRight justified, zero filledRefer to the most recent version of *STORE* for additional instructions..TumorSystemic therapy may involve the administration of one or a combination of agents. This data item allows for the evaluation of hormonal agents given as part of the first course of therapy. Furthermore, it is useful to know the reason hormone therapy was not administered when evaluating quality of care for certain tumors. If central registries wish to study the treatment given at particular facilities, the facility-level treatment fields must be used. The summary treatment fields, conversely, combine information for all reporting facilities that provide first course of treatment for the tumor. Facility-specific fields allow studies of detailed referral patterns and treatment by type of healthcare setting. Knowing what part of the treatment was given at a particular facility also helps resolve consolidation issues.A,C,I,MHospital-SpecificRCoC
720RX Hosp--BRMrxHospBrm2Records whether immunotherapeutic agents (biologic response modifiers) were administered as first-course treatment at this facility or the reason they were not given. Immunotherapy consists of biological or chemical agents that alter the immune system or change the host’s response to tumor cells.00, 01, 82, 85-88, 99Immunotherapy at this Facility (CoC).R*Note:* For tumors diagnosed on or after January 1, 2003, information on bone marrow and stem cell transplants is no longer coded under this item. *ROADS* codes 02-06 should not be used in this field. For diagnosed on or after January 1, 2003, this information should be coded in the new field RX SUMM--Transplnt/Endocr [3250].digitsRight justified, zero filled*Note*: Prior to 2013, targeted therapies that invoke an immune response, such as Herceptin, had been coded as chemotherapy. Effective with cases diagnosed January 1, 2013, and forward these therapies are classified as biological response modifiers. Coding instructions for these changes have been added to the remarks field for the applicable drugs in the SEER\*RX Interactive Drug Database ( <http://seer.cancer.gov/tools/seerrx/>).Refer to the most recent *STORE* and SEER Rx for complete coding instructions..TumorSystemic therapy may involve the administration of one or a combination of agents. This data item allows for the evaluation of immunotherapeutic agents given as part of the first course of therapy. Furthermore, it is useful to know the reason immunotherapy was not administered when evaluating quality of care. If central registries wish to study the treatment given at particular facilities, the facility-level treatment fields must be used. The summary treatment fields, conversely, combine information for all facilities that provide first course of treatment for the tumor. Facility-specific fields allow studies of detailed referral patterns and treatment by type of healthcare setting. Knowing what part of the treatment was given at a particular facility also helps resolve consolidation issues.A,C,I,MHospital-SpecificRCoC
730RX Hosp--OtherrxHospOther1Identifies treatment given at this facility that cannot be defined as surgery, radiation, or systemic therapy according to the defined data items in this manual. Treatment for reportable hematopoietic diseases can be supportive care, observation, or any treatment that does not meet the usual definition in which treatment modifies, controls, removes, or destroys proliferating cancer tissue. Supportive care such as phlebotomy, transfusions, or aspirin may be recorded for hematopoietic diseases ONLY.0-3, 6-9Other Treatment at this Facility (CoC).Rdigits.TumorInformation on other therapy is used to describe treatment practices and evaluate quality of care. If central registries wish to study the treatment given at particular facilities, the facility-level treatment fields must be used. The summary treatment fields, conversely, combine information for all reporting facilities that provide first course of treatment for the tumor. Facility-specific fields allow studies of detailed referral patterns and treatment by type of healthcare setting. Knowing what part of the treatment was given at a particular facility also helps resolve consolidation issues.A,C,I,MHospital-SpecificRCoC
740RX Hosp--DX/Stg ProcrxHospDxStgProc2Identifies the surgical procedure(s) performed in an effort to diagnose and/or stage disease at this facility.00-07, 09Non Cancer-Directed Surgery at this Facility (CoC), RX Hosp--DX/Stg/Pall Proc, Surgical Diagnostic & Staging Procedure at this Facility (1996-2002).R*Note*: This item has been used for tumors diagnosed in 1996 and later. For cases diagnosed before 1996, this item may have been converted from the *DAM*, and cases with surgery would have been converted to 09 in this field. For cases diagnosed between 1996 and 2002, this field may have described palliative care according to coding rules in *ROADS*. For tumors diagnosed on or after January 1, 2003, palliative care is coded in a new field RX Hosp--Palliative Proc [3280].digitsRight justified, zero filledRefer to the most recent version of *STORE* for additional instructions..TumorThis data item is used to track the use of surgical procedure resources that are not considered treatment. If central registries wish to study the procedures performed at particular facilities, the facility-level fields must be used. The summary fields, conversely, combine information for all facilities that provide first course of treatment for the tumor. Facility-specific fields allow studies of detailed referral patterns and diagnostic/staging procedures by type of healthcare setting. Knowing what part of the diagnostic or staging process was performed at a particular facility also helps resolve consolidation issues.A,C,I,MHospital-Specific.CoC
746RX Hosp--Surg Site 98-02rxHospSurgSite98022Describes surgical procedures used to treat the primary site of the reportable tumor. This item records that portion of the first course of treatment given at the reporting facility. This field is to be used for *ROADS* codes after the *ROADS* to *FORDS* conversion. It is also to be used to code Surgery Primary Site at the reporting facility for all tumors diagnosed before January 1, 2003. See Chapter V, Unresolved Issues, for a discussion of differences in treatment coding among groups and over time.00, 10-90, 99 (site-specific), blankCancer-Directed Surgery at this Facility (pre-96 CoC), RX Hosp--CA Dir Surgery (pre-96 NAACCR), Surgical Procedure of Primary Site.RH*Note*: See the CoC *ROADS* Manual 1998 Supplement and the *SEER Program Code Manual* for site-specific codes.digitsRight justified, zero filledIn addition to the site-specific codes.TumorThis data item can be used to compare the efficacy of treatment options. If central registries wish to study the treatment given at particular facilities, the facility-level treatment fields must be used. The summary treatment fields, conversely, combine information for all reporting facilities that provide first course of treatment for the tumor. Facility-specific fields allow studies of detailed referral patterns and treatment by type of healthcare setting. Knowing what part of the treatment was given at a particular facility also helps resolve consolidation issues.A,C,I,MHospital-SpecificRHCoC
747RX Hosp--Scope Reg 98-02rxHospScopeReg98021Describes the removal, biopsy, or aspiration of regional lymph node(s) at the time of surgery of the primary site or during a separate surgical event at the reporting facility. This field is to be used for *ROADS* codes after the *ROADS* to *FORDS* conversion. It is also to be used to code Scope of Regional Lymph Node Surgery at the reporting facility for all tumors diagnosed before January 1, 2003.0-9 (site-specific), blankScope of Regional Lymph Node Surgery at this Facility (CoC).RHdigitsSee the CoC *ROADS Manual 1998 Supplement* and the *SEER Program Code Manual* for site-specific codes.TumorIn evaluating quality of care and treatment practices it is important to identify the removal, biopsy, or aspiration of regional lymph node(s) at the time of surgery of the primary site or during a separate surgical event. If central registries wish to study the treatment given at particular reporting facilities, the facility-level treatment fields must be used. The summary treatment fields, conversely, combine information across all reporting facilities that provide first course of treatment for the tumor. Reporting facility-specific fields allow studies of detailed referral patterns and treatment by type of hospital. Knowing the extent of treatment given at a particular reporting facility also helps resolve coding issues.A,C,I,MHospital-SpecificRHCoC
748RX Hosp--Surg Oth 98-02rxHospSurgOth98021Records the surgical removal of distant lymph nodes or other tissue(s)/organ(s) beyond the primary site at this facility. This field is to be used for *ROADS* codes after the *ROADS* to *FORDS* conversion. It is also to be used to code Surgery Other Regional/Distant Sites at the reporting facility for all tumors diagnosed before January 1, 2003.0-9 (site-specific), blankSurgery of Other Regional Site(s), Distant Site(s), or Distant Lymph Node(s) at this Facility (CoC), Surgical Procedure/Other Site at this Facility.RHdigitsSee the CoC *ROADS Manual* 1998 Supplement and the SEER Program Code Manual for site-specific codes..TumorThe removal of non-primary tissue documents the extent of surgical treatment and is useful in evaluating the extent of metastatic involvement. If central registries wish to study the treatment given at particular facilities, the facility-level treatment fields must be used. The summary treatment fields, conversely, combine information for all reporting facilities that provide first course of treatment for the tumor. Facility-specific fields allow studies of detailed referral patterns and treatment by type of healthcare setting. Knowing what part of the treatment was given at a particular facility also helps resolve consolidation issues.A,C,I,MHospital-SpecificRHCoC
751RX Hosp--Recon BreastrxHospReconBreast4Used to collect information on immediate breast reconstruction.A000, A100, A200, A300, A400, A500, A600, A610, A620, A630, A640, A900, A970, A980, A990.RmixedRight justified, no leading or trailing zeros or spaces.TumorBreast reconstruction was previously collected within the breast surgery codes. CoC will collect this data item to support the Synoptic Operative Reports and allow for more descriptive reconstruction codes.A,C,I,MRevisedHospital-SpecificRCoC242024
752Tumor Size ClinicaltumorSizeClinical3This data item records the size of a solid primary tumor **before any treatment** (surgical resection or initiation of any treatment including neoadjuvant).000-990, 998, 999R*.digitsRefer to the most recent version of** [**SEER Program Coding and Staging Manual**](http://seer.cancer.gov/tools/codingmanuals/) **for additional instructions..TumorClinical tumor size (pre-treatment size) is essential for treatment decision making and prognosis determination for many types of cancer.A,C,I,MUpdated SEERStage/Prognostic FactorsRHSEER162016
754Tumor Size PathologictumorSizePathologic3This data item records the size of a solid primary tumor that has been resected.000-990, 998, 999R*.digitsRefer to the most recent version of** [**SEER Program Coding and Staging Manual**](http://seer.cancer.gov/tools/codingmanuals/) **for additional instructions..TumorPathologic tumor size is an important prognostic indicator and valuable for clinical practice and research on surgically treated patients for most cancers.A,C,I,MUpdated SEERStage/Prognostic FactorsRHSEER162016
756Tumor Size SummarytumorSizeSummary3This data item records the most accurate measurement of a solid primary tumor, usually measured on the surgical resection specimen.000-990, 998, 999.RdigitsSee the most recent version of the** [**STORE**](https://www.facs.org/quality-programs/cancer/ncdb/registrymanuals/cocmanuals) **manual** **for additional instructions.RTumorTumor size is one indication of the extent of disease. As such, it is used by both clinicians and researchers. Tumor size that is independent of stage is also useful for quality assurance efforts.A,C,I,MUpdated SEERStage/Prognostic FactorsRNPCR/CoC162016
759SEER Summary Stage 2000seerSummaryStage20001Code for summary stage at the initial diagnosis or treatment of the reportable tumor. For hospital registries, CoC requires its use in the absence of a defined AJCC classification. For site-specific definitions of categories, see SEER *Summary Staging Manual 2000*. Summary stage should include all information available through completion of surgery(ies) in the first course of treatment or within 4 months of diagnosis in the absence of disease progression, whichever is longer.0-5, 7, 8, 9.RH*Note:* Code 8 has been added in Version 10.1 to be used when there is not an applicable code to reflect stage (e.g., benign brain, borderline ovarian). *Note:* See also the item Derived SS2000 [3020] for the value of SEER Summary Stage 2000 as generated by the collaborative Staging algorithm. **Clarification of NAACCR and NPCR Required Status** Summary stage is required. The correct data item to use (and corresponding code manual) is determined by the year in which the cancer was diagnosed. Tumors diagnosed on or after January 1, 2004, should be assigned a summary stage based upon the Collaborative Stage data item algorithms and retained in Derived SS2000 [3020]. Tumors diagnosed on or after January 1, 2001, should be assigned a summary stage according to the SEER *Summary Staging Manual 2000*, and the code should be reported in SEER Summary Stage 2000 [759]. Tumors diagnosed before January 1, 2001, should be assigned a summary stage according to *SEER Summary Stage Guide 1977*, and the code should be reported in SEER Summary Stage 1977 [760].digitsRHTumorStage information is important when evaluating the effects of cancer control programs. It is crucial in understanding whether changes over time in incidence rates or outcomes are due to earlier detection of the cancers. In addition, cancer treatment cannot be studied without knowing the stage at diagnosis.A,C,I,MStage/Prognostic FactorsRHSEER92001
760SEER Summary Stage 1977seerSummaryStage19771Code for summary stage at the initial diagnosis or treatment of the reportable tumor. This has traditionally been used by central registries to monitor time trends. For hospital registries, CoC requires its use in the absence of a defined AJCC classification. For site-specific definitions of categories, see the SEER Summary Staging Guide. SEER Summary Stage 1977 is limited to information available within 2 months of the date of diagnosis. NAACCR approved extension of this time period to 4 months for prostate tumors diagnosed beginning January 1, 1995.0-5, 7, 8, 9General Summary Stage (SEER/CoC).RH_Note:_ Code 8 has been added in Version 10.1 to be used when there is not an applicable code to reflect stage (e.g., benign brain, borderline ovarian).  _Note:_ See also the item Derived SS1977 \[3010\] for the value of SEER Summary Stage 1977 as generated by the Collaborative Staging algorithm.  **Clarification of NAACCR and NPCR Required Status** Summary stage is required. The correct data item to use (and corresponding code manual) is determined by the year in which the cancer was diagnosed. Tumors diagnosed on or after January 1, 2004, should be assigned a summary stage based upon the Collaborative Stage data item algorithms and retained in Derived SS2000 \[3020\]. Tumors diagnosed on or after January 1, 2001, should be assigned a summary stage according to the SEER _Summary Staging Manual 2000_, and the code should be reported in SEER Summary Stage 2000 \[759\]. Tumors diagnosed before January 1, 2001, should be assigned a summary stage according to _SEER Summary Stage Guide 1977_, and the code should be reported in SEER Summary Stage 1977 \[760\].digitsRHTumorStage information is important when evaluating the effects of cancer control programs. It is crucial for understanding whether changes over time in incidence rates or outcomes are due to earlier detection of the cancers. In addition, cancer treatment cannot be studied without knowing the stage at diagnosis. To study historical trends in stage, the coding system must be relatively unchanged (stable) over time. AJCC’s TNM system is updated periodically to maintain clinical relevance with changes in diagnosis and treatment. The surveillance registries often rely on the Summary Stage, which they consider to be more “stable.” Summary Stage has been in widespread use, either as the primary staging scheme or a secondary scheme, in most central and hospital registries since 1977.A,C,I,MStage/Prognostic Factors.SEER
762Derived Summary Stage 2018derivedSummaryStage20181Derived Summary Stage 2018 is derived using the EOD data collection system (EOD Primary Tumor [772], EOD Regional Nodes [774] and EOD Mets [776]) algorithm. Other data items may be included in the derivation process. Effective for cases diagnosed 1/1/2018+.0-4, 7-9Derived SS2018..digits*Note*: This data item was included in Standards Volume II, Version 16; however, it was not implemented until 2018..TumorThe SEER program has collected staging information on cases since its inception in 1973. Summary Stage groups cases into broad categories of in situ, local, regional, and distant. Summary Stage can be used to evaluate disease spread at diagnosis, treatment patterns and outcomes over time.   Derived Summary Stage 2018 [762] is only available at the central registry level.A,C,I,MStage/Prognostic FactorsDSEER162018
764Summary Stage 2018summaryStage20181This item stores the directly assigned Summary Stage 2018. Effective for cases diagnosed 1/1/2018+.0-4, 7-9Directly Assigned SS2018..\*Applicable for the following SS2018 chapters: Brain, CNS Other, Intracranial Gland. _Note_: For SS2018, code 5 for “Regional, NOS” can no longer be coded. Code 5 (Regional, NOS) is still applicable.digits_Note_: This data item was included in Standards Volume II, Version 16; however, it was not implemented until 2018.RTumorThe SEER program has collected staging information on cases since its inception in 1973. Summary Stage groups cases into broad categories of in situ, local, regional, and distant. Summary Stage can be used to evaluate disease spread at diagnosis, treatment patterns and outcomes over time.A,C,I,MStage/Prognostic FactorsR*SEER162018
772EOD Primary TumoreodPrimaryTumor3EOD Primary Tumor is part of the EOD 2018 data collection system and is used to classify contiguous growth (extension) of the primary tumor within the organ of origin or its direct extension into neighboring organs. See also EOD Regional Nodes [774] and EOD Mets [776]. Effective for cases diagnosed 1/1/2018+. Valid schema-specific codes; also 000, 800, 999SEER Primary Tumor..*Note*: (See the most current version of EOD (<https://staging.seer.cancer.gov/>) for rules and site-specific codes and coding structures.)text*Note*: This data item was included in Standards Volume II, Version 16; however, it was not implemented until 2018.In addition to schema-specific codes where needed.TumorEOD Primary Tumor is used to calculate Derived EOD 2018 T [785] (when applicable) and Derived Summary Stage 2018 [762]. Derivation will occur at the level of the central registry.A,C,I,MStage/Prognostic FactorsRSEER162018
774EOD Regional NodeseodRegionalNodes3EOD Regional Nodes is part of the EOD 2018 data collection system and is used to classify the regional lymph nodes involved with cancer at the time of diagnosis. See also EOD Primary Tumor [772] and EOD Mets [776]. Effective for cases diagnosed 1/1/2018+.Valid schema-specific codes; also 000, 800, 888, 999SEER Regional Nodes..*Note*: See the most current version of EOD (<https://staging.seer.cancer.gov/>) for rules and site-specific codes and coding structures.text*Note*: This data item was included in Standards Volume II, Version 16; however, it was not implemented until 2018.In addition to valid schema-specific codes.TumorEOD Regional Nodes is used to calculate Derived EOD 2018 N [815] (when applicable) and Derived Summary Stage 2018 [762]. Derivation will occur at the level of the central registry.A,C,I,MStage/Prognostic FactorsRSEER162018
776EOD MetseodMets2EOD Mets is part of the EOD 2018 data collection system and is used to classify the distant site(s) of metastatic involvement at time of diagnosis. See also EOD Primary Tumor [772] and EOD Regional Nodes [774]. Effective for cases diagnosed 1/1/2018+.Valid schema-specific codes; also 00, 88, 99SEER Mets..*Note*: See the most current version of EOD (<https://staging.seer.cancer.gov/>) for rules and site-specific codes and coding structures.text*Note*: This data item was included in Standards Volume II, Version 16; however, it was not implemented until 2018.In addition to valid schema-specific codes.Tumor EOD Mets is used to calculate Derived EOD 2018 M [795] (when applicable) and Derived Summary Stage 2018 [762]. Derivation will occur at the level of the central registry.A,C,I,MStage/Prognostic FactorsRSEER162018
780EOD--Tumor SizeeodTumorSize3Part 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.See respective source referencesSize of Primary Tumor (SEER), Size of Tumor (CoC).RH*Note:* See Chapter V, Unresolved Issues, for a discussion of coding differences between CoC and SEER. digitsRight justified, zero filledSee *S*[*EER Extent of Disease, 1988: Codes and Coding Instructions*, Third Edition](seer.cancer.gov/manuals/EOD10Dig.pub.pdf), for site-specific codes and coding rules for all EOD fields. The CoC codes for Tumor Size are in the *[STORE](http://www.facs.org/cancer/coc/fordsmanual.html)* manual..TumorSite-specific EOD codes provide extensive detail describing disease extent. The EOD codes can be grouped into different stage categories for analysis (e.g., historical summary stage categories consistent with those used in published SEER data since 1973, or more recently, AJCC stage groupings). The codes are updated as needed, but updates are usually backward compatible with old categories. See *Comparative Staging Guide for Cancer*.^6^A,C,I,MStage/Prognostic FactorsRHSEER/CoC
785Derived EOD 2018 TderivedEod2018T15This item stores the derived EOD 2018 T value derived from coded fields using the EOD algorithm. Effective for cases diagnosed 1/1/2018+...textSee the most current version of EOD (<https://staging.seer.cancer.gov/>) for rules and site-specific codes and coding structures.TumorDerived EOD 2018 T can be used to evaluate disease spread at diagnosis, treatment patterns and outcomes over time.   Derived EOD 2018 T is only available at the central registry level.A,C,I,MStage/Prognostic FactorsDSEER182018
790EOD--ExtensioneodExtension2Part 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.Reference SEER Extent of Disease manualExtension (SEER EOD) (96 CoC), Extension (pre-96 SEER/CoC)..digitsRight justified, zero filledSee [*SEER Extent of Disease, 1988: Codes and Coding Instructions*, Third Edition](http://seer.cancer.gov/manuals/EOD10Dig.3rd.pdf)^8^ for site-specific codes and coding rules for all EOD fields..TumorSite-specific EOD codes provide extensive detail describing disease extent. The EOD codes can be grouped into different stage categories for analysis (e.g., historical summary stage categories consistent with those used in published SEER data since 1973, or more recently, AJCC stage groupings). The codes are updated as needed, but updates are usually backward compatible with old categories. See *Comparative Staging Guide for Cancer*^6^.A,C,I,MStage/Prognostic FactorsRHSEER
795Derived EOD 2018 MderivedEod2018M15This item stores the derived EOD 2018 M staging element from coded fields using the EOD algorithm. Effective for cases diagnosed 1/1/2018+...textSee the most current version of EOD (<https://staging.seer.cancer.gov/>) for rules and site-specific codes and coding structures.TumorDerived EOD 2018 M can be used to evaluate disease spread at diagnosis, treatment patterns and outcomes over time.   Derived EOD 2018 M is only available at the central registry level.A,C,I,MStage/Prognostic FactorsDSEER182018
800EOD--Extension Prost PatheodExtensionProstPath2Part 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.Reference SEER Extent of Disease manual..digitsRight justified, zero filledSee [*SEER Extent of Disease, 1988: Codes and Coding Instructions*, Third Edition](http://seer.cancer.gov/manuals/EOD10Dig.3rd.pdf)^8^ for site-specific codes and coding rules for all EOD fields..TumorSite-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.A,C,I,MStage/Prognostic FactorsRHSEER41995
810EOD--Lymph Node InvolveodLymphNodeInvolv1Part 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.Reference SEER Extent of Disease manualLymph Nodes (SEER EOD) (96 CoC), Lymph Nodes (pre 96-SEER/CoC)..textSee [*SEER Extent of Disease, 1988: Codes and Coding Instructions*, Third Edition](http://seer.cancer.gov/manuals/EOD10Dig.3rd.pdf)^8^ for site-specific codes and coding rules for all EOD fields..TumorSite-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](http://seer.cancer.gov/tools/codingmanuals/historical.html)*.A,C,I,MStage/Prognostic FactorsRHSEER
815Derived EOD 2018 NderivedEod2018N15This item stores the derived EOD 2018 N staging element from coded fields using the EOD algorithm. Effective for cases diagnosed 1/1/2018+...textSee the most current version of EOD (<https://staging.seer.cancer.gov/>) for rules and site-specific codes and coding structures.TumorDerived EOD 2018 N can be used to evaluate disease spread at diagnosis, treatment patterns and outcomes over time.   Derived EOD 2018 N is only available at the central registry level.A,C,I,MStage/Prognostic FactorsDSEER182018
818Derived EOD 2018 Stage GroupderivedEod2018StageGroup15Derived EOD 2018 Stage Group is derived using the EOD data collection system (EOD Primary Tumor [772], EOD Regional Nodes [774] and EOD Mets [776]) algorithm. Other data items may be included in the derivation process. Effective for cases diagnosed 1/1/2018+...textSee the most current version of EOD (<https://staging.seer.cancer.gov/>) for rules and site-specific codes and coding structures.TumorDerived EOD 2018 Stage Group can be used to evaluate disease spread at diagnosis, treatment patterns and outcomes over time.   Derived EOD 2018 Stage group is only available at the central registry level.A,C,I,MStage/Prognostic FactorsDSEER182018
820Regional Nodes PositiveregionalNodesPositive2Records the exact number of regional nodes examined by the pathologist and found to contain metastases. Beginning with tumors diagnosed on or after January 1, 2004, this item is a component of the Collaborative Stage system. For tumors diagnosed from 1988 through 2003, this item was part of the 10-digit EOD [779], detailed site-specific codes for anatomic EOD.00-90, 95, 97-99Number of Positive Regional Lymph Nodes (SEER), Pathologic Review of Regional Lymph Nodes (SEER), Regional Lymph Nodes PositiveR*R*Note:* See Chapter V, Unresolved Issues, for a discussion of coding differences between CoC and SEER.digitsRight justified, zero filledRTumorThis data item is necessary for pathologic staging, and it serves as a quality measure for pathology reports and the extent of the surgical evaluation and treatment of the patient.A,C,I,MStage/Prognostic FactorsRSEER/CoC
830Regional Nodes ExaminedregionalNodesExamined2Records the total number of regional lymph nodes that were removed and examined by the pathologist. Beginning with tumors diagnosed on or after January 1, 2004, this item is a component of the Collaborative Stage system.00-90, 95-99Number of Regional Lymph Nodes Examined (SEER), Pathologic Review of Regional Lymph Nodes (SEER), Regional Lymph Nodes ExaminedR*RdigitsRight justified, zero filledRTumorThis data item serves as a quality measure of the pathologic and surgical evaluation and treatment of the patient.A,C,I,MStage/Prognostic FactorsRSEER/CoC
832Date of Sentinel Lymph Node BiopsydateSentinelLymphNodeBiopsy8Records the date of the sentinel lymph node(s) biopsy procedure. This data item is required for CoC-accredited facilities as of cases diagnosed 01/01/2018 and later. **This data item is required for breast and melanoma cases only.** Valid dates.RSdateYYYYMMDD.TumorIt is a known fact that sentinel lymph node biopsies have been under-reported. Additionally, the timing and results of sentinel lymph node biopsy procedures are used in quality of care measures. This data item can be used to more accurately assess the date of the sentinel lymph node biopsy procedure separate from the date of a subsequent regional node dissection procedure, if performed.A,C,I,MStage/Prognostic FactorsR*CoC182018
834Sentinel Lymph Nodes ExaminedsentinelLymphNodesExamined2Records the total number of lymph nodes sampled during the sentinel node biopsy and examined by the pathologist. This data item is required for CoC-accredited facilities as of cases diagnosed 01/01/2018 and later. **This data item is required for breast and melanoma cases only.** 00-90, 95, 98, 99.RSdigitsRight justified, zero filled.TumorIt is a known fact that sentinel lymph node biopsies have been under-reported. Additionally, the timing and results of sentinel lymph node biopsy procedures are used in quality of care measures. This data item can be used to more accurately assess the number of lymph nodes biopsied during the sentinel node biopsy procedure separate from the number of lymph nodes dissected during additional subsequent regional node procedures.A,C,I,MStage/Prognostic FactorsRSCoC182018
835Sentinel Lymph Nodes PositivesentinelLymphNodesPositive2Records the exact number of sentinel lymph nodes biopsied by the pathologist and found to contain metastases. This data item is required for CoC-accredited facilities as of cases diagnosed 01/01/2018 and later. **This data item is required for breast and melanoma cases only.** 00-90, 95, 97-99.RSdigitsRight justified, zero filled.TumorIt is a known fact that sentinel lymph node biopsies have been under-reported. Additionally, the timing and results of sentinel lymph node biopsy procedures are used in quality of care measures. This data item can be used to more accurately assess the number of positive sentinel lymph nodes biopsied separate from the number of positive lymph nodes identified during additional subsequent regional node dissection procedures, if performed.A,C,I,MStage/Prognostic FactorsRSCoC182018
840EOD--Old 13 DigiteodOld13Digit13Detailed site-specific codes for EOD used by SEER for selected sites of cancer for tumors diagnosed 1973-1982, except death-certificate-only cases.13-Digit (Expanded) Site-Specific Extent of Disease (SEER), SEER EEOD (SEER)..textNumeric and special charactersSee *Extent of Disease: Codes and Coding Instructions (SEER 1977)*^10^ for codes..TumorA,C,I,MStage/Prognostic FactorsRHSEER
850EOD--Old 2 DigiteodOld2Digit2Site-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].2-Digit Nonspecific and 2-Digit Site-Specific Extent of Disease (1973-1982 SEER)..textNumeric plus special characters \x22&\x22 and \x22dash\x22 (\x22-\x22)See *Extent of Disease: Codes and Coding Instructions (SEER 1977)*^10^ for codes..TumorA,C,I,MStage/Prognostic FactorsRHSEER
860EOD--Old 4 DigiteodOld4Digit4Codes for site-specific EOD used by SEER for tumors diagnosed from January 1, 1983, to December 31, 1987, for all cancer sites.4-Digit Extent of Disease (1983-1987 SEER)..textSee *SEER Extent of Disease: New 4-Digit Schemes: Codes and Coding Instructions*^9^ for codes..TumorA,C,I,MStage/Prognostic FactorsRHSEER
870Coding System for EODcodingSystemForEod1Indicates the type of SEER EOD code applied to the tumor. Should be used whenever EOD coding is applied.0-4, BlankCoding System for Extent of Disease (SEER)..digits.TumorUsed in data editing and analysis.A,C,I,MStage/Prognostic FactorsRHSEER51995
880TNM Path TtnmPathT4Detailed site-specific codes for the pathologic tumor (T) as defined by AJCC and recorded by the physician. Pathologic and clinical stage data are given three separate areas in the NAACCR Data Exchange Record Layout.See AJCC Cancer Staging Manual and FORDS manual; also 88, blankPathologic T (CoC).RH*Note:* See the *AJCC Cancer Staging Manual*, current edition for site-specific categories for the TNM elements and stage groups. See the *STORE* manual for specifications for codes and data entry rules.textUpper case, alphanumeric, left justified, blank filledIn addition to those published in the *AJCC Cancer Staging Manual*.TumorCoC requires that AJCC TNM staging be used in its approved cancer programs. AJCC developed its staging system for evaluating trends in the treatment and control of cancer. This staging is used by physicians to estimate prognosis, to plan treatment, to evaluate new types of therapy, to analyze outcome, to design follow-up strategies, and to assess early detection results.A,C,I,MStage/Prognostic FactorsRHAJCC
890TNM Path NtnmPathN4Detailed site-specific codes for the pathologic nodes (N) as defined by AJCC and recorded by physician. Pathologic and clinical stage data are given three separate areas in the NAACCR Data Exchange Record Layout.See AJCC Cancer Staging Manual and FORDS manual; also 88, blankPathologic N (CoC).RH*Note:* See the *AJCC Cancer Staging Manual*, current edition for site-specific categories for the TNM elements and stage groups. See the *STORE* manual for specifications for codes and data entry rules.textUpper case, alphanumeric, left justified, blank filledIn addition to those published in the *AJCC Cancer Staging Manual*.TumorCoC requires that AJCC TNM staging be used in its approved cancer programs. AJCC developed its staging system for evaluating trends in the treatment and control of cancer. This staging is used by physicians to estimate prognosis, to plan treatment, to evaluate new types of therapy, to analyze outcome, to design follow-up strategies, and to assess early detection results.A,C,I,MStage/Prognostic FactorsRHAJCC
900TNM Path MtnmPathM4Detailed site-specific codes for the pathologic metastases (M) as defined by AJCC and recorded by the physician. Pathologic and clinical stage data are given three separate areas in the NAACCR Data Exchange Record Layout.See AJCC Cancer Staging Manual and FORDS Manual; also 88, blankPathologic M (CoC).RH*Note:* See the *AJCC Cancer Staging Manual*, current edition for site-specific categories for the TNM elements and stage groups. See the *STORE* manual for specifications for codes and data entry rules.textUpper case, alphanumeric, left justified, blank filledIn addition to those published in the *AJCC Cancer Staging Manual*.TumorCoC requires that AJCC TNM staging be used in its approved cancer programs. AJCC developed its staging system for evaluating trends in the treatment and control of cancer. This staging is used by physicians to estimate prognosis, to plan treatment, to evaluate new types of therapy, to analyze outcome, to design follow-up strategies, and to assess early detection results.A,C,I,MStage/Prognostic FactorsRHAJCC
910TNM Path Stage GrouptnmPathStageGroup4Detailed site-specific codes for the pathologic stage group as defined by AJCC and recorded by the physician. Pathologic and clinical stage data are given three separate areas in the NAACCR Data Exchange Record Layout.See AJCC Cancer Staging Manual and FORDS Manual; also 88, 99Pathologic Stage Group (CoC).RH*Note:* See the *AJCC Cancer Staging Manual*, current edition for site-specific categories for the TNM elements and stage groups. See the *STORE* manual for specifications for codes and data entry rules.textUpper case, alphanumeric. Convert AJCC Roman numerals to Arabic numerals. Left justified, blank filledIn addition to those published in the *AJCC Cancer Staging Manual*.TumorCoC requires that AJCC TNM staging be used in its approved cancer programs. AJCC developed its staging system for evaluating trends in the treatment and control of cancer. This staging is used by physicians to estimate prognosis, to plan treatment, to evaluate new types of therapy, to analyze outcome, to design follow-up strategies, and to assess early detection results.A,C,I,MStage/Prognostic FactorsRH*AJCC
920TNM Path DescriptortnmPathDescriptor1Identified the AJCC pathologic stage (prefix/suffix) descriptor as recorded by the physician. AJCC stage descriptors identify special cases that need separate data analysis. The descriptors are adjuncts to and do not change the stage group. Pathologic and clinical stage data are given three separate areas in the NAACCR Data Exchange Record Layout. CoC defines a descriptor and “Staged By” item for each of these three areas.0-6, 9, blankPathologic Stage (Prefix/Suffix) Descriptor (CoC).RHdigits.TumorCoC requires that AJCC TNM staging be used in its approved cancer programs. AJCC developed its staging system for evaluating trends in the treatment and control of cancer. This staging is used by physicians to estimate prognosis, to plan treatment, to evaluate new types of therapy, to analyze outcome, to design follow-up strategies, and to assess early detection results.A,C,I,MStage/Prognostic FactorsRHCoC
930TNM Path Staged BytnmPathStagedBy2Identifies the person who recorded the pathologic AJCC staging elements and the stage group in the patient’s medical record.00, 10-15, 20, 30, 40, 50, 60, 88, 99 Staged By (Pathologic Stage) (CoC).RHdigitsRefer to the most recent version of *STORE* for additional coding instructions.TumorData captured in this field can be used to evaluate the source of pathologic staging and form the basis for quality management and improvement studies.A,C,I,MStage/Prognostic FactorsRHCoC
940TNM Clin TtnmClinT4Detailed site-specific codes for the clinical tumor (T) as defined by AJCC and recorded by the physician. Pathologic and clinical stage data are given three separate areas in the NAACCR Data Exchange Record Layout.See AJCC Cancer Staging Manual and FORDS Manual; also 88, blankClinical T (CoC).RH*Note:* See the *AJCC Cancer Staging Manual*, current edition for site-specific categories for the TNM elements and stage groups. See the *STORE* manual for specifications for codes and data entry rules.textUpper case, alphanumeric, left justified, blank filledIn addition to those published in the *AJCC Cancer Staging Manual*.TumorCoC requires that AJCC TNM staging be used in its approved cancer programs. AJCC developed its staging system for evaluating trends in the treatment and control of cancer. This staging is used by physicians to estimate prognosis, to plan treatment, to evaluate new types of therapy, to analyze outcome, to design follow-up strategies, and to assess early detection results.A,C,I,MStage/Prognostic FactorsRHAJCC
950TNM Clin NtnmClinN4Detailed site-specific codes for the clinical nodes (N) as defined by AJCC and recorded by the physician. Pathologic and clinical stage data are given three separate areas in the NAACCR Data Exchange Record Layout.See AJCC Cancer Staging Manual and FORDS Manual; also 88, blankClinical N (CoC).RH*Note:* See the *AJCC Cancer Staging Manual*, current edition for site-specific categories for the TNM elements and stage groups. See the *STORE* manual for specifications for codes and data entry rules.textUpper case, alphanumeric, left justified, blank filledIn addition to those published in the AJCC Cancer Staging Manual.TumorCoC requires that AJCC TNM staging be used in its approved cancer programs. AJCC developed its staging system for evaluating trends in the treatment and control of cancer. This staging is used by physicians to estimate prognosis, to plan treatment, to evaluate new types of therapy, to analyze outcome, to design follow-up strategies, and to assess early detection results.A,C,I,MStage/Prognostic FactorsRHAJCC
960TNM Clin MtnmClinM4Detailed site-specific codes for the clinical metastases (M) as defined by AJCC and recorded by the physician. Pathologic and clinical stage data are given three separate areas in the NAACCR Data Exchange Record Layout.See AJCC Cancer Staging Manual and FORDS Manual; also 88, blankClinical M (CoC).RH*Note:* See the *AJCC Cancer Staging Manual*, current edition for site-specific categories for the TNM elements and stage groups. See the *STORE* manual for specifications for codes and data entry rules.textUpper case, alphanumeric, left justified, blank filledIn addition to those published in the AJCC Cancer Staging Manual.TumorCoC requires that AJCC TNM staging be used in its approved cancer programs. AJCC developed its staging system for evaluating trends in the treatment and control of cancer. This staging is used by physicians to estimate prognosis, to plan treatment, to evaluate new types of therapy, to analyze outcome, to design follow-up strategies, and to assess early detection results.A,C,I,MStage/Prognostic FactorsRHAJCC
970TNM Clin Stage GrouptnmClinStageGroup4Detailed site-specific codes for the clinical stage group as defined by AJCC and recorded by the physician. Pathologic and clinical stage data are given three separate areas in the NAACCR Data Exchange Record Layout.See AJCC Cancer Staging Manual and FORDS Manual; also 88, 99Clinical Stage Group (CoC).RH*Note:* See the *AJCC Cancer Staging Manual*, current edition for site-specific categories for the TNM elements and stage groups. See the *STORE* manual for specifications for codes and data entry rules.textUpper case, alphanumeric. Convert AJCC Roman numerals to Arabic numerals. Left justified, blank filledIn addition to those published in the *AJCC Cancer Staging Manual*.TumorCoC requires that AJCC TNM staging be used in its approved cancer programs. AJCC developed its staging system for evaluating trends in the treatment and control of cancer. This staging is used by physicians to estimate prognosis, to plan treatment, to evaluate new types of therapy, to analyze outcome, to design follow-up strategies, and to assess early detection results.A,C,I,MStage/Prognostic FactorsRH*AJCC
980TNM Clin DescriptortnmClinDescriptor1Identifies the AJCC clinical stage (prefix/suffix) descriptor as recorded by the physician. AJCC stage descriptors identify special cases that need separate data analysis. The descriptors are adjuncts to and do not change the stage group. Pathologic and clinical stage data are given three separate areas in the NAACCR Data Exchange Record Layout. CoC defines a descriptor and “Staged By” item for each of these three areas.0-3, 5, 9, blankClinical Stage (Prefix/Suffix) Descriptor (CoC).RHdigits.TumorCoC requires that AJCC TNM staging be used in its approved cancer programs. AJCC developed its staging system for evaluating trends in the treatment and control of cancer. This staging is used by physicians to estimate prognosis, to plan treatment, to evaluate new types of therapy, to analyze outcome, to design follow-up strategies, and to assess early detection results.A,C,I,MStage/Prognostic FactorsRHCoC
990TNM Clin Staged BytnmClinStagedBy2Identifies the person who recorded the clinical AJCC staging elements and the stage group in the patient’s medical record.00, 10-15, 20, 30, 40, 50, 60, 88, 99 Staged By (Clinical Stage) (CoC).RHdigitsRefer to the most recent version of *STORE* for additional coding instructions.TumorData captured in this field can be used to evaluate the source of clinical staging and form the basis for quality management and improvement studies. This item can be used to monitor application of the CoC Staging Standard.A,C,I,MStage/Prognostic FactorsRHCoC
995AJCC IDajccId4The values for this data item are based on the chapters of the AJCC manual and will be derived primarily from the site/histology fields and other data items as required. IDs are assigned to cases for which AJCC staging is applicable. When staging is not applicable, code ‘XX’ is used.R*DEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.text.TumorThis data item will be used to create an efficient process for running TNM Edits.A,C,I,MNPCR RevisedRevisedStage/Prognostic FactorsDNAACCR182018
1001AJCC TNM Clin TajccTnmClinT15Detailed site-specific codes for the clinical tumor (T) as defined by the current AJCC edition.See the AJCC Cancer Staging Manual for valid codes; also 88, BlankR*R*Note*: See the AJCC Cancer Staging Manual, 8th edition for site-specific categories for the TNM elements and stage groups. See the CURRENT *STORE* manual for specifications for codes and data entry rules.textLeft justifiedIn addition to those published in the AJCC Cancer Staging Manual.TumorCoC requires that AJCC TNM staging be used in its approved cancer programs. AJCC developed its staging system for evaluating trends in the treatment and control of cancer. This staging is used by physicians to estimate prognosis, to plan treatment, to evaluate new types of therapy, to analyze outcome, to design follow-up strategies, and to assess early detection results.A,C,I,MStage/Prognostic FactorsRCAJCC182018
1002AJCC TNM Clin NajccTnmClinN15Detailed site-specific codes for the clinical nodes (N) as defined by the current AJCC edition.See the AJCC Cancer Staging Manual for valid codes; also 88, BlankR*R*Note*: See the AJCC Cancer Staging Manual, 8th edition for site-specific categories for the TNM elements and stage groups. See the CURRENT *STORE* manual for specifications for codes and data entry rules.textLeft justifiedIn addition to those published in the AJCC Cancer Staging Manual.TumorCoC requires that AJCC TNM staging be used in its approved cancer programs. AJCC developed its staging system for evaluating trends in the treatment and control of cancer. This staging is used by physicians to estimate prognosis, to plan treatment, to evaluate new types of therapy, to analyze outcome, to design follow-up strategies, and to assess early detection results.A,C,I,MStage/Prognostic FactorsRCAJCC182018
1003AJCC TNM Clin MajccTnmClinM15Detailed site-specific codes for the clinical metastases (M) as defined by the current AJCC edition.See the AJCC Cancer Staging Manual for valid codes; also 88, BlankR*R*Note*: See the AJCC Cancer Staging Manual, 8th edition for site-specific categories for the TNM elements and stage groups. See the CURRENT *STORE* manual for specifications for codes and data entry rules.textLeft justifiedIn addition to those published in the AJCC Cancer Staging Manual.TumorCoC requires that AJCC TNM staging be used in its approved cancer programs. AJCC developed its staging system for evaluating trends in the treatment and control of cancer. This staging is used by physicians to estimate prognosis, to plan treatment, to evaluate new types of therapy, to analyze outcome, to design follow-up strategies, and to assess early detection results.A,C,I,MStage/Prognostic FactorsRCAJCC182018
1004AJCC TNM Clin Stage GroupajccTnmClinStageGroup15Detailed site-specific codes for the clinical stage group as defined by the current AJCC edition.See the AJCC Cancer Staging Manual for valid codes; also 88, 99R*R*Note*: See the AJCC Cancer Staging Manual, 8th edition for site-specific categories for the TNM elements and stage groups. See the CURRENT *STORE* manual for specifications for codes and data entry rules.textLeft justifiedIn addition to those published in the AJCC Cancer Staging Manual.TumorCoC requires that AJCC TNM staging be used in its approved cancer programs. AJCC developed its staging system for evaluating trends in the treatment and control of cancer. This staging is used by physicians to estimate prognosis, to plan treatment, to evaluate new types of therapy, to analyze outcome, to design follow-up strategies, and to assess early detection results.A,C,I,MStage/Prognostic FactorsRCAJCC182018
1011AJCC TNM Path TajccTnmPathT15Detailed site-specific codes for the pathologic tumor (T) as defined by the current AJCC edition.See the AJCC Cancer Staging Manual for valid codes; also 88, BlankR*R*Note*: See the AJCC Cancer Staging Manual, 8th edition for site-specific categories for the TNM elements and stage groups. See the CURRENT *STORE* manual for specifications for codes and data entry rules.textLeft justifiedIn addition to those published in the AJCC Cancer Staging Manual.TumorCoC requires that AJCC TNM staging be used in its approved cancer programs. AJCC developed its staging system for evaluating trends in the treatment and control of cancer. This staging is used by physicians to estimate prognosis, to plan treatment, to evaluate new types of therapy, to analyze outcome, to design follow-up strategies, and to assess early detection results.A,C,I,MStage/Prognostic FactorsRCAJCC182018
1012AJCC TNM Path NajccTnmPathN15Detailed site-specific codes for the pathologic nodes (N) as defined by the current AJCC edition.See the AJCC Cancer Staging Manual for valid codes; also 88, BlankR*R*Note*: See the AJCC Cancer Staging Manual, 8th edition for site-specific categories for the TNM elements and stage groups. See the CURRENT *STORE* manual for specifications for codes and data entry rules.textLeft justifiedIn addition to those published in the AJCC Cancer Staging Manual.TumorCoC requires that AJCC TNM staging be used in its approved cancer programs. AJCC developed its staging system for evaluating trends in the treatment and control of cancer. This staging is used by physicians to estimate prognosis, to plan treatment, to evaluate new types of therapy, to analyze outcome, to design follow-up strategies, and to assess early detection results.A,C,I,MStage/Prognostic FactorsRCAJCC182018
1013AJCC TNM Path MajccTnmPathM15Detailed site-specific codes for the clinical path (M) as defined by the current AJCC edition.See the AJCC Cancer Staging Manual for valid codes; also 88, BlankR*R*Note*: See the AJCC Cancer Staging Manual, 8th edition for site-specific categories for the TNM elements and stage groups. See the CURRENT *STORE* manual for specifications for codes and data entry rules.textLeft justifiedIn addition to those published in the AJCC Cancer Staging Manual.TumorCoC requires that AJCC TNM staging be used in its approved cancer programs. AJCC developed its staging system for evaluating trends in the treatment and control of cancer. This staging is used by physicians to estimate prognosis, to plan treatment, to evaluate new types of therapy, to analyze outcome, to design follow-up strategies, and to assess early detection results.A,C,I,MStage/Prognostic FactorsRCAJCC182018
1014AJCC TNM Path Stage GroupajccTnmPathStageGroup15Detailed site-specific codes for the pathologic stage group as defined by the current AJCC edition.See the AJCC Cancer Staging Manual for valid codes; also 88, 99R*R*Note*: See the AJCC Cancer Staging Manual, 8th edition for site-specific categories for the TNM elements and stage groups. See the CURRENT *STORE* manual for specifications for codes and data entry rules.textLeft justifiedIn addition to those published in the AJCC Cancer Staging Manual.TumorCoC requires that AJCC TNM staging be used in its approved cancer programs. AJCC developed its staging system for evaluating trends in the treatment and control of cancer. This staging is used by physicians to estimate prognosis, to plan treatment, to evaluate new types of therapy, to analyze outcome, to design follow-up strategies, and to assess early detection results.A,C,I,MStage/Prognostic FactorsRCAJCC182018
1021AJCC TNM Post Therapy Path (yp) TajccTnmPostTherapyT15Detailed site-specific codes for the postneoadjuvant therapy Path tumor (T) as defined by AJCC. Clinical, pathological, and post therapy yc and yp stage data are given four separate areas in the NAACCR Data Exchange Record Layout.See the AJCC Cancer Staging Manual for valid codes; also 88, BlankR*R*Note*: See the AJCC Cancer Staging Manual, current edition for site-specific categories for the TNM categories and stage groups. See the CURRENT *STORE* manual for specifications for codes and data entry rules.textLeft justifiedIn addition to those published in the AJCC Cancer Staging Manual.TumorCoC requires that AJCC TNM staging be used in its approved cancer programs. AJCC developed its staging system for evaluating trends in the treatment and control of cancer. This staging is used by physicians to estimate prognosis, to plan treatment, to evaluate new types of therapy, to analyze outcome, to design follow-up strategies, and to assess early detection results. Evaluates the primary tumor (T) and reflects the tumor size and/or extension of the tumor known following the completion of neoadjuvant therapy (satisfying the definition for that disease site) and planned postneoadjuvant therapy surgical resection.A,C,I,MStage/Prognostic FactorsRCAJCC182018
1022AJCC TNM Post Therapy Path (yp) NajccTnmPostTherapyN15Detailed site-specific codes for the postneoadjuvant therapy Path nodes (N) as defined by AJCC. Clinical, pathological, and post therapy yc and yp stage data are given four separate areas in the NAACCR Data Exchange Record Layout..See the AJCC Cancer Staging Manual for valid codes; also 88, BlankR*R*Note*: See the AJCC Cancer Staging Manual, current edition for site-specific categories for the TNM categories and stage groups. See the CURRENT *STORE* manual for specifications for codes and data entry rules.textLeft justifiedIn addition to those published in the AJCC Cancer Staging Manual.TumorCoC requires that AJCC TNM staging be used in its approved cancer programs. AJCC developed its staging system for evaluating trends in the treatment and control of cancer. This staging is used by physicians to estimate prognosis, to plan treatment, to evaluate new types of therapy, to analyze outcome, to design follow-up strategies, and to assess early detection results. Identifies the absence or presence of regional lymph node (N) metastasis and describes the extent of lymph node metastasis of the tumor known known following the completion of neoadjuvant therapy (satisfying the definition for that disease site) and planned postneoadjuvant therapy surgical resection.A,C,I,MStage/Prognostic FactorsRCAJCC182018
1023AJCC TNM Post Therapy Path (yp) MajccTnmPostTherapyM15Detailed site-specific codes for the postneoadjuvant therapy category metastases (M) as defined by AJCC. Clinical, pathological, and post therapy yc and yp stage data are given four separate areas in the NAACCR Data Exchange Record Layout.See the AJCC Cancer Staging Manual for valid codes; also 88, BlankR*R*Note*: See the AJCC Cancer Staging Manual, current edition for site-specific categories for the TNM categories and stage groups. See the CURRENT *STORE* manual for specifications for codes and data entry rules.textLeft justifiedIn addition to those published in the AJCC Cancer Staging Manual.TumorCoC requires that AJCC TNM staging be used in its approved cancer programs. AJCC developed its staging system for evaluating trends in the treatment and control of cancer. This staging is used by physicians to estimate prognosis, to plan treatment, to evaluate new types of therapy, to analyze outcome, to design follow-up strategies, and to assess early detection results. M category for postneoadjuvant therapy staging remains the same as that assigned in the clinical stage before initiation of neoadjuvant therapy, cM or pM.A,C,I,MStage/Prognostic FactorsRCAJCC182018
1024AJCC TNM Post Therapy Path (yp) Stage GroupajccTnmPostTherapyStageGroup15Detailed site-specific codes for the postneoadjuvant therapy Path stage group as defined by AJCC. Clinical, pathological, and post therapy yc and yp stage data are given four separate areas in the NAACCR Data Exchange Record Layout.See the AJCC Cancer Staging Manual for valid codes; also 88, 99R*R*Note*: See the AJCC Cancer Staging Manual, current edition for site-specific categories for the TNM categories and stage groups. See the CURRENT *STORE* manual for specifications for codes and data entry rules.textLeft justifiedIn addition to those published in the AJCC Cancer Staging Manual.TumorCoC requires that AJCC TNM staging be used in its approved cancer programs. AJCC developed its staging system for evaluating trends in the treatment and control of cancer. This staging is used by physicians to estimate prognosis, to plan treatment, to evaluate new types of therapy, to analyze outcome, to design follow-up strategies, and to assess early detection results. Identifies the remaining anatomic extent of disease based on the T and N following the completion of neoadjuvant therapy (satisfying the definition for that disease site) and planned postneoadjuvant therapy surgical resection, and the M status defined during the diagnostic workup.A,C,I,MStage/Prognostic FactorsRCAJCC182018
1031AJCC TNM Clin T SuffixajccTnmClinTSuffix4Detailed site-specific codes for the clinical T category suffix as defined by AJCC. Clinical, pathological, and postneoadjuvant therapy stage data are given three separate areas in the NAACCR Data Exchange Record Layout.See the AJCC Cancer Staging Manual for valid codes; also (m), (s), blankR*R*Note*: Refer to the current AJCC Cancer Staging Manual for staging rules.textLeft justifiedAs published in the AJCC Cancer Staging Manual.TumorCoC requires that AJCC TNM staging be used in its approved cancer programs. AJCC developed its staging system for evaluating trends in the treatment and control of cancer. This staging is used by physicians to estimate prognosis, to plan treatment, to evaluate new types of therapy, to analyze outcome, to design follow-up strategies, and to assess early detection resultsA,C,I,MStage/Prognostic FactorsRCAJCC182018
1032AJCC TNM Path T SuffixajccTnmPathTSuffix4Detailed site-specific codes for the pathological T category suffix as defined by AJCC. Clinical, pathological, and postneoadjuvant therapy stage data are given three separate areas in the NAACCR Data Exchange Record Layout.See the AJCC Cancer Staging Manual for valid codes; also (m), (s), BlankR*R*Note*: Refer to the current AJCC Cancer Staging Manual for staging rules.textLeft justifiedAs published in the AJCC Cancer Staging Manual.TumorCoC requires that AJCC TNM staging be used in its approved cancer programs. AJCC developed its staging system for evaluating trends in the treatment and control of cancer. This staging is used by physicians to estimate prognosis, to plan treatment, to evaluate new types of therapy, to analyze outcome, to design follow-up strategies, and to assess early detection results.A,C,I,MStage/Prognostic FactorsRCAJCC
1033AJCC TNM Post Therapy Path (yp) T SuffixajccTnmPostTherapyTSuffix4Detailed site-specific codes for the postneoadjuvant therapy Path T category suffix as defined by AJCC. Clinical, pathological, and post therapy yc and yp stage data are given four separate areas in the NAACCR Data Exchange Record Layout.See the AJCC Cancer Staging Manual for valid codes; also (m),(s), BlankR*R*Note*: Refer to the current AJCC Cancer Staging Manual for staging rules.textLeft justifiedAs published in the AJCC Cancer Staging Manual.TumorCoC requires that AJCC TNM staging be used in its approved cancer programs. AJCC developed its staging system for evaluating trends in the treatment and control of cancer. This staging is used by physicians to estimate prognosis, to plan treatment, to evaluate new types of therapy, to analyze outcome, to design follow-up strategies, and to assess early detection results.A,C,I,MStage/Prognostic FactorsRCAJCC182018
1034AJCC TNM Clin N SuffixajccTnmClinNSuffix4Detailed site-specific codes for the clinical N category suffix as defined by AJCC. Clinical, pathological, and postneoadjuvant therapy stage data are given three separate areas in the NAACCR Data Exchange Record Layout.See the AJCC Cancer Staging Manual for valid codes; also (sn), (f), BlankR*R*Note*: Refer to the current AJCC Cancer Staging Manual for staging rules.textLeft justified.TumorCoC requires that AJCC TNM staging be used in its approved cancer programs. AJCC developed its staging system for evaluating trends in the treatment and control of cancer. This staging is used by physicians to estimate prognosis, to plan treatment, to evaluate new types of therapy, to analyze outcome, to design follow-up strategies, and to assess early detection results.A,C,I,MStage/Prognostic FactorsRCAJCC
1035AJCC TNM Path N SuffixajccTnmPathNSuffix4Detailed site-specific codes for the pathological N category suffix as defined by AJCC. Clinical, pathological, and postneoadjuvant therapy stage data are given three separate areas in the NAACCR Data Exchange Record Layout.(sn), (f), BlankR*RtextLeft justified.TumorCoC requires that AJCC TNM staging be used in its approved cancer programs. AJCC developed its staging system for evaluating trends in the treatment and control of cancer. This staging is used by physicians to estimate prognosis, to plan treatment, to evaluate new types of therapy, to analyze outcome, to design follow-up strategies, and to assess early detection results.A,C,I,MStage/Prognostic FactorsRCAJCC182018
1036AJCC TNM Post Therapy Path (yp) N SuffixajccTnmPostTherapyNSuffix4Detailed site-specific codes for the postneoadjuvant therapy Path N category suffix as defined by AJCC. Clinical, pathological, and post therapy yc and yp stage data are given four separate areas in the NAACCR Data Exchange Record Layout.(sn), (f), BlankR*RtextLeft justified.TumorCoC requires that AJCC TNM staging be used in its approved cancer programs. AJCC developed its staging system for evaluating trends in the treatment and control of cancer. This staging is used by physicians to estimate prognosis, to plan treatment, to evaluate new types of therapy, to analyze outcome, to design follow-up strategies, and to assess early detection results.A,C,I,MStage/Prognostic FactorsRCAJCC182018
1060TNM Edition NumbertnmEditionNumber2A code that indicates the edition of the AJCC manual used to stage the case. This applies to the manually coded AJCC fields. It does not apply to the Derived AJCC T, N, M and AJCC Stage Group fields [2940, 2960, 2980, and 3000].00-09, 88, 99RRtextRight justified, zero filled.TumorTNM codes have changed over time and conversion is not always simple. Therefore, a case-specific indicator is needed to allow grouping of cases for comparison.A,C,I,MStage/Prognostic FactorsRHCoC
1062AJCC TNM Post Therapy Clin (yc) TajccTnmPostTherapyClinT15Detailed site-specific codes for the post therapy clinical (yc) tumor (T) as defined by AJCC. Clinical, pathological, and post therapy yc and yp stage data are given four separate areas in the NAACCR Data Exchange Record Layout.    Those published in the AJCC Cancer Staging Manual, 88, blank.R*Note*: See the *AJCC Cancer Staging Manual*, current edition for site-specific categories for the TNM categories and stage groups. See the CURRENT *STORE* manual for specifications for codes and data entry rules.textIn addition to those published in the AJCC Cancer Staging Manual.TumorCoC requires that AJCC TNM staging be used in its approved cancer programs. AJCC developed its staging system for evaluating trends in the treatment and control of cancer. This staging is used by physicians to estimate prognosis, to plan treatment, to evaluate new types of therapy, to analyze outcome, to design follow-up strategies, and to assess early detection results. Evaluates the primary tumor (T) and reflects the tumor size and/or extension of the tumor known following the completion of neoadjuvant therapy (satisfying the definition for that disease site) before planned surgical resection or primary treatment consisting of systemic and/or radiation therapy.A,C,I,MStage/Prognostic FactorsRCAJCC212021
1063AJCC TNM Post Therapy Clin (yc) T SuffixajccTnmPostTherapyClinTSuffix4Detailed site-specific codes for the post therapy clinical (yc) tumor T category suffix as defined by AJCC. Clinical, pathological, and post therapy yc and yp stage data are given four separate areas in the NAACCR Data Exchange Record Layout.(m), (s), blank.R*Note*: Refer to the current *AJCC Cancer Staging Manual* for staging rules.textAs published in the AJCC Cancer Staging Manual.TumorCoC requires that AJCC TNM staging be used in its approved cancer programs. AJCC developed its staging system for evaluating trends in the treatment and control of cancer. This staging is used by physicians to estimate prognosis, to plan treatment, to evaluate new types of therapy, to analyze outcome, to design follow-up strategies, and to assess early detection results.A,C,I,MStage/Prognostic FactorsRCAJCC212021
1064AJCC TNM Post Therapy Clin (yc) NajccTnmPostTherapyClinN15Detailed site-specific codes for the post therapy clinical (yc) nodes (N) as defined by AJCC. Clinical, pathological, and post therapy yc and yp stage data are given four separate areas in the NAACCR Data Exchange Record Layout.In addition to those published in the AJCC Cancer Staging Manual: 88, Blank.R*Note*: See the *AJCC Cancer Staging Manual*, current edition for site-specific categories for the TNM categories and stage groups. See the CURRENT *STORE* manual for specifications for codes and data entry rules.textIn addition to those published in the AJCC Cancer Staging Manual.TumorCoC requires that AJCC TNM staging be used in its approved cancer programs. AJCC developed its staging system for evaluating trends in the treatment and control of cancer. This staging is used by physicians to estimate prognosis, to plan treatment, to evaluate new types of therapy, to analyze outcome, to design follow-up strategies, and to assess early detection results. Identifies the absence or presence of regional lymph node (N) metastasis and describes the extent of lymph node metastasis of the tumor known following the completion of neoadjuvant therapy (satisfying the definition for that disease site) before planned surgical resection or primary treatment consisting of systemic and/or radiation therapy.A,C,I,MStage/Prognostic FactorsRCAJCC212021
1065AJCC TNM Post Therapy Clin (yc) N SuffixajccTnmPostTherapyClinNSuffix4Detailed site-specific codes for the post therapy clinical (yc) N category suffix as defined by AJCC. Clinical, pathological, and post therapy yc and yp stage data are given four separate areas in the NAACCR Data Exchange Record Layout.(sn), (f), Blank.Rtext.TumorCoC requires that AJCC TNM staging be used in its approved cancer programs. AJCC developed its staging system for evaluating trends in the treatment and control of cancer. This staging is used by physicians to estimate prognosis, to plan treatment, to evaluate new types of therapy, to analyze outcome, to design follow-up strategies, and to assess early detection results.A,C,I,MStage/Prognostic FactorsRCAJCC212021
1066AJCC TNM Post Therapy Clin (yc) MajccTnmPostTherapyClinM15Detailed site-specific codes for the post therapy clinical (yc) metastases (M) as defined by AJCC. Clinical, pathological, and post therapy yc and yp stage data are given four separate areas in the NAACCR Data Exchange Record Layout.Those published in the AJCC Cancer Staging Manual, 88, Blank.R*Note*: See the *AJCC Cancer Staging Manual*, current edition for site-specific categories for the TNM categories and stage groups. See the CURRENT *STORE* manual for specifications for codes and data entry rules.textIn addition to those published in the AJCC Cancer Staging Manual.TumorCoC requires that AJCC TNM staging be used in its approved cancer programs. AJCC developed its staging system for evaluating trends in the treatment and control of cancer. This staging is used by physicians to estimate prognosis, to plan treatment, to evaluate new types of therapy, to analyze outcome, to design follow-up strategies, and to assess early detection results. M category for post neoadjuvant therapy staging remains the same as that assigned in the clinical stage before initiation of neoadjuvant therapy or primary systemic/radiation therapy, cM or pM.A,C,I,MStage/Prognostic FactorsRCAJCC212021
1067AJCC TNM Post Therapy Clin (yc) Stage GroupajccTnmPostTherapyClinStageGrp15Detailed site-specific codes for the post therapy clinical (yc) stage group as defined by AJCC. Clinical, pathological, and post therapy yc and yp stage data are given four separate areas in the NAACCR Data Exchange Record Layout.Those published in the AJCC Cancer Staging Manual, 88, Blank..*Note*: See the *AJCC Cancer Staging Manual*, current edition for site-specific categories for the TNM categories and stage groups. See the CURRENT *STORE* manual for specifications for codes and data entry rules.textIn addition to those published in the AJCC Cancer Staging Manual.TumorCoC requires that AJCC TNM staging be used in its approved cancer programs. AJCC developed its staging system for evaluating trends in the treatment and control of cancer. This staging is used by physicians to estimate prognosis, to plan treatment, to evaluate new types of therapy, to analyze outcome, to design follow-up strategies, and to assess early detection results. Identifies the remaining anatomic extent of disease based on the T and N following the completion of neoadjuvant therapy (satisfying the definition for that disease site) before planned surgical resection or primary treatment consisting of systemic and/or radiation therapy, and the M status defined during the diagnostic workup.A,C,I,MStage/Prognostic Factors.AJCC212021
1068Grade Post Therapy Clin (yc)gradePostTherapyClin1This data item records the grade of a solid primary tumor that has been microscopically sampled following neoadjuvant therapy or primary systemic/radiation therapy. If AJCC staging is being assigned, the tumor must have met the neoadjuvant therapy or primary systemic/radiation therapy requirements in the AJCC manual or according to national treatment guidelines. Record the highest grade documented from the microscopically sampled specimen of the primary site following neoadjuvant therapy or primary systemic/radiation therapy. For cases diagnosed January 1, 2021, and later, this data item, along with Grade Clinical, Grade Pathological, and Grade Post Therapy Path (yp), replaces NAACCR Data Item Grade \[440\] as well as SSF’s for cancer sites with alternative grading systems (e.g., breast \[Bloom-Richardson\], prostate \[Gleason\]).Refer to the most recent version of the SSDI, Blank.REach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.textRefer to the most recent version of the SSDI Manual for additional site-specific instructionsR*TumorGrade is a measure of the aggressiveness of the tumor. Grade and cell type are important prognostic indicators for many cancers. For some sites, grade is required to assign the post therapy stage group. For those cases that are eligible for AJCC staging, the recommended grading system is specified in the AJCC Chapter. The AJCC Chapter-specific grading systems (codes 1-5, L, H, M, S) take priority over the generic grade definitions (codes A-E, 9). For those cases that are not eligible for AJCC staging, if the recommended grading system is not documented, the generic grade definitions would apply.A,C,I,MStage/Prognostic FactorsRSNAACCR212021
1112Mets at DX-BonemetsAtDxBone1This 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.0, 1, 8, 9RRdigits.TumorInformation 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.A,C,I,MStage/Prognostic FactorsRSEER162016
1113Mets at DX-BrainmetsAtDxBrain1This 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.0, 1, 8, 9RRdigits.TumorInformation 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.A,C,I,MStage/Prognostic FactorsRSEER162016
1114Mets at Dx-Distant LNmetsAtDxDistantLn1This 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.0, 1, 8, 9RRdigits.TumorInformation 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.A,C,I,MStage/Prognostic FactorsRSEER162016
1115Mets at DX-LivermetsAtDxLiver1This 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.0, 1, 8, 9RRdigits.TumorInformation 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.A,C,I,MStage/Prognostic FactorsRSEER162016
1116Mets at DX-LungmetsAtDxLung1This 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.0, 1, 8, 9RRdigits.TumorInformation 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.A,C,I,MStage/Prognostic FactorsRSEER162016
1117Mets at DX-OthermetsAtDxOther1The six Mets at Dx-Metastatic Sites fields provide information on metastases for data analysis. This field identifies any type of distant involvement not captured in the Mets at Dx-Bone [1112], Mets at Dx-Brain [1113], Mets at Dx-Liver [1115], Mets at Dx-Lung [1116], and Mets at Dx-Distant LN [1114] fields. It includes involvement of other specific sites and more generalized metastases such as carcinomatosis. Some examples include but are not limited to the adrenal gland, bone marrow, pleura, malignant pleural effusion, peritoneum, and skin.0, 1, 2, 8, 9RRdigits.TumorInformation 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.A,C,I,MStage/Prognostic FactorsRSEER162016
1132Pediatric IDpediatricId5The derived values in this data item link Site-Specific Data Items with the appropriate site/histology grouping and account for the combination of primary site and histologies that are being collected for Pediatric Cancers starting in 2024. The values for this data item are derived based on primary site and histology and are initially based on the Toronto Childhood Cancer Stage Guidelines. The derived values link Site-Specific Data Items with the appropriate site/histology grouping.  * _For example_, the Pediatric ID for a Neuroblastoma is 4a. This value links the Staging and Site-Specific Data Items associated with Neuroblastoma: 1185: Intl Neuroblastoma Risk Grp Stag Sys (INRGSS), 1186: n-MYC Amplification, and 1187: Intl Neuroblastoma Path Prog Class (INPC)..text.TumorThe purpose of the Pediatric ID is to link the appropriate Site-Specific Data Items and Pediatric Stage Data Items (Pediatric Primary Tumor, Pediatric Regional Nodes, Pediatric Mets) with the patient’s primary site/histology. Each Site-Specific Data Item (SSDI) and definitions for the Pediatric Stage Data Items apply only to selected primary sites, histologies, and years of diagnosis.A,C,I,MStage/Prognostic FactorsRS*NAACCR252025
1133Pediatric ID Version CurrentpediatricIdVersionCurrent5This item indicates the version of Pediatric component of the SEER Staging API used to assign the 2024 and later pediatric staging fields of Pediatric ID and Pediatric input fields. This data item is recorded the first time the Pediatric ID is determined and should be updated each time the related input fields are modified.0.3-99.99..Pediatric ID Version Current is a code with up to 2 digits, a decimal and then up to 2 more digits. (e.g., 1.5, 10.12). The first two digits represent the major version number; the second two digits represent minor version changes. The minimum allowable value would be “0.3”. The maximum allowable value would be “99.99”.  Blanks would not be allowed.Revised. Added codes 1.1, 1.2, and 1.3numeric.TumorOver time, the definitions for the Pediatric ID and the input codes and instructions for other related Pediatric data items may change. This item identifies the correct interpretation of information recorded.A,C,I,MStage/Prognostic FactorsRS*NAACCR/SEER252025
1134Pediatric ID Version OriginalpediatricIdVersionOriginal5This item indicates the version of Pediatric component of the SEER Staging API used to assign the 2024 and later pediatric staging fields of Pediatric ID and Pediatric input fields. This data item is recorded the first time the Pediatric ID is determined. This data item should not be updated each time the related input fields are modified.0.3-99.99..Pediatric ID Version Current is a code with up to 5 digits, a decimal and then up to 2 more digits. (e.g., 1.5, 10.12). The first two digits represent the major version number related to diagnosis year; the second two digits represent minor version changes with the diagnosis years. The minimum allowable value would be “0.5”. The maximum allowable value would be “99.99”.  Blanks would not be allowed. This data item will be generated by registry software. No coding instructions are required.numeric.TumorOver time, the definitions for the Pediatric ID and the input codes and instructions for other related Pediatric data items may change. This item identifies the correct interpretation of information recorded.A,C,I,MStage/Prognostic FactorsRS*NAACCR/SEER252025
1135Toronto Version NumbertorontoVersionNumber1This item indicates the Toronto Staging Version number that the Pediatric staging is based on. This data item is recorded based on when the case is abstracted.1, 2..numeric.TumorThe Pediatric Staging API is based on the Toronto Staging System, so named because the definitions were first discussed at a meeting held in Toronto.  Over time, the definitions will be revised, and the Pediatric staging API will be updated accordingly. This value captures the Toronto version which the current Pediatric Staging API is based on.A,C,I,MNewStage/Prognostic FactorsRS*NAACCR/SEER252025
1136Pediatric Primary TumorpediatricPrimaryTumor3Pediatric Primary Tumor is part of the Pediatric Staging data collection system and is used to classify contiguous growth (extension) of the primary tumor within the organ of origin or its direct extension into neighboring organs. See also Pediatric Regional Nodes \[1137\], and Pediatric Mets \[1138\]. Effective for cases diagnosed 1/1/2024 and forward.000, Schema-Specific Does where needed, 800, 888, 999..Schema-specific codes where needed.numericSee the most current version of [SEER\RSA](https://staging.seer.cancer.gov/) (Pediatric tab) for rules and site-specific codes and coding structures.TumorPediatric Primary Tumor is used to calculate Derived Pediatric T \[1142\] (when applicable). Derivation will occur at the level of the central registry.A,C,I,MNewStage/Prognostic FactorsRS*NAACCR/SEER252025
1137Pediatric Regional NodespediatricRegionalNodes3Pediatric Regional Nodes is part of the Pediatric Staging data collection system and is used **to classify the regional lymph nodes involved with cancer at the time of diagnosis.** See also Pediatric Primary Tumor **\[1136\]** and Pediatric Mets **\[1138\]**. **Effective for cases diagnosed 1/1/2024 and forward.**000, schema-specific codes where needed, 800, 888, 999..Schema-specific codes where needednumericSee the most current version of [SEER\RSA](https://staging.seer.cancer.gov/) (Pediatric tab) for rules and site-specific codes and coding structures.TumorPediatric Regional Nodes is used to calculate Derived Pediatric N **\[1143\]** (when applicable)**.** Derivation will occur at the level of the central registry.A,C,I,MNewStage/Prognostic FactorsRS*NAACCR/SEER252025
1138Pediatric MetspediatricMets2Pediatric Mets is part of the Pediatric Staging data collection system and is used **to classify the distant site(s) of metastatic involvement at time of diagnosis.** See also Pediatric Primary Tumor **\[1136\]** and Pediatric Regional Nodes **\[1137\]**. **Effective for cases diagnosed 1/1/2024 and forward.**00, schema-specific codes where needed, 70, 88, 99..Schema-specific codes where needednumericSee the most current version of [SEER\RSA](https://staging.seer.cancer.gov/) (Pediatric Staging tab) for rules and site-specific codes and coding structures.TumorPediatric Mets is used to calculate Derived Pediatric M **\[1144\]** (when applicable)**.** Derivation will occur at the level of the central registry.A,C,I,MNewStage/Prognostic FactorsRS*NAACCR/SEER252025
1142Derived Pediatric TderivedPediatricT3This item stores the derived Pediatric T value from Pediatric Primary Tumor **\[1136\]** and other fields (when applicable). Effective for cases diagnosed 1/1/2024 and forward...digits.TumorDerived Pediatric T can be used to evaluate disease spread at diagnosis, treatment patterns and outcomes over time.A,C,I,MNewStage/Prognostic FactorsRS*NAACCR/SEER252025
1143Derived Pediatric NderivedPediatricN3This item stores the derived Pediatric N value from Pediatric Regional Nodes **\[1137\]** and other fields (when applicable). Effective for cases diagnosed 1/1/2024 and forward...digitsDerived in Central registry only..TumorDerived Pediatric N can be used to evaluate disease spread at diagnosis, treatment patterns and outcomes over time.A,C,I,MNewStage/Prognostic FactorsRS*NAACCR/SEER252025
1144Derived Pediatric MderivedPediatricM3This item stores the derived Pediatric M value from Pediatric Mets **\[1138\]** and other fields (when applicable). Effective for cases diagnosed 1/1/2024 and forward....TumorDerived Pediatric M can be used to evaluate disease spread at diagnosis, treatment patterns and outcomes over time.A,C,I,MNewStage/Prognostic FactorsRS*NAACCR/SEER252025
1145Derived Pediatric Stage GroupderivedPediatricStageGroup3Derived Pediatric Stage Group is derived using the Pediatric Stage Data Items (Derived Pediatric T \[**1142\]**, Derived Pediatric N **\[1143\]** and Derived Pediatric M **\[1144\]**) algorithm. Other data items may be included in the derivation process. Effective for cases diagnosed 1/1/2024 and forward....TumorDerived Pediatric Stage Group can be used to evaluate disease spread at diagnosis, treatment patterns and outcomes over time.A,C,I,MNewStage/Prognostic FactorsRS*NAACCR/SEER252025
1146Toronto TtorontoT3This item stores the Toronto T value derived from coded fields the Toronto Stage algorithm (when applicable). Effective for cases diagnosed 1/1/2025 and forward....TumorToronto T can be used to evaluate disease spread at diagnosis, treatment patterns and outcomes over time.A,C,I,MNewStage/Prognostic FactorsR*NAACCR/SEER252025
1147Toronto NtorontoN3This item stores the Toronto N value derived from coded fields the Toronto Stage algorithm (when applicable). Effective for cases diagnosed 1/1/2025 and forward....TumorToronto N can be used to evaluate disease spread at diagnosis, treatment patterns and outcomes over time.A,C,I,MNewStage/Prognostic FactorsR*NAACCR/SEER252025
1148Toronto MtorontoM3This item stores the Toronto M value derived from coded fields the Toronto Stage algorithm (when applicable). Effective for cases diagnosed 1/1/2025 and forward....TumorToronto M can be used to evaluate disease spread at diagnosis, treatment patterns and outcomes over time.A,C,I,MNewStage/Prognostic FactorsR*NAACCR/SEER252025
1149Toronto Stage GrouptorontoStageGroup3Toronto Stage Group is derived using the Toronto Stage Data Items (Toronto T **\[9628\]**, Toronto N **\[9629\]** and Toronto M **\[9630\]**) algorithm. Other data items may be included in the derivation process. Effective for cases diagnosed 1/1/2025 and forward....TumorToronto Stage Group can be used to evaluate disease spread at diagnosis, treatment patterns and outcomes over time.A,C,I,MNewStage/Prognostic FactorsR*NAACCR/SEER252025
1150Tumor Marker 1tumorMarker11Records prognostic indicators for specific sites or histologies. CoC offered these items for optional use for cases diagnosed 1996 and forward. See the CoC *ROADS Manual*, 1998 Supplement, for a list of specific sites and histologies. For SEER requirements for the specific sites, histologies, and diagnosis years for which this item is coded, see the 1998 *SEER Program Code Manual*.0-6, 8, 9Tumor Marker One (CoC).RH*Note:* As of January 1, 2003, this data item is no longer required or recommended by CoC. However, the item was collected in the past and it is recommended that historic data be retained. digits.TumorA,C,I,MStage/Prognostic FactorsRHSEER
1160Tumor Marker 2tumorMarker21Records prognostic indicators for specific sites or histologies. CoC offered these items for optional use for cases diagnosed 1996 and forward. See the CoC *ROADS Manual*, 1998 Supplement, for a list of specific sites and histologies. For SEER requirements for the specific sites, histologies, and diagnosis years for which this item is coded, see the 1998 *SEER Program Code Manual*.0-6, 8, 9Tumor Marker Two (CoC).RH*Note:* As of January 1, 2003, this data item is no longer required or recommended by CoC. However, the item was collected in the past and it is recommended that historic data be retained.digits.TumorA,C,I,MStage/Prognostic FactorsRHSEER
1170Tumor Marker 3tumorMarker31Records prognostic indicators for specific sites or histologies. CoC offered these items for optional use for cases diagnosed 1996 and forward. See the CoC *ROADS Manual*, 1998 Supplement, for a list of specific sites and histologies. For SEER requirements for the specific sites, histologies, and diagnosis years for which this item is coded, see the 1998 *SEER Program Code Manual*.0-6, 8, 9Tumor Marker Three (CoC).RH*Note:* As of January 1, 2003, this data item is no longer required or recommended by CoC. However, the item was collected in the past and it is recommended that historic data be retained.digits.TumorA,C,I,MStage/Prognostic FactorsRHSEER
1172Post Transplant Lymphoproliferative Disorder-PTLDptld1Post Transplant Lymphoproliferative Disorder (PTLD) is a lymphoid proliferation arising in a recipient of a solid organ transplant, allogeneic bone marrow transplantation, or an umbilical cord blood transfusion. The patient must  have a history of a solid organ transplant or an allogeneic bone marrow transplant. Both polymorphic and monomorphic PTLD are actually caused by post-transplant immunosuppression. Most cases of PTLD occur within a year of transplantation; however, they can occur any time after the transplant. Monomorphic PTLD may have histology indistinguishable from that of various malignant hematopoietic neoplasms, particularly lymphomas such as Diffuse Large B-cell Lymphoma.0, 1, 2, 4, 8RS*RNote 1: Post Transplant Lymphoproliferative Disorder (PTLD) is a lymphoid proliferation arising in a recipient of a solid organ transplant, allogeneic bone marrow transplantation, or an umbilical cord blood transfusion. The development of PTLD is clinically significant and a prognostic indicator. * Code 0 if the patient has NO or UNKNOWN history of a solid organ transplant, allogeneic bone marrow transplantation, or an umbilical cord blood transplant AND there is no mention of PTLD in the pathology report Note 2: There are several types of PTLD * Polymorphic PTLD: This is a PTLD by itself, there is no histology that is identical to that of another other type of Hematopoietic neoplasm. This type of PTLD is NOT collected in this data item. * Monomorphic PTLD (Code 2): This is the most common PTLD and may have a histology identical to that of another malignant hematopoietic neoplasm. Most common, but not limited to, diffuse large B-cell lymphoma (DLBCL) and Burkitt lymphoma  * Classic Hodgkin lymphoma-PTLD type (Code 3): Under the microscope, Reed-Sternberg cells, which are associated with Hodgkin lymphoma are present * PTLD, NOS (Code 4): Used when only PTLD (NOS) is documented and there is no mention of monomorphic or Hodgkin like type Note 3: This SSDI is effective for diagnosis years 2025+.  * For cases diagnosed prior to 2025, leave this SSDI blank.numericRS*TumorThe presence of PTLD, either polymorphic or monomorphic, has clinical significance and prognostic value, especially in the Pediatric and Adolescence and Young Adult (AYA) populations.A,C,I,MNewStage/Prognostic FactorsRSNAACCR252025
1174PD-L1pdl15The absence or presence of PD-L1 expression determines if the tumor will respond to treatment with a targeted inhibitor (immunotherapy). PD-L1 is done for Non-small cell lung cancers (NSCLC).0.0, 0.1-100.0, XXX.2, XXX.3, XXX.4, XXX.7, XXX.8, XXX.9RS*RS**Note 1:** This SSDI is effective for diagnosis years 2025+.  * For cases diagnosed 2018-2024, leave this SSDI blank **Note 2:** Physician statement PD-L1 can be used to code this data item when no other information is available. **Note 3:** The absence or presence of PD-L1 expression determines if the tumor will respond to treatment with a targeted inhibitor. PDL-1 is done for Non-Small Cell lung cancers (NSCLC) **Note 4:** If neoadjuvant therapy is given, record the assay from tumor specimens prior to neoadjuvant therapy.  * If neoadjuvant therapy is given and there are no PD-L1 results from pre-treatment specimens, report the findings from post-treatment specimenstextRS*TumorPD-L1 is recommended by treatment guidelines for lung cancer to determine if the patient may benefit from checkpoint inhibitor drugs (immunotherapy). It is a new data item for cases diagnosed 1/1/2025+.A,C,I,MNewStage/Prognostic FactorsRSNAACCR252025
1176Spread Through Air Spaces (STAS)spreadThroughAirSpacesStas1Spread Through Air Spaces (STAS) is defined as micropapillary clusters, solid nests, or single cells of tumor extending beyond the edge of the tumor into the air spaces of the surrounding lung parenchyma.0, 1, 8, 9, Blank.RSNewNewNewNewNewnumeric.TumorInitial studies have shown that the presence of STAS is associated with an increased incidence of recurrence in tumors that have undergone limited resection (e.g., segmentectomy, wedge resection).NewNewA,C,I,MNewNewStage/Prognostic FactorsRCNAACCR262026
1178Residual Cancer Burden (RCB)residualCancerBurdenRCB5Residual Cancer Burden (RCB) is a score that measures the amount of cancer remaining in the breast and the regional lymph nodes after neoadjuvant therapy and surgical resection. The RCB score is based on 4 independent prognostic factors measuring the primary tumor bed and 2 independent factors measuring the lymph nodes.  The RCB score combines these 6 independently prognostic factors from the surgical specimen after neoadjuvant therapy into a single continuous score. This score is prognostic across breast cancer subtypes, different treatments, and within existing stage groups.  The independent prognostic factors include 1. Primary Tumor Bed 1. Primary Tumor Bed area (measured in millimeters) 1. Includes the largest two dimensions 2. Overall Cancer Cellularity (as percentage of area) 3. Percentage of cancer that is invasive disease 4. Percentage of cancer that is in situ disease 2. Lymph nodes 1. Number of positive lymph nodes 2. Diameter of largest metastasis0.000-9.999, X.777, X.888, X.999, Blank.RSNewNewNewNewNewtext.TumorNeoadjuvant therapy is now standard of care for HER2+ and triple negative breast carcinoma. Quantification of residual disease after neoadjuvant therapy determines further patient management in this setting. The Residual Cancer Burden (RCB) is the most validated measure of volume of residual disease post neoadjuvant for breast cancer and has prognostic value.NewNewA,C,I,MNewNewStage/Prognostic FactorsRCNAACCR262026
1179Residual Cancer Burden ClassresidualCancerBurdenClass1Residual Cancer Burden (RCB) is a score that measures the amount of cancer remaining in the breast and the regional lymph nodes after neoadjuvant therapy and surgical resection. The RCB score is based on 4 independent prognostic factors measuring the primary tumor bed and 2 independent factors measuring the lymph nodes.  * See Residual Cancer Burden (RCB) Score for further information on these prognostic factors. Based on the RCB score, patients are then divided into four different classes. These classes are used to determine the likelihood of a patient being cancer free after treatment.  * RCB-0 (pathologic complete response). No residual invasive cancer is present. * RCB-1 (minimal burden). Very little residual invasive cancer is present. * RCB-2 (moderate burden). A moderate amount of residual invasive cancer is present. * RCB-3 (extensive burden). A large amount of residual invasive cancer is present.0, 1, 2, 3, 7, 8, 9, Blank.RSNewNewNewNewNewnumeric.TumorNeoadjuvant therapy is now standard of care for HER2+ and triple negative breast carcinoma. Quantification of residual disease after neoadjuvant therapy determines further patient management in this setting. The Residual Cancer Burden (RCB) is the most validated measure of volume of residual disease post neoadjuvant for breast cancer and has prognostic value.NewNewA,C,I,MNewNewStage/Prognostic FactorsRCNAACCR262026
1182Lymphovascular InvasionlymphVascularInvasion1Lymphovascular invasion (LVI) indicates the presence or absence of tumor cells in lymphatic channels (not lymph nodes) or blood vessels within the primary tumor as noted microscopically by the pathologist. LVI includes lymphatic invasion, vascular invasion, and lymphovascular invasion.0-4,8,9Lymph-vascular InvasionR*RdigitsR*TumorPresence or absence of cancer cells in the lymphatic ducts or blood vessels is useful for prognosis. CAP Protocols for some disease sites will be expanded to distinguish between lymphatic and small vessel invasion only, venous (large vessel) invasion only, and BOTH lymphatic and small vessel AND venous (large vessel) invasion.A,C,I,MStage/Prognostic FactorsRSAJCC122010
1184White Blood Cell CountwhiteBloodCellCount7White Blood Cell Count (WBC) will record the actual lab value prior to treatment.1.1-99999.9, XXXXX.1, XXXXX.2, XXXXX.3, XXXXX.4, XXXXX.7, XXXXX.8, XXXXX.9..**Note 1: Effective years** * This SSDI is effective for diagnosis years 2024+ * For cases diagnosed 2018-2023, this SSDI must be blank **Note 2:** **Physician statement** Physician statement of WBC (White Blood Cell Count) Pretreatment Lab Value can be used to code this data item when no other information is available.text**Source documents**: blood tests/laboratory reports (white blood cell count).TumorThis is part of the National Childhood Cancer Registry (NCCR) project to collect more specific information on pediatric patients. Registries part of the NCCR will start collection on specific pediatric data items with 2024 diagnoses.A,C,I,MNewStage/Prognostic FactorsRS*NAACCR/SEER252025
1185Intl Neuroblastoma Risk Grp Stag Sys (INRGSS)inrgss1International Neuroblastoma Risk Group Staging System (INRGSS) for Neuroblastoma is defined based on clinical work up and image-defined risk factors.  The INRGSS is a clinically based staging system and is able to be utilized for every single neuroblastoma tumor as it is based on the clinical work up and image-defined risk factors * Primary source of information for this data item is imaging * Do not code any staging information from results of surgical resection in this data item _Note_: There is a different staging system available for patients who have surgery (International Neuroblastoma Staging System (INSS)) which is collected in Pediatric Primary Tumor, Pediatric Regional Nodes, and Pediatric Mets1, 2, 3, 4, 8, 9INRG..**Note 1: Effective years** * This SSDI is effective for diagnosis years 2024+ * For cases diagnosed 2018-2023, this SSDI must be blank **Note 2: Image-Defined Risk Factors** Image-Defined Risk Factors in Neuroblastic Tumors: Staging requires assessment of whether patients have none, or one or more of the image-defined risk factors (IDRF). These IDRF’s are based on imaging prior to any surgical resection or other treatment.  Ipsilateral tumor extension within two body compartments Neck-chest, chest-abdomen, abdomen-pelvis Neck Tumor encasing carotid and/or vertebral artery and/or internal jugular vein Tumor extending to base of skull Tumor compressing the trachea Cervico-thoracic junction Tumor encasing brachial plexus roots Tumor encasing subclavian vessels and/or vertebral and/or carotid artery Tumor compressing the trachea Thorax Tumor encasing the aorta and/or major branches Tumor compressing the trachea and/or principal bronchi Lower mediastinal tumor, infiltrating the costovertebral junction between T9 and T12 Thoraco-abdominal Tumor encasing the aorta and/or vena cava Abdomen, pelvis  Tumor infiltrating the porta hepatis and/or the hepatoduodenal ligament Tumor encasing branches of the superior mesenteric artery at the mesenteric root Tumor encasing the origin of the coeliac axis, and/or of the superior mesenteric artery Tumor invading one or both renal pedicles Tumor encasing the aorta and/or vena cava Tumor encasing the iliac vessels Pelvic tumor crossing sciatic notch Intraspinal tumor extension whatever the location provided that More than one third of the spinal canal in the axial plane is invaded and/or the perimedullary leptomeningeal spaces are not visible and/or the spinal cord signal is abnormal  Infiltration of adjacent organs/structures Pericardium, diaphragm, kidney, liver, duodeno-pancreatic block, and mesentery **Note 4: Ascites and pleural effusion** * Ascites and/or a pleural effusion, even with malignant cells, do not constitute metastatic disease unless they are remote from the body compartment of the primary tumor. **Note 5: Lymph node involvement** * Regional lymph node involvement does not factor into staging * **Code 3** for non-regional lymph node involvement (distant lymph nodes)numeric.TumorThis is part of the National Childhood Cancer Registry (NCCR) project to collect more specific information on pediatric patients. Registries part of the NCCR will start collection on specific pediatric data items with 2024+ diagnoses.A,C,I,MNewStage/Prognostic FactorsRS*NAACCR/SEER252025
1186n-MYC AmplificationnMycAmplification1n-MYC Amplification is a gene that normally regulates cell growth. Studies have shown that n-MYC amplification is an indicator of poor prognosis and increased risk of unfavorable outcomes in patients with neuroblastoma. This field indicates the n-MYC status of a neuroblastoma tumor after a pathologic specimen is obtained.0, 1, 2, 7, 8, 9,..**Note 1: Effective years** * This SSDI is effective for diagnosis years 2024+ * For cases diagnosed 2018-2023, this SSDI must be blank **Note 2: Physician statement**  Physician statement of n-MYC can be used to code this data item when no other information is available.numeric**Source documents:** molecular pathology report (may be addendum to original pathology report) For further information, refer to the **Neuroblastoma** cancer protocol published by the College of American Pathologists..TumorThis is part of the National Childhood Cancer Registry (NCCR) project to collect more specific information on pediatric patients. Registries part of the NCCR will start collection on specific pediatric data items with 2024+ diagnoses.A,C,I,MNewStage/Prognostic FactorsRS*NAACCR/SEER252025
1187Intl Neuroblastoma Path Prog Class (INPC)inpc1The International Neuroblastoma Pathology Prognostic Classification (INPC) categorizes neuroblastomas as favorable or unfavorable histologies based on the following factors: age, neuroblastic maturation, Schwannian stromal content, Mitosis-kayorrhexis index (MKI), and degree of differentiation (grade).  The International Neuroblastoma Pathology Prognostic Classification (INPC) (unfavorable versus favorable histology) is a biologically relevant classification based on morphologic features of neuroblastic tumors which has prognostic indications. It is based on the following criteria * Age * Neuroblastic maturation * Schwannian stromal content * Mitosis-kayorrhexis index (MKI) * Degree of differentiation (grade)0, 1, 7, 8, 9International Neuroblastoma Pathology Prognostic Classification (INPC), Shimada Classification, Unfavorable histology, or Favorable histology..**Note 1: Effective years** * This SSDI is effective for diagnosis years 2024+ * For cases diagnosed 2018-2023, this SSDI must be blank **Note 2: Physician statement** * Physician statement of unfavorable vs favorable histology can be used to code this data item when no other information is available, provided there is information that the results are from a biopsy or surgical resection without neoadjuvant therapy. **Note 3: Neoadjuvant Therapy** * The INPC results are to be coded based on either biopsy or surgical resection (without neoadjuvant therapy). * **Code 9** if the only results are from a post neoadjuvant surgical resection.digits**Source documents:** pathology reportFor further information, refer to the **Neuroblastoma** cancer protocol published by the College of American Pathologists.TumorThis is part of the National Childhood Cancer Registry (NCCR) project to collect more specific information on pediatric patients. Registries part of the NCCR will start collection on specific pediatric data items with 2024+ diagnoses.A,C,I,MNewStage/Prognostic FactorsRS*NAACCR/SEER252025
1188IRSS Stage for Eye-2irssStageForEye21Bilateral retinoblastoma is abstracted as a single primary regardless of timing, but there is no effective way to measure the different extent of diseases or stages for each eye beyond text. Currently, abstractors are required to enter the information of the most advanced eye in the staging data fields, losing all measurable data on the stage the less advanced eye. This field allows the abstractor to enter the individual stages for each eye in cases of bilateral retinoblastoma at the time of diagnosis.0, 1, 2, 3, 4, 7, 8, 9..**Note 1: Effective years** * This SSDI is effective for diagnosis years 2024+ * For cases diagnosed 2018-2023, this SSDI must be blank **Note 2: Bilateral retinoblastomas** * This data item records the stage of the second eye when there are bilateral retinoblastomas. * **Code 7** if only one eye is involved (unilateral retinoblastoma) * Extension of one eye (unilateral retinoblastoma) is coded in Pediatric Primary Tumor * If there are bilateral retinoblastomas, record the Stage Group of the lesser/lower stage in this data item (more advanced/higher stage is recorded in Pediatric Primary Tumor) * Do not record a stage (Stage 0-IV) in this data item if only one eye is invovlednumeric**Source documents:** imaging, pathology report, clinician’s statement.TumorEven though staging information for only one retinoblastoma tumor can currently be captured in data form, abstractors are still required to put treatment information for bilaterally affected eyes into the treatment fields of the abstract. The ability to capture measurable staging data of the contralateral eye will provide substantiation of the treatment captured for both eyes in the abstract.A,C,I,MNewStage/Prognostic FactorsRS*NAACCR/SEER252025
1189Chromosome 16q: Loss of Heterozygositychromosome16qLossHeterozygosity1Chromosome 16q: Loss of Heterozygosity (LOH) refers to the loss of genetic material normally found on the short arm of one of the patient's two copies of chromosome 16. Occurs in approximately 5% of favorable (non-anaplastic) histology Wilm’s tumor (FHWT) cells and has been shown to be associated with inferior relapse-free survival (RFS) and overall survival (OS) in patients with FH Wilm’s tumor. This testing is commonly done in conjunction with Chromosome 1p: Loss of Heterozygosity (NAACCR ID: 3801) and Chromosome 1q: Gain of heterozygosity (GOH) (NAACCR ID: 1190: Chromosome 1q Status). This is a special molecular diagnostic test performed on tumor tissue to identify loss of genetic material found on the long arm of one of the patient’s two copies of chromosome 16. A normal cell will contain two complete copies of each chromosome, one from each parent, and this normal state is termed heterozygous. Loss of heterozygosity (LOH) is an abnormal state reflecting loss of the whole arm of chromosome 16q following a chromosomal translocation event.0, 1, 7, 8,9..**Note 1: Effective years** * This SSDI is effective for diagnosis years 2024+ * For cases diagnosed 2018-2023, this SSDI must be blank **Note 2:** **Physician statement** * Physician statement of Chromosome 16q deletion/LOH can be used to code this data item when no other information is available.numeric**Source documents:** molecular pathology report (may be addendum to original pathology report)..TumorThis is part of the National Childhood Cancer Registry (NCCR) project to collect more specific information on pediatric patients. Registries part of the NCCR will start collection on specific pediatric data items with 2024+ diagnoses.A,C,I,MStage/Prognostic FactorsRS*NAACCR/SEER252025
1190Chromosome 1q Statuschromosome1qStatus1Gain of chromosome 1q is one of the most common cytogenetic findings in Wilms tumor, occurring approximately 30% of tumors. It is associated with a poorer relapse-free survival (RFS) and overall survival (OS) in patients with favorable (non-anaplastic) histology Wilm’s tumor (FHWT). This testing is commonly done in conjunction with Chromosome 1p: Loss of Heterozygosity (see NAACCR ID: 3801) and Chromosome 16q: Loss of Heterozygosity (see NAACCR ID: 1189). This is a special molecular diagnostic test performed on tumor tissue to identify gain of genetic material normally found on the short arm of one of the patient's two copies of chromosome 1. A normal cell will contain two complete copies of each chromosome, one from each parent, and this normal state is termed heterozygous. Gain of heterozygosity (GOH) is an abnormal state reflecting gain of the whole arm of chromosome 1q following a chromosomal translocation event.0, 1, 7, 8, 9..**Note 1: Effective years** * This SSDI is effective for diagnosis years 2024+ * For cases diagnosed 2018-2023, this SSDI must be blank **Note 2:** **Physician statement** * Physician statement of Chromosome 1q gain can be used to code this data item when no other information is available.numeric**Source documents:** molecular pathology report (may be addendum to original pathology report)..TumorThis is part of the National Childhood Cancer Registry (NCCR) project to collect more specific information on pediatric patients. Registries part of the NCCR will start collection on specific pediatric data items with 2024+ diagnoses.A,C,I,MNewStage/Prognostic FactorsRS*NAACCR/SEER252025
1191EWSR1-FLI1 fusionewsr1Fli1Fusion1This data item documents rearrangement (fusion) in EWR1 genes. EWSR1-FLI1 fusion occurs in about 90% of Ewing Sarcomas and functions as both a pioneering transcription factor and potent oncogene.0-5, 7-9..**Note 1: Effective years** * This SSDI is effective for diagnosis years 2024+ * For cases diagnosed 2018-2023, this SSDI must be blank **Note 2:** **Physician statement** * Physician statement of EWSR1-FLI1 fusion can be used to code this data item when no other information is available.numeric**Source documents:** molecular pathology report (may be addendum to original pathology report)..TumorThis is part of the National Childhood Cancer Registry (NCCR) project to collect more specific information on pediatric patients. Registries part of the NCCR will start collection on specific pediatric data items with 2024+ diagnoses.A,C,I,MNewStage/Prognostic FactorsRS*NAACCR/SEER252025
1192Pretext Clinical StagingpretextClinicalStaging1PRETEXT stands for PRE-Treatment Extent of tumor. This field describes the extent of involvement within the four lobes of the liver at time of a pediatric liver tumor diagnosis. It is based off clinical imaging and was originally designed to standardize imaging evaluation and risk stratification of hepatoblastoma before neoadjuvant chemotherapy or tumor resection.1-4, 8, 9..**Note 1: Effective years** * This SSDI is effective for diagnosis years 2024+ * For cases diagnosed 2018-2023, this SSDI must be blank **Note 2: Criteria for coding** * This SSDI is based on imaging findings only\*\*. Do not\*\* code any findings from surgical resection in this data item. Evaluation must also be done prior to any neoadjuvant therapy **Note 3: Pretext Staging-Segments of the live**r * Caudate liver: Segment I _**Note**_: Involvement of the caudate liver is at minimum Stage 2 * Left lateral section: Segments II & III * Left medial section: Segments IVA & IVB * Right anterior section: Segments V & VIII * Right posterior section: Segments VI & VIInumeric**Source documents:** imaging.TumorAfter initially being created by the International Childhood Liver Tumours Strategy Group (SIOPEL) in 1990, PRETEXT was introduced for use within the United States in 2014 by the Children’s Oncology Group (COG) once radiographic imaging became more sophisticated and exploratory surgery at diagnosis was no longer advisable. It is used as a central component of risk stratification schemes that define treatment of hepatoblastoma.A,C,I,MNewStage/Prognostic FactorsRS*NAACCR/SEER252025
1193FOXO1 Gene Rearrangementsfoxo1GeneRearrangements1FOXO1 gene rearrangement fusions are found to be positive in about 85% of alveolar rhabdomyosarcoma patients, while they are generally negative for embryonal rhabdomyosarcomas. The presence of these fusions indicates a poor prognosis. Identifying these fusions will also provide new therapeutic opportunities for the treatment of fusion positive rhabdomyosarcomas (FP-RMS).0-4, 7-9FKHR-PAX3, FKHR-PAX7..**Note 1: Effective years** * This SSDI is effective for diagnosis years 2024+ * For cases diagnosed 2018-2023, this SSDI must be blank **Note 2:** **Physician statement** * Physician statement of FOXO1 gene rearrangements can be used to code this data item when no other information is available. **Note 3: Applicable histologies** * FOXO1 may be recorded all sarcomas; however, it is primary done for Alveolar Rhabdomyosarcomas * Embryonal Rhabdomyosarcomas are usually negative, and therefore the test is usually not done.  * Code 9 if information is not availablenumeric**Source documents:** molecular pathology report (may be addendum to original pathology report).TumorThis is part of the National Childhood Cancer Registry (NCCR) project to collect more specific information on pediatric patients, specifically for Rhabdomyosarcoma. Registries part of the NCCR will start collection on specific pediatric data items with 2024+ diagnoses.A,C,I,MNewStage/Prognostic FactorsRS*NAACCR/SEER252025
1200RX Date SurgeryrxDateSurgery8Date the first surgery of the type described under Surgery of Primary Site, Scope of Regional Lymph Node Surgery, or Surgery of Other Regional Site(s), Distant Site(s) or Distant Lymph Nodes was performed. See also RX Summ--Surg Prim Site \[1290\], RX Summ--Scope Reg LN Sur \[1292\], and RX Summ--Surg Oth Reg/Dis \[1294\]. See [**Data Descriptor Table**](https://apps.naaccr.org/data-dictionary/data-dictionary/version=24/chapter-view/data-descriptor-table/) for date format.   Formerly RX Date--Surgery.Valid datesDate of Cancer-Directed Surgery (CoC), Date of First Surgical Procedure (CoC), Date of Surgery, RX Date--Surgery.RdateYYYYMMDDR*TumorThe dates on which different treatment modalities were started are used to evaluate whether the treatments were part of first-course therapy and to reconstruct the sequence of first-course treatment modes.A,C,I,MTreatment-1st CourseRCoC
1210RX Date RadiationrxDateRadiation8Records the date on which radiation therapy began at any facility that is part of the first course of treatment. See [**Data Descriptor Table**](https://apps.naaccr.org/data-dictionary/data-dictionary/version=24/chapter-view/data-descriptor-table/) for date format.    Formerly RX Date--RadiationValid datesDate Radiation Started (CoC), RX Date--Radiation.RdateYYYYMMDDR*TumorThe dates on which different treatment modalities were started are used to evaluate whether the treatments were part of first-course therapy and to reconstruct the sequence of first-course treatment modes.A,C,I,MTreatment-1st CourseRCoC
1220RX Date ChemorxDateChemo8Date of initiation of chemotherapy that is part of the first course of treatment. See also RX Summ--Chemo \[1390\]. See [**Data Descriptor Table**](https://apps.naaccr.org/data-dictionary/data-dictionary/version=24/chapter-view/data-descriptor-table/) for date format. Formerly RX Date--Chemo.Valid datesDate Chemotherapy Started (CoC), RX Date--Chemo.RdateYYYYMMDD_Note:_ CoC discontinued support of this item from 2003 through 2009.R*TumorThe dates on which different treatment modalities were started are used to evaluate whether the treatments were part of first-course therapy and to reconstruct the sequence of first-course treatment modes.A,C,I,MTreatment-1st CourseRCoC
1230RX Date HormonerxDateHormone8Date of initiation for hormone therapy that is part of the first course of treatment. See also RX Summ--Hormone \[1400\]. See [**Data Descriptor Table**](https://apps.naaccr.org/data-dictionary/data-dictionary/version=24/chapter-view/data-descriptor-table/) for date format. Formerly RX Date--Hormone.Valid datesDate Hormone Therapy Started (CoC), RX Date--Hormone.RdateYYYYMMDD_Note:_ CoC discontinued support of this item from 2003 through 2009.R*TumorThe dates on which different treatment modalities were started are used to evaluate whether the treatments were part of first-course therapy and to reconstruct the sequence of first-course treatment modes.A,C,I,MTreatment-1st CourseRCoC
1240RX Date BRMrxDateBrm8Date of initiation for immunotherapy (a.k.a. biological response modifier) that is part of the first course of treatment. See also RX Summ--BRM \[1410\]. See [**Data Descriptor Table**](https://apps.naaccr.org/data-dictionary/data-dictionary/version=24/chapter-view/data-descriptor-table/) for date format. Formerly RX Date--BRM.Valid datesDate Immunotherapy Started (CoC), RX Date--BRM.RdateYYYYMMDD_Note:_ CoC discontinued support of this item from 2003 through 2009.R*TumorThe dates on which different treatment modalities were started are used to evaluate whether the treatments were part of first course of therapy and to reconstruct the sequence of first-course treatment modes.A,C,I,MTreatment-1st CourseRCoC
1250RX Date OtherrxDateOther8Date of initiation for other treatment that is part of the first course of treatment at any facility. See RX Summ--Other \[1420\]. See [**Data Descriptor Table**](https://apps.naaccr.org/data-dictionary/data-dictionary/version=24/chapter-view/data-descriptor-table/) for date format. Formerly RX Date--Other.Valid datesDate Other Treatment Started (CoC), RX Date--Other.RdateYYYYMMDDR*TumorThe dates on which different treatment modalities were started are used to evaluate whether the treatments were part of first-course therapy and to reconstruct the sequence of first-course treatment modes.A,C,I,MTreatment-1st CourseRCoC
1260Date Initial RX SEERdateInitialRxSeer8Date 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 [**Data Descriptor Table**](https://apps.naaccr.org/data-dictionary/data-dictionary/version=24/chapter-view/data-descriptor-table/) for date format.    Formerly Date of Initial RX--SEER.Valid datesDate Started (SEER), Date Therapy Initiated (SEER), Date of Initial RX--SEER.**Clarification of NPCR Required Status** Central registries funded by NPCR are required to collect either Date Initial RX SEER \[1260\] or Date 1st Crs RX CoC \[1270\]..dateYYYYMMDDR#*TumorA,C,I,MTreatment-1st CourseRSEER
1270Date 1st Crs RX CoCdate1stCrsRxCoc8Date of initiation of the first therapy for the cancer being reported, using the CoC definition of first course. The date of first treatment includes the date a decision was made not to treat the patient. See _STORE_ for details. See Chapter V, Unresolved Issues for further discussion of the difference between SEER and CoC items. See [**Data Descriptor Table**](https://apps.naaccr.org/data-dictionary/data-dictionary/version=24/chapter-view/data-descriptor-table/) for date format.    Formerly Date of 1st Crs RX--CoC.Valid datesDate Started (pre 96 CoC), Date of 1st Crs RX--CoC, Date of First Course Treatment (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\].RdateYYYYMMDDR#*TumorA,C,I,MTreatment-1st Course.CoC
1280RX Date DX/Stg ProcrxDateDxStgProc8Records the date on which the surgical diagnostic and/or staging procedure was performed. See Surgical and Diagnostic Staging Procedure \[1350\]. See [**Data Descriptor Table**](https://apps.naaccr.org/data-dictionary/data-dictionary/version=24/chapter-view/data-descriptor-table/) for date format.   Formerly RX Date--DX/Stg Proc.Valid datesDate of Diagnostic, Staging or Palliative Procedures (1996-2002), Date of Non Cancer-Directed Surgery ( CoC), Date of Surgical Diagnostic and Staging Procedure (CoC), RX Date--DX/Stg Proc, RX Date--DX/Stg/Pall Proc.RdateYYYYMMDD_Note:_ This is a CoC item and for tumors diagnosed from January 1, 1996, through December 31, 2002, this may have been the date on which diagnostic, staging, and palliative procedures were performed. Beginning with tumors diagnosed on or after January 1, 2003, palliative procedures are collected in RX Summ--Palliative Proc \[3270\] and RX Hosp--Palliative Proc \[3280\]..TumorA,C,I,MTreatment-1st Course.CoC
1285RX Summ--Treatment StatusrxSummTreatmentStatus1This data item is a summary of the status for all treatment modalities. It is used in conjunction with Date Initial RX SEER [1260] and/or Date 1st Crs RX CoC [1270] and each modality of treatment with their respective date field to document whether treatment was given or not given, whether it is unknown if treatment was given, or whether treatment was given on an unknown date. Also indicates active surveillance (watchful waiting). This data item is effective for January 2010+ diagnoses.0-2, 9.RdigitsR#TumorThis field will document active surveillance (watchful waiting) and eliminate searching each treatment modality to determine whether treatment was given.A,C,I,MTreatment-1st CourseRSEER/CoC122010
1290RX Summ--Surg Prim Site 03-2022rxSummSurgPrimSite2Site-specific codes for the type of surgery to the primary site performed as part of the first course of treatment. This includes treatment given at all facilities as part of the first course of treatment.00, 10-80, 90, 98, 99 (site-specific)Cancer-Directed Surgery (pre-96 CoC), RX Summ--Surg Prim Site, Surgery of Primary Site (SEER/CoC).RdigitsRight justified, zero filledRefer to the most recent version of STORE and SEER Program Code manual for additional instructions. Also see Surgery Codes and Surgery Codes Crosswalks: [https://www.naaccr.org/crosswalks-interoperability/](https://www.naaccr.org/crosswalks-interoperability/)RHTumorA,C,I,MUpdated NPCRTreatment-1st CourseRHSEER/CoC5.11997
1291RX Summ--Surg Prim Site 2023rxSummSurgPrimSite20234Surgery of Primary Site describes a surgical procedure that removes and/or destroys tissue of the primary site that is performed as part of the initial diagnostic and staging work-up or first course of therapy.A000, A200-A990, B000, B200-B990, BlankSurgery of Primary Site.RmixedAlphanumericRefer to latest version of the Store manual. Also see Surgery Codes and Surgery Codes Crosswalks: [https://www.naaccr.org/crosswalks-interoperability/](https://www.naaccr.org/crosswalks-interoperability/)RTumorThis data item can be used to compare the efficacy of treatment options.A,C,I,MUpdated NPCRTreatment-1st CourseRSEER/CoC232023
1292RX Summ--Scope Reg LN SurrxSummScopeRegLnSur1Describes the removal, biopsy or aspiration of regional lymph node(s) at the time of surgery of the primary site or during a separate surgical event at all facilities.0-7, 9Scope of Regional Lymph Node Surgery (SEER/CoC).R*Note:* One important use of registry data is the tracking of treatment patterns over time. To compare contemporary treatment to previously published treatment based on former codes, or to data unmodified from pre-1998 definitions, the ability to differentiate surgeries in which four or more regional lymph nodes are removed is desirable. However, it is very important to note that the distinction between codes 4 and 5 is made to permit comparison of current surgical procedures with procedures coded in the past when the removal of fewer than 4 nodes was not reflected in surgery codes. It is not intended to reflect clinical significance when applied to a particular surgical procedure. It is important to avoid inferring, by data presentation or other methods, that one category is preferable to another within the intent of these items.digitsRefer to the most recent versions of *STORE* and the *SEER Program Code Manual* for instructions that should be applied to all surgically treated cases for all types of cancers. The treatment of breast and skin cancers are where the distinction between sentinel lymph node biopsies (SLNBx) and more extensive dissection of regional lymph nodes is most frequently encountered. For all other sites, non-sentinel regional node dissections are typical, and codes 2, 6 and 7 are infrequently usedRTumorIn evaluating quality-of-care and treatment practices it is important to identify the removal, biopsy, or aspiration of regional lymph node(s) at the time of surgery of the primary site or during a separate surgical event.A,C,I,MTreatment-1st CourseRSEER/CoC5.11997
1294RX Summ--Surg Oth Reg/DisrxSummSurgOthRegDis1Records the surgical removal of distant lymph nodes or other tissue(s)/organ(s) beyond the primary site.0-5, 9Surgery of Other Regional Site(s), Distant Site(s) or Distant Lymph Nodes (SEER/CoC), Surgical Procedure/Other Site.RdigitsRefer to the most recent version of *STORE* and *SEER Program Code Manual* for additional instructions.RTumorThe removal of non-primary tissue documents the extent of surgical treatment and is useful in evaluating the extent of metastatic involvement.A,C,I,MTreatment-1st CourseRSEER/CoC5.11997
1296RX Summ--Reg LN ExaminedrxSummRegLnExamined2Codes for the number of regional lymph nodes examined in conjunction with surgery performed as part of the first-course treatment. This includes treatment given at all facilities as part of the first course of treatment. See also RX Summ--Scope Reg LN Sur [1292].00-90, 95-99Number of Regional Lymph Nodes Examined (SEER/CoC), Number of Regional Lymph Nodes Removed (CoC).RH*Note:* As of January 1, 2003, this data item is no longer required or recommended by CoC. However, the item was collected in the past and it is recommended that historic data be retained.digitsRight justified, zero filled.TumorA,C,I,MTreatment-1st CourseRHSEER/CoC5.11997
1310RX Summ--Surgical ApprochrxSummSurgicalApproch1Codes for method used to approach the surgical field for the primary site.0-9 (site-specific)Surgical Approach (CoC).RHdigits*Note:* As of January 1, 2003, this data item is no longer required or recommended by CoC. However, the item was collected in the past and it is recommended that historic data be retained. This former item should not be confused with NAACCR item [668] RX HOSP--SURG APP 2010 .See the CoC *ROADS Manual*, 1998 Supplement, for site-specific codes..TumorA,C,I,MTreatment-1st Course.CoC
1320RX Summ--Surgical MarginsrxSummSurgicalMargins1Codes describe the final status of surgical margins after resection of the primary tumor. See also RX Summ--Surg Prim Site [1290].0-3, 7-9Residual Primary Tumor Following Cancer-Directed Surgery (pre-96 CoC), Surgical Margins (CoC).R*Note:* Codes were site specific (1998-2002), and have been changed to be generic across all disease sites.digitsRefer to the most recent version of *STORE* for additional instructions..TumorThis item serves as a quality measure for pathology reports, is used for staging, and may be a prognostic factor in recurrence. This item is not limited to cases that have been staged. It applies to all cases that have a surgical procedure of the primary site.A,C,I,MTreatment-1st CourseR*CoC
1330RX Summ--Reconstruct 1strxSummReconstruct1st1Codes for surgical procedures done to reconstruct, restore, or improve the shape and appearance or function of body structures that are missing, defective, damaged, or misshapen by cancer or therapies. Reconstructive/restorative procedures are coded here when started during the first course of therapy. CoC introduced site-specific codes for this item in the CoC *ROADS Manual* 1998 Supplement. RX Coding System--Current [1460] identifies which coding system applies. SEER collects reconstructive procedures for breast cancer tumors only.For reconstructive/restorative procedures performed later, see Subseq RX--Reconstruct Del [1741]. See also RX Summ--Surgery Type [1640].0-9 (site-specific)Reconstruction--First Course (SEER), Reconstruction/Restoration-First Course (CoC).RHdigits*Note:* This data item is no longer supported by CoC (as of January 1, 2003)..TumorA,C,I,MTreatment-1st Course.SEER
1335RX Summ--Recon BreastrxSummReconBreast4Records the reconstruction procedure immediately following resection performed at any facility. This data item is required beginning with diagnosis year 2024 and breast cases only.A000, A100, A200, A300, A400, A500, A600, A610, A620, A630, A640, A900, A970, A980, A990.Rmixed.TumorBreast reconstruction was previously collected within the breast surgery codes. CoC will collect this data item to support the Synoptic Operative Reports and allow for more descriptive reconstruction codes.A,C,I,MRevisedTreatment-1st CourseRCoC242024
1340Reason for No SurgeryreasonForNoSurgery1Records the reason that no surgery was performed on the primary site.0-2, 5-9Reason for No CA Dir Surgery (CoC), Reason for No Cancer-Directed Surgery (SEER), Reason for No Surgery to Primary Site.RdigitsRTumorThis data item provides information related to the quality of care and describes why primary site surgery was not performed.A,C,I,MTreatment-1st CourseRSEER/CoC
1350RX Summ--DX/Stg ProcrxSummDxStgProc2Identifies the surgical procedure(s) performed in an effort to diagnose and/or stage disease.00-07, 09Non Cancer-Directed Surgery (CoC), RX Summ--DX/Stg/Pall Proc, Surgical Diagnostic and Staging Procedure (1996-2002).R*Note:* CoC recommends this item for tumors diagnosed 1996 and forward. For tumors diagnosed before 1996, this item may have been converted, and tumors with surgery would have been converted to 09 in this field. See also RX Summ--Surg Prim Site [1290] and RX Summ--Reconstruct 1st [1330]. For SEER and pre-1996 CoC, see RX Summ--Surgery Type [1640]. For tumors diagnosed between 1996 and 2002 this field may have described palliative care. For tumors diagnosed on or after January 1, 2003, palliative care is coded in a new field RX Summ--Palliative Proc [3270].digitsRight justified, zero filledRefer to the most recent version of *STORE* for additional instructions..TumorA,C,I,MTreatment-1st Course.CoC
1360RX Summ--RadiationrxSummRadiation1Codes for the type of radiation therapy performed as part of the first course of treatment.0-9Radiation (SEER/CoC), Radiation Therapy (pre-96 CoC)..*Note*: CoC discontinued collection of this item in 2003 when FORDS was implemented. For CoC, codes 7 and 8 were used for tumors diagnosed before 1996, but should have been converted to 0 in this field and to the appropriate code in the new field Reason for No Radiation [1430]. SEER continues to use codes 7 and 8 for all years. See Chapter V, Unresolved Issues, for further discussion. In the SEER program, a code 2 for other radiation was used between 1973 and 1987. When the radiation codes were expanded to add codes ‘2’ radioactive implants and ‘3’ radioisotopes, all cases with a code ‘2’ and diagnosed in 1973-1987 were converted to a code ‘6’ radiation other than beam radiation.digits*Note:* Radiation to brain and central nervous system for leukemia and lung cases is coded as radiation in this field.RHTumorA,C,I,MTreatment-1st CourseRHSEER
1370RX Summ--Rad to CNSrxSummRadToCns1For lung and leukemia cases only, codes for radiation given to the brain or central nervous system. Includes treatment given at all facilities as part of the first course. See Chapter V, Unresolved Issues, for more information. *Note:* SEER does not collect this data item beginning with 1998 cases. They retain the codes for older cases in this field, and they have also recoded radiation coded here as radiation in RX Summ--Radiation [1360]. CoC does not collect this data item beginning with 1996 cases.0, 1, 7-9Radiation Therapy to CNS (CoC), Radiation to the Brain and/or Central Nervous System (SEER)..digitsFor Lung and Leukemia Cases only.TumorA,C,I,MTreatment-1st CourseRHSEER/CoC
1380RX Summ--Surg/Rad SeqrxSummSurgRadSeq1Codes for the sequencing of radiation and surgery given as part of the first course of treatment. See also RX Summ--Surg Prim Site [1290], RX Summ--Scope LN Surg [1292], RX Summ--Surg Oth Reg/Dis [1294], and RX Summ--Radiation [1360].0, 2-7, 9Radiation Sequence with Surgery (pre-96 SEER/CoC), Radiation/Surgery Sequence (CoC).RdigitsRTumorA,C,I,MTreatment-1st CourseRSEER/CoC
1390RX Summ--ChemorxSummChemo2Codes for chemotherapy given as part of the first course of treatment or the reason chemotherapy was not given. Includes treatment given at all facilities as part of the first course.00-03, 82, 85-88, 99Chemotherapy (SEER/CoC).RdigitsRight justified, zero filled*Note*: Prior to 2013, targeted therapies that invoke an immune response, such as Herceptin, had been coded as chemotherapy. Effective with cases diagnosed January 1, 2013, and forward these therapies are classified as biological response modifiers. Coding instructions for these changes have been added to the remarks field for the applicable drugs in the SEER\*RX Interactive Drug Database ( <http://seer.cancer.gov/tools/seerrx/>).Refer to the most recent version of *STORE* for additional instructions.RTumorA,C,I,MTreatment-1st CourseRSEER/CoC
1400RX Summ--HormonerxSummHormone2Records whether systemic hormonal agents were administered as first-course treatment at any facility, or the reason they were not given. Hormone therapy consists of a group of drugs that may affect the long-term control of a cancer’s growth. It is not usually used as a curative measure.00, 01, 82, 85-88, 99Endocrine (Hormone/Steroid) Therapy (pre-96 SEER), Hormone Therapy (SEER/CoC).R*Note:* For tumors diagnosed on or after January 1, 2003, information on endocrine surgery and/or endocrine radiation should be coded in the new field, RX Summ--Transplnt/Endocr [3250]. The CoC standards for hospitals do not allow use of codes 02-03 in tumors diagnosed on or after January 1, 2003.digitsRight justified, zero filledRefer to the most recent version of *STORE* and the *SEER Program Code Manual* for additional instructions.RTumorSystemic therapy may involve the administration of one or a combination of agents. This data item allows for the evaluation of the administration of hormonal agents as part of the first course of therapy.A,C,I,MTreatment-1st CourseRSEER/CoC
1410RX Summ--BRMrxSummBrm2Records whether immunotherapeutic (biologic response modifiers) agents were administered as first-course treatment at all facilities or the reason they were not given. Immunotherapy consists of biological or chemical agents that alter the immune system or change the host’s response to tumor cells.00, 01, 82, 85-88, 99Biological Response Modifiers (pre-96 SEER), Immunotherapy (SEER/CoC).R\*Note :\*For tumors diagnosed on or after January 1, 2003, information on bone marrow transplants and stem cell transplants should be coded in the new field, RX SUMM--Transplnt/Endocr \[3250\]. The CoC standards for hospitals do not allow use of codes 02-06 in tumors diagnosed on or after January 1, 2003.digitsRight justified, zero filled_Note_: Prior to 2013, targeted therapies that invoke an immune response, such as Herceptin, had been coded as chemotherapy. Effective with cases diagnosed January 1, 2013, and forward these therapies are classified as biological response modifiers. Coding instructions for these changes have been added to the remarks field for the applicable drugs in the SEER\*RX Interactive Drug Database ( \<http://seer.cancer.gov/tools/seerrx/\>).Refer to the most recent version of** **STORE** **and the** **SEER Program Code Manual** **for additional instructions.RTumorSystemic therapy may involve the administration of one or a combination of agents. This data item allows for the evaluation of the administration of immunotherapeutic agents as part of the first course of therapy.A,C,I,MTreatment-1st CourseRSEER/CoC
1420RX Summ--OtherrxSummOther1Identifies other treatment given at all facilities that cannot be defined as surgery, radiation, or systemic therapy according to the defined data items in this manual. Treatment for reportable hematopoietic diseases can be supportive care, observation, or any treatment that does not meet the usual definition in which treatment modifies, controls, removes, or destroys proliferating cancer tissue. Such treatments include phlebotomy, transfusions, and aspirin.0-3, 6-9Other Cancer-Directed Therapy (SEER/pre-96 CoC), Other Treatment (CoC).RdigitsRefer to the most recent version of *STORE* for additional coding instructionsRTumorInformation on other therapy is used to describe and evaluate the quality-of-care and treatment practices.A,C,I,MTreatment-1st CourseRSEER/CoC
1430Reason for No RadiationreasonForNoRadiation1Code the reason the patient did not receive radiation treatment as part of first course of therapy. See also RX--Regional RX Modality [1570].0-2, 5-9Reason for No Regional Radiation Therapy.RdigitsRTumorA,C,I,MTreatment-1st CourseRCoC
1460RX Coding System--CurrentrxCodingSystemCurrent2Code describing how treatment for this tumor now is coded.00-08, 99..digitsRight justified, zero filledRTumorA,C,I,MTreatment-1st Course.NAACCR
1501Phase I Dose per Fractionphase1DosePerFraction5Records the dose per fraction (treatment session) delivered to the patient in the first phase of radiation during the first course of treatment. The unit of measure is centiGray (cGy). This data item is required for CoC-accredited facilities as of  01/01/2018.00000-99999.RdigitsRight Justified, zero filled.TumorRadiation therapy is delivered in one or more phases with identified dose per fraction. It is necessary to capture information describing the dose per fraction to evaluate patterns of radiation oncology care. Outcomes are strongly related to the dose delivered.A,C,I,MTreatment-1st CourseR*CoC182018
1502Phase I Radiation External Beam Planning Techphase1RadiationExternalBeamTech2Identifies the external beam radiation planning technique used to administer the first phase of radiation treatment during the first course of treatment. This data item is required for CoC-accredited facilities as of 01/01/2018.00-10, 88, 98, 99.Rdigits.TumorExternal beam radiation is the most commonly-used radiation modality in North America. In this data item we specified the planning technique for external beam treatment. Identifying the radiation technique is of interest for patterns of care and comparative effectiveness studies. Historically, the previously-named Regional Treatment Modality data item [1570] utilized codes that were not mutually exclusive. Rather, it included codes describing a mix of modalities, treatment planning techniques, and delivery techniques that are commonly utilized by radiation oncologists. However, every phase of radiation treatment will include a specified modality, planning technique, and delivery technique. The goal of the 2018 implementation of separate phase-specific data items for the recording of Phase I Radiation Treatment Modality [1506] and Phase I Radiation External Beam Planning Tech [1502] is to clarify this information and implement mutually exclusive categories. A separate data item for delivery technique has not been implemented because this information is not consistently reported in end treatment summaries.A,C,I,MTreatment-1st CourseRCCoC182018
1503Phase I Number of Fractionsphase1NumberOfFractions3Records the total number of fractions (treatment sessions) delivered to the patient in the first phase of radiation during the first course of treatment. This data item is required for CoC-accredited facilities as of 01/01/2018.000-999.RdigitsRight justified, zero filled.Tumor Radiation therapy is delivered in one or more phases with each phase spread out over a number of fractions (treatment sessions). It is necessary to capture information describing the number of fraction(s) to evaluate patterns of radiation oncology care.A,C,I,MTreatment-1st CourseR*CoC182018
1504Phase I Radiation Primary Treatment Volumephase1RadiationPrimaryTxVolume2Identifies the primary treatment volume or primary anatomic target treated during the first phase of radiation therapy during the first course of treatment. This data item is required for CoC-accredited facilities as of 01/01/2018.00-07, 09-14, 20-26, 29-32, 39-42, 50-68, 70-73, 80-86, 88, 90-99.Rtext.TumorRadiation treatment is commonly delivered in one or more phases. Typically, in each phase, the primary tumor or tumor bed is treated. This data item should be used to indicate the primary target volume, which might include the primary tumor or tumor bed. If the primary tumor was not targeted, record the other regional or distant site that was targeted. Draining lymph nodes may also be targeted during the first phase. These will be identified in a separate data item Phase I Radiation to Draining Lymph Nodes \[1505\].   This data item provides information describing the anatomical structure targeted by radiation therapy during the first phase of radiation treatment and can be used to determine whether the site of the primary diseases was treated with radiation or if other regional or distant sites were targeted. This information is useful in evaluating the patterns of care within a facility and on a regional or national basis. The breakdown and reorganization of the sites will allow for concise reporting.A,C,I,MTreatment-1st CourseR*CoC182018
1505Phase I Radiation to Draining Lymph Nodesphase1RadiationToDrainingLN2Identifies the draining lymph nodes treated (if any) during the first phase of radiation therapy delivered to the patient during the first course of treatment. This data item is required for CoC-accredited facilities as of 01/01/2018.00-08, 88, 99.Rdigits.TumorThe first phase of radiation treatment commonly targets both the primary tumor (or tumor bed) and draining lymph nodes as a secondary site. This data item should be used to indicate the draining regional lymph nodes, if any, that were irradiated during the first phase of radiation.A,C,I,MTreatment-1st CourseR*CoC182018
1506Phase I Radiation Treatment Modalityphase1RadiationTreatmentModality2Identifies the radiation modality administered during the first phase of radiation treatment delivered as part of the first course of treatment. This data item is required for CoC-accredited facilities as of 01/01/2018.00-16, 98, 99.RdigitsRTumorRadiation modality reflects whether a treatment was external beam, brachytherapy, a radioisotope as well as their major subtypes, or a combination of modalities. This data item should be used to indicate the radiation modality administered during the first phase of radiation. Historically, the previously-named Regional Treatment Modality data item [1570] utilized codes that were not mutually exclusive. Rather, it included codes describing a mix of modalities, treatment planning techniques, and delivery techniques that are commonly utilized by radiation oncologists. However, every phase of radiation treatment will include a specific modality, planning technique, and delivery technique. The goal of the 2018 implementation of separate phase-specific data items for the recording of radiation modality and radiation treatment planning techniques is to clarify this information and implement mutually exclusive categories. A separate data item for delivery technique has not been implemented because this information is not consistently reported in end treatment summaries.A,C,I,MTreatment-1st CourseRCoC182018
1507Phase I Total Dosephase1TotalDose6Identifies the total radiation dose delivered to the patient in the first phase of radiation treatment during the first course of treatment. The unit of measure is centiGray (cGy). This data item is required for CoC-accredited facilities as of 01/01/2018.000000-999999.RdigitsRight Justified, zero filled.TumorTo evaluate the patterns of radiation care, it is necessary to capture information describing the prescribed dose of Phase I radiation to the patient during the first course of treatment. Outcomes are strongly related to the total dose delivered.A,C,I,MTreatment-1st CourseR*CoC182018
1511Phase II Dose per Fractionphase2DosePerFraction5Records the dose per fraction (treatment session) delivered to the patient in the second phase of radiation during the first course of treatment. The unit of measure is centiGray (cGy). This data item is required for CoC-accredited facilities for cases diagnosed as of 01/01/2018.00000-99999.RBlanks allowed if no Phase II radiation treatment administered.digits.TumorRadiation therapy is delivered in one or more phases with identified dose per fraction. It is necessary to capture information describing the dose per fraction to evaluate patterns of radiation oncology care. Outcomes are strongly related to the dose delivered.A,C,I,MTreatment-1st CourseR*CoC182018
1512Phase II Radiation External Beam Planning Techphase2RadiationExternalBeamTech2Identifies the external beam radiation planning technique used to administer the second phase of radiation treatment during the first course of treatment. This data item is required for CoC-accredited facilities for cases diagnosed as of 01/01/2018.00-10, 88, 98, 99.RBlanks allowed if no Phase II radiation treatment administered.digits.TumorExternal beam radiation is the most commonly-used radiation modality in North America. In this data item we specified the planning technique for external beam treatment. Identifying the radiation technique is of interest for patterns of care and comparative effectiveness studies. Historically, the previously-named Rad--Boost RX Modality [3200] utilized codes that were not mutually exclusive. Rather, it included codes describing a mix of modalities, treatment planning techniques, and delivery techniques that are commonly utilized by radiation oncologists. However, every phase of radiation treatment will include a specified modality, planning technique, and delivery technique. The goal of the 2018 implementation of separate phase-specific data items for the recording of Phase II Radiation Treatment Modality [1516] and Phase II Radiation External Beam Planning Tech [1512] is to clarify this information and implement mutually exclusive categories. A separate data item for delivery technique has not been implemented because this information is not consistently reported in end treatment summaries.A,C,I,MTreatment-1st CourseRCCoC182018
1513Phase II Number of Fractionsphase2NumberOfFractions3Records the total number of fractions (treatment sessions) administered to the patient in the second phase of radiation during the first course of treatment. This data item is required for CoC-accredited facilities for cases diagnosed as of 01/01/2018.000-999.RBlanks allowed if no Phase II radiation treatment administered.digitsRight justified, zero filled.TumorRadiation therapy is delivered in one or more phases with each phase spread out over a number of fractions (treatment sessions). It is necessary to capture information describing the number of fraction(s) to evaluate patterns of radiation oncology care.A,C,I,MTreatment-1st CourseR*CoC182018
1514Phase II Radiation Primary Treatment Volumephase2RadiationPrimaryTxVolume2Identifies the primary treatment volume or primary anatomic target treated during the second phase of radiation therapy during the first course of treatment. This data item is required for CoC-accredited facilities as of cases diagnosed 01/01/2018.00-07, 09-14, 20-26, 29-32, 39-42, 50-68, 70-73, 80-86, 88, 90-99.Rdigits.TumorRadiation treatment is commonly delivered in one or more phases. Typically, in each phase, the primary tumor or tumor bed is treated. This data item should be used to indicate the primary target volume, which might include the primary tumor or tumor bed. If the primary tumor was not targeted, record the other regional or distant site that was targeted. Draining lymph nodes may also be targeted during the second phase. These will be identified in a separate data item Phase II Radiation to Draining Lymph Nodes \[1515\]. This data item provides information describing the anatomical structure targeted by radiation therapy during the second phase of radiation treatment and can be used to determine whether the site of the primary diseases was treated with radiation or if other regional or distant sites were targeted. This information is useful in evaluating the patterns of care within a facility and on a regional or national basis. The breakdown and reorganization of the sites will allow for concise reporting.A,C,I,MTreatment-1st CourseR*CoC182018
1515Phase II Radiation to Draining Lymph Nodesphase2RadiationToDrainingLN2Identifies the draining lymph nodes treated (if any) during the second phase of radiation therapy delivered to the patient during the first course of treatment. This data item is required for CoC-accredited facilities as of cases diagnosed 01/01/2018.00-08, 88, 99.RBlanks allowed if no Phase II radiation treatment administered.digits.TumorThe second phase of radiation treatment commonly targets both the primary tumor (or tumor bed) and draining lymph nodes as a secondary site. This data item should be used to indicate the draining regional lymph nodes, if any, that were irradiated during the second phase of radiation.A,C,I,MTreatment-1st CourseR*CoC182018
1516Phase II Radiation Treatment Modalityphase2RadiationTreatmentModality2Identifies the radiation modality administered during the second phase of radiation treatment delivered during the first course of treatment. This data item is required for CoC-accredited facilities as of 01/01/2018.00-16, 98, 99.RBlanks allowed if no Phase II radiation treatment administered.digits.TumorRadiation modality reflects whether a treatment was external beam, brachytherapy, a radioisotope as well as their major subtypes, or a combination of modalities. This data item should be used to indicate the radiation modality administered during the second phase of radiation. Historically, the previously-named Radiation Treatment Modality data item [1570] utilized codes that were not mutually exclusive. Rather, it included codes describing a mix of modalities, treatment planning techniques, and delivery techniques that are commonly utilized by radiation oncologists. However, every phase of radiation treatment will include a specified modality, planning technique, and delivery technique. The goal of the 2018 implementation of separate phase-specific data items for the recording of radiation modality and radiation treatment planning techniques is to clarify this information and implement mutually exclusive categories. A separate data item for delivery technique has not been implemented because this information is not consistently reported in end treatment summaries.A,C,I,MTreatment-1st CourseRCoC182018
1517Phase II Total Dosephase2TotalDose6Identifies the total radiation dose administered in the second phase of radiation treatment delivered to the patient during the first course of treatment. The unit of measure is centiGray (cGy). This data item is required for CoC-accredited facilities for cases diagnosed as of 01/01/2018.000000-999999.RBlanks allowed if no Phase II radiation treatment administered.digitsRight justified, zero filled.TumorTo evaluate the patterns of radiation care, it is necessary to capture information describing the prescribed dose of Phase II radiation to the patient during the first course of treatment. Outcomes are strongly related to the total dose delivered.A,C,I,MTreatment-1st CourseR*CoC182018
1521Phase III Dose per Fractionphase3DosePerFraction5Records the dose per fraction (treatment session) delivered to the patient in the third phase of radiation during the first course of treatment. The unit of measure is centiGray (cGy). This data item is required for CoC-accredited facilities for cases diagnosed as of 01/01/2018.00000-99999.RBlanks allowed if no Phase III radiation treatment administered.digits.TumorRadiation therapy is delivered in one or more phases with identified dose per fraction. It is necessary to capture information describing the dose per fraction to evaluate patterns of radiation oncology care. Outcomes are strongly related to the dose delivered.A,C,I,MTreatment-1st CourseR*CoC182018
1522Phase III Radiation External Beam Planning Techphase3RadiationExternalBeamTech2Identifies the external beam radiation planning technique used to administer the third phase of radiation treatment during the first course of treatment. This data item is required for CoC-accredited facilities for cases diagnosed as of 01/01/2018.00-10, 88, 98, 99.RBlanks allowed if no Phase III radiation treatment administered.digits.TumorExternal beam radiation is the most commonly-used radiation modality in North America. In this data item we specified the planning technique for external beam treatment. Identifying the radiation technique is of interest for patterns of care and comparative effectiveness studies. Historically, the previously-name Regional Treatment Modality data item [1570] utilized codes that were not mutually exclusive. Rather, it included codes describing a mix of modalities, treatment planning techniques, and delivery techniques that are commonly utilized by radiation oncologists. However, every phase of radiation treatment will include a specified modality, planning technique, and delivery technique. The goal of the 2018 implementation of separate phase-specific data items for the recording of Phase III Radiation Treatment Modality [1526] and Phase III Radiation External Beam Planning Tech [1522] is to clarify this information and implement mutually exclusive categories. A separate data item for delivery technique has not been implemented because this information is not consistently reported in end treatment summaries.A,C,I,MTreatment-1st CourseRCCoC182018
1523Phase III Number of Fractionsphase3NumberOfFractions3Records the total number of fractions (treatment sessions) delivered to the patient in the third phase of radiation during the first course of treatment. This data item is required for CoC-accredited facilities for cases diagnosed as of 01/01/2018.000-999.RBlanks allowed if no Phase III radiation treatment administered.digitsRight-justified, zero-filled.TumorRadiation therapy is delivered in one or more phases with each phase spread out over a number of fractions (treatment sessions). It is necessary to capture information describing the number of fraction(s) to evaluate patterns of radiation oncology care.A,C,I,MTreatment-1st CourseR*CoC182018
1524Phase III Radiation Primary Treatment Volumephase3RadiationPrimaryTxVolume2Identifies the primary treatment volume or primary anatomic target treated during the third phase of radiation therapy during the first course of treatment. This data item is required for CoC-accredited facilities for cases diagnosed as of 01/01/2018.00-07, 09-14, 20-26, 29-32, 39-42, 50-68, 70-73, 80-86, 88, 90-96, 98-99.Rdigits.TumorRadiation treatment is commonly delivered in one or more phases. Typically, in each phase, the primary tumor or tumor bed is treated. This data item should be used to indicate the primary target volume, which might include the primary tumor or tumor bed. If the primary tumor was not targeted, record the other regional or distant site that was targeted. Draining lymph nodes may also be targeted during the first phase. These will be identified in a separate data item Phase III Radiation to Draining Lymph Nodes \[1525\].   This data item provides information describing the anatomical structure targeted by radiation therapy during the third phase of radiation treatment and can be used to determine whether the site of the primary diseases was treated with radiation or if other regional or distant sites were targeted. This information is useful in evaluating the patterns of care within a facility and on a regional or national basis. The breakdown and reorganization of the sites will allow for concise reporting.A,C,I,MTreatment-1st CourseR*CoC182018
1525Phase III Radiation to Draining Lymph Nodesphase3RadiationToDrainingLN2Identifies the draining lymph nodes treated (if any) during the third phase of radiation therapy delivered to the patient during the first course of treatment. This data item is required for CoC-accredited facilities as of cases diagnosed 01/01/2018.00-08, 88, 99.RBlanks allowed if no Phase III radiation treatment administered.digits.TumorThe third phase of radiation treatment commonly targets both the primary tumor (or tumor bed) and draining lymph nodes as a secondary site. This data item should be used to indicate the draining regional lymph nodes, if any, that were irradiated during the third phase of radiation.A,C,I,MTreatment-1st CourseR*CoC182018
1526Phase III Radiation Treatment Modalityphase3RadiationTreatmentModality2Radiation modality reflects whether a treatment was external beam, brachytherapy, a radioisotope as well as their major subtypes, or a combination of modalities. This data item should be used to indicate the radiation modality administered during the third phase of radiation. This data item is required for CoC-accredited facilities for cases diagnosed as of 01/01/2018.00-16, 98, 99.RBlanks allowed if no Phase III radiation treatment administered.digits.TumorRadiation modality reflects whether a treatment was external beam, brachytherapy, a radioisotope as well as their major subtypes, or a combination of modalities. This data item should be used to indicate the radiation modality administered during the third phase of radiation. Historically, the previously-name Radiation Treatment Modality data item [1570] utilized codes that were not mutually exclusive. Rather, it included codes describing a mix of modalities, treatment planning techniques, and delivery techniques that are commonly utilized by radiation oncologists. However, every phase of radiation treatment will include a specified modality, planning technique, and delivery technique. The goal of the 2018 implementation of separate phase-specific data items for the recording of radiation modality and radiation treatment planning techniques is to clarify this information and implement mutually exclusive categories. A separate data item for delivery technique has not been implemented because this information is not consistently reported in end treatment summaries.A,C,I,MTreatment-1st CourseRCoC182018
1527Phase III Total Dosephase3TotalDose6Identifies the total radiation dose delivered during the third phase of radiation treatment delivered to the patient during the first course of treatment. The unit of measure is centiGray (cGy). This data item is required for CoC-accredited facilities for cases diagnosed as of 01/01/2018.000000-999999.RBlanks allowed if no Phase III radiation treatment administered.digitsright justified, zero filled.TumorTo evaluate the patterns of radiation care, it is necessary to capture information describing the prescribed dose of Phase III radiation to the patient during the first course of treatment. Outcomes are strongly related to the total dose delivered.A,C,I,MTreatment-1st CourseR*CoC182018
1531Radiation Treatment Discontinued EarlyradiationTxDiscontinuedEarly2This field is used to identify patients/tumors whose radiation treatment course was discontinued earlier than initially planned. That is the patients/tumors received fewer treatment fractions (sessions) than originally intended by the treating physician. This data item is required for CoC-accredited facilities as of cases diagnosed 01/01/2018 and later.00-07, 99.Rdigits.TumorCurrently, the total dose of radiation reflects what was actually delivered rather than what was intended. When a patient doesn’t complete a radiation course as initially intended this is typically commented on within the radiation end of treatment summary. By flagging these patients within the cancer registry database, these patients can be excluded from analyses attempting to describe adherence to radiation treatment guidelines or patterns of care analyses.A,C,I,MTreatment-1st CourseR*CoC182018
1532Number of Phases of Rad Treatment to this VolumenumberPhasesOfRadTxToVolume2Identifies the total number of phases administered to the patient during the first course of treatment. A “phase” consists of one or more consecutive treatments delivered to the same anatomic volume with no change in the treatment technique. Although the majority of courses of radiation therapy are completed in one or two phases (historically, the “regional” and “boost” treatments) there are occasions in which three or more phases are used, most typically with head and neck malignancies. This data item is required for CoC-accredited facilities as of cases diagnosed 01/01/2018 and later.00, 01, 02, 03, 04, 99 .Rdigitsright justified, zero-filled.TumorThe number of phases of radiation treatment is used to evaluate patterns of radiation therapy and the treatment schedule.A,C,I,MTreatment-1st CourseR*CoC182018
1533Total DosetotalDose6Identifies the total radiation dose administered to the patient across all phases during the first course of treatment. The unit of measure is centiGray (cGy). This data item is required for CoC-accredited facilities as of cases diagnosed 01/01/2018 and later.000000-999999.To evaluate the patterns of radiation care, it is necessary to capture information describing the prescribed total dose of radiation during the first course of treatment. Outcomes are strongly related to the dose delivered.Rdigitsright justified, zero filled.TumorA,C,I,MTreatment-1st CourseR*CoC182018
1550Rad--Location of RXradLocationOfRx1Identifies the location of the facility where radiation treatment was administered during first course of treatment. See also RX Summ--Radiation \[1360\].0-4, 8, 9Location of Radiation Treatment (CoC).Rdigits.TumorA,C,I,MTreatment-1st Course.CoC
1570Rad--Regional RX ModalityradRegionalRxModality2Records the dominant modality of radiation therapy used to deliver the clinically most significant regional dose to the primary volume of interest during the first course of treatment.00, 20-32, 40-43, 50-55, 60-62, 80, 85, 98, 99Regional Treatment Modality (CoC)..*Note:* For tumors diagnosed prior to January 1, 2003, the codes reported in this data item describe any radiation administered to the patient as part or all of the first course of therapy. \*Codes 80 and 85 describe specific converted descriptions of radiation therapy coded according to *Volume II ROADS*, and *DAM* rules and should only be used to record regional radiation for tumors diagnosed prior to January 1, 2003. digitsRight justified, zero filledRHTumorRadiation treatment frequently is delivered in two or more phases that can be summarized as regional and boost treatments. To evaluate patterns of radiation oncology care, it is necessary to know which radiation resources were employed in the delivery of therapy. For outcomes analysis, the modalities used for each of these phases can be very important.A,C,I,MTreatment-1st Course.CoC
1632Neoadjuvant TherapyneoadjuvantTherapy1This data item records whether the patient had neoadjuvant therapy prior to planned definitive surgical resection of the primary site.0-3, 9..text.TumorThis data items provides information related to the quality of care and describes whether a patient had neoadjuvant therapy. For the purposes of this data item, neoadjuvant therapy is defined as systemic treatment (chemotherapy, endocrine / hormone therapy, targeted therapy, immunotherapy, or biological therapy) and/or radiation therapy before intended or performed surgical resection to improve local therapy and long term outcomes.A,C,I,MTreatment-1st CourseRSEER212021
1633Neoadjuvant Therapy-Clinical ResponseneoadjuvTherapyClinicalResponse1This data item records the clinical outcomes of neoadjuvant therapy prior to planned surgical resection.0-9..text.TumorThis data items provides information related to the quality of care and describes the clinical outcomes after neoadjuvant therapy. This data item provides prognostically relevant information by quantifying the extent of therapy-induced tumor regression. Therefore, this item can provide a better risk stratification for patients who received neoadjuvant therapy. In addition, this data item can contribute to assessments of cancer care quality. This data item records the clinical outcomes of neoadjuvant therapy as determined by the managing physician (oncologic surgeon, radiation oncologist or medical oncologist). For the purposes of this data item, neoadjuvant therapy is defined as systemic treatment (chemotherapy, endocrine / hormone therapy, targeted therapy, immunotherapy, or biological therapy) and/or radiation therapy given to shrink a tumor before surgical resection.A,C,I,MTreatment-1st CourseRSEER212021
1634Neoadjuvant Therapy-Treatment EffectneoadjuvTherapyTreatmentEffect1This data item records the pathologist’s statement of neoadjuvant treatment effect on the primary tumor from the surgical pathology report. Whenever treatment effect definitions are recommended by or available in CAP Cancer Protocols, this data item follows the CAP definitions indicating absent or present effect. When specific CAP definitions are not available, registrars should use treatment effect general use categories.0-4, 6, 7, 9..text.TumorThis data item provides information related to the quality of care and describes the pathological outcomes after neoadjuvant therapy. This data item provides prognostically relevant information by quantifying the extent of therapy-induced tumor regression. Therefore, this item can provide a better risk stratification for patients who received neoadjuvant therapy. In addition, this data item can contribute to assessments of cancer care quality.A,C,I,MTreatment-1st CourseRSEER212021
1639RX Summ--Systemic/Sur SeqrxSummSystemicSurSeq1Records the sequencing of systemic therapy (RX Summ-Chemo [1390], RX Summ-Hormone [1400], RX Summ-BRM [1410], and RX Summ-Transplnt/Endocr [3250]) and surgical procedures given as part of the first course of treatment. See also RX Summ--Surg Prim Site [1290], RX Summ--Scope LN Surg [1292], and RX Summ--Surg Oth Reg/Dis [1294].0, 2-7, 9Systemic/Surgery Sequence.RdigitsRTumorThe sequence of systemic therapy and surgical procedures given as part of the first course of treatment cannot always be determined using the date on which each modality was started or performed. This data item can be used to more precisely evaluate the time of delivery of treatment to the patient.A,C,I,MTreatment-1st CourseRCoC112006
1640RX Summ--Surgery TyperxSummSurgeryType2Field for pre-1996 surgery codes for CoC and pre-1998 surgery codes for SEER. Surgery codes used 1998 and later can be backward converted into the older codes and the converted value can be stored in this field. See Chapter V, Unresolved Issues, for discussion of CoC/SEER differences in coding treatment.00-99 (site-specific)Site--Specific Surgery (pre-98 SEER)..digitsRight justified, zero filled.TumorA,C,I,MTreatment-1st CourseRHSEER12.22011
1646RX Summ--Surg Site 98-02rxSummSurgSite98022Site-specific codes for the type of surgery to the primary site performed as part of the first course of treatment. This includes treatment given at all facilities as part of the first course of treatment. This field is to be used for *ROADS* codes after the *ROADS* to *FORDS* conversion. It is also to be used to code Surgery Primary Site at all facilities for all tumors diagnosed before January 1, 2003.00, 10-90, 99 (site-specific), blankCancer-Directed Surgery (pre-96 CoC), Surgery of Primary Site (SEER/CoC).RH*Note:* See the CoC *ROADS Manual*, 1998 Supplement, CoC Coding System [2140] code 7, and the *SEER Program Code Manual*, RX Coding System [1460] code 5, 1998 for site-specific codes.digitsRight justified, zero filledIn addition to the site-specific codes.TumorIf central registries wish to study the treatment given at particular hospitals, the hospital-level treatment fields must be used.A,C,I,MTreatment-1st Course.SEER/CoC
1647RX Summ--Scope Reg 98-02rxSummScopeReg98021Describes the removal, biopsy or aspiration of regional lymph node(s) at the time of surgery of the primary site or during a separate surgical event at all facilities. This field is to be used for *ROADS* codes after the *ROADS* to *FORDS* conversion. It is also to be used to code Scope of Regional Lymph Node Surgery at all facilities for all tumors diagnosed before January 1, 2003.0-9 (site-specific), blankScope of Regional Lymph Node Surgery (SEER/CoC).RHdigitsSee the CoC *ROADS* Manual 1998 Supplement and the *SEER Program Code Manual* for site-specific codes..TumorIn evaluating quality of care and treatment practices it is important to identify the removal, biopsy, or aspiration of regional lymph node(s) at the time of surgery of the primary site or during a separate surgical event.A,C,I,MTreatment-1st CourseRHSEER/CoC
1648RX Summ--Surg Oth 98-02rxSummSurgOth98021Records the surgical removal of distant lymph nodes or other tissue(s)/organ(s) beyond the primary site given at all facilities as part of the first course of treatment. This field is to be used for *ROADS* codes after the *ROADS* to *FORDS* conversion. It is also to be used to code Surgery Regional/Distant Sites at all facilities for all tumors diagnosed before January 1, 2003.0-9 (site-specific), blankSurgery of Other Regional Site(s), Distant Site(s) or Distant Lymph Nodes (SEER/CoC), Surgical Procedure/Other Site.RHdigitsSee the CoC ROADS Manual 1998 Supplement and the SEER Program Code Manual for site-specific codes..TumorThe removal of non-primary tissue documents the extent of surgical treatment and is useful in evaluating the extent of metastatic involvement.A,C,I,MTreatment-1st CourseRHSEER/CoC
1660Subsq RX 2nd Course DatesubsqRx2ndCourseDate8Date of initiation of second-course treatment. Central registries currently collecting this data item should follow the _1998 ROADS Manual_ coding instructions. See [**Data Descriptor Table**](https://apps.naaccr.org/data-dictionary/data-dictionary/version=24/chapter-view/data-descriptor-table/) for date format.Valid datesSecond Course of Therapy-Date Started (pre-96 CoC)..dateYYYYMMDD_Note:_ This data item is no longer supported by CoC (as of January 1, 2003)..TumorA,C,I,MTreatment-Subsequent & Other.CoC
1671Subsq RX 2nd Course SurgsubsqRx2ndCourseSurg2Codes for the type of primary site surgery given as part of the second course of treatment. Central registries currently collecting this data item should follow the *1998 ROADS Manual* coding instructions. The codes are the same as those for Surgery of Primary Site, *1998 ROADS Manual*, p. 187.00, 10-90, 99..digitsRight justified, zero filled*Note:* This data item is no longer supported by CoC (as of January 1, 2003)..TumorA,C,I,MTreatment-Subsequent & Other.CoC12.22011
1672Subsq RX 2nd Course RadsubsqRx2ndCourseRad1Codes for the type of radiation given as part of the second course of treatment. Central registries currently collecting this data item should follow the *1998 ROADS Manual* coding instructions. The codes are the same as those for Radiation, *1998 ROADS Manual*, p. 199.0-5, 9..digits*Note:* This data item is no longer supported by CoC (as of January 1, 2003)..TumorA,C,I,MTreatment-Subsequent & Other.CoC12.22011
1673Subsq RX 2nd Course ChemosubsqRx2ndCourseChemo1Codes for the type of chemotherapy given as part of the second course of treatment. Central registries currently collecting this data item should follow the *1998 ROADS Manual* coding instructions. The codes are the same as those for Chemotherapy, *1998 ROADS Manual*, p. 228.0-3, 9..digits*Note:* This data item is no longer supported by CoC (as of January 1, 2003)..TumorA,C,I,MTreatment-Subsequent & Other.CoC12.22011
1674Subsq RX 2nd Course HormsubsqRx2ndCourseHorm1Codes for the type of hormonal therapy given as part of the second course of treatment. Central registries currently collecting this data item should follow the *1998 ROADS Manual* coding instructions. The codes are the same as those for Hormone Therapy, *1998 ROADS Manual*, p. 238.0-3, 9..digits*Note:* This data item is no longer supported by CoC (as of January 1, 2003)..TumorA,C,I,MTreatment-Subsequent & Other.CoC
1675Subsq RX 2nd Course BRMsubsqRx2ndCourseBrm1Codes for the type of biological response modifier therapy given as part of the second course of treatment. Central registries currently collecting this data item should follow the *1998 ROADS Manual* coding instructions. The codes are the same as those for Immunotherapy, *1998 ROADS Manual*, p. 243.0-9..digits*Note:* This data item is no longer supported by CoC (as of January 1, 2003)..TumorA,C,I,MTreatment-Subsequent & Other.CoC12.22011
1676Subsq RX 2nd Course OthsubsqRx2ndCourseOth1Codes for the type of other treatment given as part of the second course of treatment. Central registries currently collecting this data item should follow the *1998 ROADS Manual* coding instructions. The codes are the same as those for Other Treatment, *1998 ROADS Manual*, p. 246.0-3, 6-9..digits*Note:* This data item is no longer supported by CoC (as of January 1, 2003)..TumorA,C,I,MTreatment-Subsequent & Other.CoC12.22011
1677Subsq RX 2nd--Scope LN SUsubsqRx2ndScopeLnSu1Codes for the type of surgery performed to remove regional lymph nodes as part of the second course of treatment. Central registries currently collecting this data item should follow the *1998 ROADS Manual* coding instructions. The codes are the same as those for Scope of Regional Lymph Node Surgery, *1998 ROADS Manual*, p. 192. 0-9..digits*Note:* This data item is no longer supported by CoC (as of January 1, 2003)..TumorA,C,I,MTreatment-Subsequent & Other.CoC5.11997
1678Subsq RX 2nd--Surg OthsubsqRx2ndSurgOth1Codes for the type of surgery performed on tissue or organs other than the primary site and regional lymph nodes as part of the second course of treatment. Central registries currently collecting this data item should follow the *1998 ROADS Manual* coding instructions. The codes are the same as those for Surgery of Other Regional Site(s), Distant Site(s) or Distant Lymph Node(s), *1998 ROADS Manual*, p. 194.0-9..digits*Note:* This data item is no longer supported by CoC (as of January 1, 2003)..TumorA,C,I,MTreatment-Subsequent & Other.CoC5.11997
1679Subsq RX 2nd--Reg LN RemsubsqRx2ndRegLnRem2Codes for the number of regional lymph nodes removed as part of the second course of treatment. Central registries currently collecting this data item should follow the *1998 ROADS Manual* coding instructions. The codes are the same as those for Number of Regional Lymph Nodes Removed, *1998 ROADS Manual*, p. 193.00-90, 95-99..digitsRight justified, zero filled*Note:* This data item is no longer supported by CoC (as of January 1, 2003)..TumorA,C,I,MTreatment-Subsequent & Other.CoC5.11997
1680Subsq RX 3rd Course DatesubsqRx3rdCourseDate8Date of initiation of third course of treatment. Central registries currently collecting this data item should follow the _1998 ROADS Manual_ coding instructions. See [**Data Descriptor Table**](https://apps.naaccr.org/data-dictionary/data-dictionary/version=24/chapter-view/data-descriptor-table/) for date format.Valid dates..dateYYYYMMDD.TumorA,C,I,MTreatment-Subsequent & Other.CoC
1691Subsq RX 3rd Course SurgsubsqRx3rdCourseSurg2Codes for the type of primary site surgery given as part of the third course of treatment. Central registries currently collecting this data item should follow the *1998 ROADS Manual* coding instructions. The codes are the same as those for Surgery of Primary Site, *1998 ROADS Manual*, p. 187.00, 10-90, 99..digitsRight justified, zero filled*Note:* This data item is no longer supported by CoC (as of January 1, 2003)..TumorA,C,I,MTreatment-Subsequent & Other.CoC12.22011
1692Subsq RX 3rd Course RadsubsqRx3rdCourseRad1Codes for the type of radiation given as part of the third course of treatment. Central registries currently collecting this data item should follow the *1998 ROADS Manual* coding instructions. The codes are the same as those for Radiation, *1998 ROADS Manual*, p. 199.0-5, 9..digits*Note:* This data item is no longer supported by CoC (as of January 1, 2003)..TumorA,C,I,MTreatment-Subsequent & Other.CoC12.22011
1693Subsq RX 3rd Course ChemosubsqRx3rdCourseChemo1Codes for the type of chemotherapy given as part of the third course of treatment. Central registries currently collecting this data item should follow the *1998 ROADS Manual* coding instructions. The codes are the same as those for Chemotherapy, *1998 ROADS Manual*, p. 228.0-3, 9..digits*Note:* This data item is no longer supported by CoC (as of January 1, 2003)..TumorA,C,I,MTreatment-Subsequent & Other.CoC12.22011
1694Subsq RX 3rd Course HormsubsqRx3rdCourseHorm1Codes for the type of hormonal therapy given as part of the third course of treatment. Central registries currently collecting this data item should follow the *1998 ROADS Manual* coding instructions. The codes are the same as those for Hormone Therapy, *1998 ROADS Manual*, p. 238.0-3, 9..digits*Note:* This data item is no longer supported by CoC (as of January 1, 2003)..TumorA,C,I,MTreatment-Subsequent & Other.CoC12.22011
1695Subsq RX 3rd Course BRMsubsqRx3rdCourseBrm1Codes for the type of biological response modifier therapy given as part of the second course of treatment. Central registries currently collecting this data item should follow the *1998 ROADS Manual* coding instructions. The codes are the same as those for Immunotherapy, *1998 ROADS Manual*, p. 2430-9..digits*Note:* This data item is no longer supported by CoC (as of January 1, 2003)..TumorA,C,I,MTreatment-Subsequent & Other.CoC12.22011
1696Subsq RX 3rd Course OthsubsqRx3rdCourseOth1Codes for the type of other treatment given as part of the third course of treatment. Central registries currently collecting this data item should follow the *1998 ROADS Manual* coding instructions. The codes are the same as those for Other Treatment, *1998 ROADS Manual*, p. 246.0-3, 6-9..digits*Note:* This data item is no longer supported by CoC (as of January 1, 2003)..TumorA,C,I,MTreatment-Subsequent & Other.CoC12.22011
1697Subsq RX 3rd--Scope LN SusubsqRx3rdScopeLnSu1Codes for the type of surgery performed to remove regional lymph nodes as part of the third course of treatment. Central registries currently collecting this data item should follow the *1998 ROADS Manual* coding instructions. The codes are the same as those for Scope of Regional Lymph Node Surgery, *1998 ROADS Manual*, p. 192.0-9..digits*Note:* This data item is no longer supported by CoC (as of January 1, 2003)..TumorA,C,I,MTreatment-Subsequent & Other.CoC5.11997
1698Subsq RX 3rd--Surg OthsubsqRx3rdSurgOth1Codes for the type of surgery performed on tissue or organs other than the primary site and regional lymph nodes as part of the third course of treatment. Central registries currently collecting this data item should follow the *1998 ROADS Manual* coding instructions. The codes are the same as those for Surgery of Other Regional Site(s), Distant Site(s) or Distant Lymph Node(s), *1998 ROADS Manual*, p. 194.0-9..digits*Note:* This data item is no longer supported by CoC (as of January 1, 2003)..TumorA,C,I,MTreatment-Subsequent & Other.CoC5.11997
1699Subsq RX 3rd--Reg LN RemsubsqRx3rdRegLnRem2Codes for the number of regional lymph nodes removed as part of the third course of treatment. Central registries currently collecting this data item should follow the *1998 ROADS Manual* coding instructions. The codes are the same as those for Number of Regional Lymph Nodes Removed, *1998 ROADS Manual*, p. 193.00-90, 95-99..digitsRight justified, zero filled*Note:* This data item is no longer supported by CoC (as of January 1, 2003)..TumorA,C,I,MTreatment-Subsequent & Other.CoC5.11997
1700Subsq RX 4th Course DatesubsqRx4thCourseDate8Date of initiation of the fourth course of treatment. Central registries currently collecting this data item should follow the _1998 ROADS Manual_ coding instructions. See [**Data Descriptor Table**](https://apps.naaccr.org/data-dictionary/data-dictionary/version=24/chapter-view/data-descriptor-table/) for date format.Valid dates..dateYYYYMMDD.TumorA,C,I,MTreatment-Subsequent & Other.CoC
1711Subsq RX 4th Course SurgsubsqRx4thCourseSurg2Codes for the type of primary site surgery given as part of the fourth course of treatment. Central registries currently collecting this data item should follow the *1998 ROADS Manual* coding instructions. The codes are the same as those for Surgery of Primary Site, *1998 ROADS Manual*, p. 187.00, 10-90, 99..digitsRight justified, zero filled*Note:* This data item is no longer supported by CoC (as of January 1, 2003)..TumorA,C,I,MTreatment-Subsequent & Other.CoC12.22011
1712Subsq RX 4th Course RadsubsqRx4thCourseRad1Codes for the type of radiation given as part of the fourth course of treatment. Central registries currently collecting this data item should follow the *1998 ROADS Manual* coding instructions. The codes are the same as those for Radiation, *1998 ROADS Manual*, p. 199.0-5, 9..digits*Note:* This data item is no longer supported by CoC (as of January 1, 2003)..TumorA,C,I,MTreatment-Subsequent & Other.CoC12.22011
1713Subsq RX 4th Course ChemosubsqRx4thCourseChemo1Codes for the type of chemotherapy given as part of the fourth course of treatment. Central registries currently collecting this data item should follow the *1998 ROADS Manual* coding instructions. The codes are the same as those for Chemotherapy, *1998 ROADS Manual*, p. 228.0-3, 9..digits*Note:* This data item is no longer supported by CoC (as of January 1, 2003)..TumorA,C,I,MTreatment-Subsequent & Other.CoC12.22011
1714Subsq RX 4th Course HormsubsqRx4thCourseHorm1Codes for the type of hormonal therapy given as part of the fourth course of treatment. Central registries currently collecting this data item should follow the *1998 ROADS Manual* coding instructions. The codes are the same as those for Hormone Therapy, *1998 ROADS Manual*, p. 238.0-3, 9..digits*Note:* This data item is no longer supported by CoC (as of January 1, 2003)..TumorA,C,I,MTreatment-Subsequent & Other.CoC12.22011
1715Subsq RX 4th Course BRMsubsqRx4thCourseBrm1Codes for the type of biological response modifier therapy given as part of the second course of treatment. Central registries currently collecting this data item should follow the *1998 ROADS Manual* coding instructions. The codes are the same as those for Immunotherapy, *1998 ROADS Manual*, p. 2430-9..digits*Note:* This data item is no longer supported by CoC (as of January 1, 2003)..TumorA,C,I,MTreatment-Subsequent & Other.CoC12.22011
1716Subsq RX 4th Course OthsubsqRx4thCourseOth1Codes for the type of other treatment given as part of the fourth course of treatment. Central registries currently collecting this data item should follow the *1998 ROADS Manual* coding instructions. The codes are the same as those for Other Treatment, *1998 ROADS Manual*, p. 246.0-3, 6-9..digits*Note:* This data item is no longer supported by CoC (as of January 1, 2003)..TumorA,C,I,MTreatment-Subsequent & Other.CoC12.22011
1717Subsq RX 4th--Scope LN SusubsqRx4thScopeLnSu1Codes for the type of surgery performed to remove regional lymph nodes as part of the fourth course of treatment. Central registries currently collecting this data item should follow the *1998 ROADS Manual* coding instructions. The codes are the same as those for Scope of Regional Lymph Node Surgery, *1998 ROADS Manual*, p. 192.0-9..digits*Note:* This data item is no longer supported by CoC (as of January 1, 2003)..TumorA,C,I,MTreatment-Subsequent & Other.CoC5.11997
1718Subsq RX 4th--Surg OthsubsqRx4thSurgOth1Codes for the type of surgery performed on tissue or organs other than the primary site and regional lymph nodes as part of the fourth course of treatment. Central registries currently collecting this data item should follow the *1998 ROADS Manual* coding instructions. The codes are the same as those for Surgery of Other Regional Site(s), Distant Site(s) or Distant Lymph Node(s), *1998 ROADS Manual*, p. 194.0-9..digits*Note:* This data item is no longer supported by CoC (as of January 1, 2003)..TumorA,C,I,MTreatment-Subsequent & Other.CoC5.11997
1719Subsq RX 4th--Reg LN RemsubsqRx4thRegLnRem2Codes for the number of regional lymph nodes removed as part of the fourth course of treatment. Central registries currently collecting this data item should follow the *1998 ROADS Manual* coding instructions. The codes are the same as those for Number of Regional Lymph Nodes Removed, *1998 ROADS Manual*, p. 193.00-90, 95-99..digitsRight justified, zero filled*Note:* This data item is no longer supported by CoC (as of January 1, 2003)..TumorA,C,I,MTreatment-Subsequent & Other.CoC5.11997
1750Date of Last ContactdateOfLastContact8Date 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 [**Data Descriptor Table**](https://apps.naaccr.org/data-dictionary/data-dictionary/version=24/chapter-view/data-descriptor-table/) for date format.Valid datesDate of Last Contact or Death (CoC), Date of Last Follow-Up or of Death (SEER).RdateYYYYMMDDRPatientUsed for recording Date of Last Contact from active or passive follow-up. Used to record date of death and to calculate survival.A,C,I,MFollow-up/Recurrence/DeathRSEER/CoC
1755Date of Death--CanadadateOfDeathCanada8This field is used by the Canadian provinces/territories to record the patient's date of death. See [**Data Descriptor Table**](https://apps.naaccr.org/data-dictionary/data-dictionary/version=24/chapter-view/data-descriptor-table/) for date format.Valid DatesR*.dateYYYYMMDD.PatientA,C,I,MFollow-up/Recurrence/Death.CCCR11.32009
1760Vital StatusvitalStatus1Vital status of the patient as of the date entered in Date of Last Contact [1750]. If the patient has multiple tumors, vital status should be the same for all tumors.0, 1DRdigitsRPatientA,C,I,MFollow-up/Recurrence/DeathRSEER/CoC
1762Vital Status RecodevitalStatusRecode1This variables is akin to Vital Status [1760], with the exception that any patient that dies after the follow-up cut-off date is recoded to alive as of the cut-off date. This variable is used as part of the algorithm for calculating the survival time recode variables (NAACCR items 1782-1788) and is used for survival, prevalence, and multiple primary – standardized incidence ratio analyses in SEER\*Stat. This recode is necessary to conduct survival and prevalence analyses outside of SEER\*Stat using other statistical software.0, 1..digitsDPatientThese changes will benefit the cancer surveillance community by facilitating the application of standard methods for survival analysis. Beginning with data collected in the November 2014 call for data, NAACCR has published *Cancer in North America Volume 4: Cancer Survival in the United States and Canada*, which provides cancer survival estimates on a wider population than was previously available. However, at present IMS must pre-process the datasets that are included in the NAACCR survival dataset to calculate the four  standard data items, SEER Cause Specific COD [1914], SEER Other COD [1915], Record Number Recode [1775], and Vital Status Recode [1762]. For registries that do not submit cause of death information to NAACCR, it is not possible to calculate the 'SEER cause-specific death classification' or 'SEER other cause of death classification' variables. The 4 new data items will assist individual registries in performing survival analyses using their own data.A,C,I,MFollow-up/Recurrence/DeathDNAACCR182018
1770Cancer StatuscancerStatus1Records the presence or absence of clinical evidence of the patient's malignant or non-malignant tumor as of the Date of Last Cancer (tumor) Status [1772]. If the patient has multiple primaries, the values may be different for each primary. 1, 2, 9.Rdigits.TumorThis 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.A,C,I,MFollow-up/Recurrence/DeathR*CoC
1772Date of Last Cancer (tumor) Status dateOfLastCancerStatus8This data item documents the date of last cancer (tumor status) of the patient’s malignant or non-malignant tumor. Record in CCYYMMDD form, where blank spaces are used for unknown trailing portions of the date or where a date is not applicable. This data item is required for CoC-accredited facilities as of cases diagnosed 01/01/2018 and later.Valid dates.RdateYYYYMMDD.TumorThis information is used for patient follow-up and outcomes studies.A,C,I,MFollow-up/Recurrence/DeathR*CoC182018
1775Record Number RecoderecordNumberRecode2This variable sequentially numbers a person's tumors within each dataset. The ordered values are based on date of diagnosis and then sequence number central. This variable is used as part of the algorithm for calculating the survival time recode variables (NAACCR items 1782-1788) and is used for survival, prevalence, and multiple primary – standardized incidence ratio analyses in SEER\*Stat.01-99..digitsDTumorThese changes will benefit the cancer surveillance community by facilitating the application of standard methods for survival analysis. Beginning with data collected in the November 2014 call for data, NAACCR has published *Cancer in North America Volume 4: Cancer Survival in the United States and Canada*, which provides cancer survival estimates on a wider population than was previously available. However, at present IMS must pre-process the datasets that are included in the NAACCR survival dataset to calculate the four new standard data items, SEER Cause Specific COD [1914], SEER Other COD [1915], Record Number Recode [1775], and Vital Status Recode [1762]. For registries that do not submit cause of death information to NAACCR, it is not possible to calculate the 'SEER cause-specific death classification' or 'SEER other cause of death classification' variables. The 4 new data items will assist individual registries in performing survival analyses using their own data.A,C,I,MFollow-up/Recurrence/DeathDNAACCR182018
1782Surv-Date Active FollowupsurvDateActiveFollowup8The Surv-Date Active Followup is defined as the earlier of the Date of Last Contact \[1750\] and a study cutoff date. The study cut-off date is a pre-determined date based on the year of data submission and is set in the survival program used to derive the seven survival variables. If the Date of Last Contact \[1750\] is earlier than the study cut-off date and either the day or month is unknown or not available, the values are imputed by the survival program. The survival program is available from your standard setter or NAACCR. **Example 1** Date of Last Contact: 20111120 Study Cut-off Date: 20111231 Surv-Date Active Followup: 20111120 Note: The date of last contact is earlier than the study cut-off date, and the date of last contact is complete, so the date of last contact is used in Surv-Date Active Followup. **Example 2** Date of Last Contact: 201111 Study Cut-off Date: 20111231 Surv-Date Active Followup: 20111115 Note: Rationale is to take mid-point of possible values. For Nov (30 days) it would be FLOOR((1+30)/2) = 15, where FLOOR is a function that rounds a decimal down to an integer.Valid Dates..If Date of Last Contact \[1750\] is blank, Surv-Date Active Followup will also be blank.dateYYYYMMDDAdditional information about the survival algorithm and what specific values are assigned in given missing date situations are available here: \<http://seer.cancer.gov/survivaltime/\>.DTumorThe Surv-Date Active Followup is needed to be able to recalculate survival months if a different study cut-off date is used and provides flexibility to recalculate survival without needing to rerun the survival program on the original data.A,C,I,MFollow-up/Recurrence/DeathDNAACCR152015
1783Surv-Flag Active FollowupsurvFlagActiveFollowup1This flag is generated by the program that creates Surv-Mos Active Followup [1784] and describes how complete the date information is that was used to calculate survival months. This item is one of seven survival variables designed to facilitate a common approach to survival analysis by NAACCR registries.0-3, 8,9, blank..digitsDTumorThe flag will enable analysts to easily select a subset of cases.A,C,I,MFollow-up/Recurrence/DeathDNAACCR152015
1784Surv-Mos Active FollowupsurvMosActiveFollowup4The survival interval in months is calculated using the month, day, and year of the Surv-Date DX Recode \[1788\] and the month, day, and year of the Surv-Date Active Followup \[1782\]. The survival interval is calculated by a program available from your standard setter or NAACCR. **Example of a case diagnosed in 2011 and submitted in 2013.** Date of submission: 20131101 Date of diagnosis: 20110915 Date of last contact: 20111017 Vital status: Alive Study cutoff date: 20111231 20111017 would be used as the date of last contact for the survival calculation. The survival time would be 1 month.0000-9999, blank..**Calculation** Survival months = FLOOR((endpoint – date of diagnosis) / days in a month) The FLOOR function rounds a decimal down to an integer, e.g., FLOOR(1.68) = 1. Days in a month is assigned as 365.24/12.digitsRight justified, zero filledAdditional information about the algorithm and what specific values are assigned in given missing date situations are available here: \<http://seer.cancer.gov/survivaltime/\>.A value of 9999 is for missing and matches the Surv- Flag Active Followup value of 9 or blank. Leading zeros will be used when needed to left fill the fieldDTumorAccurate survival estimates are crucial for monitoring trends in population-based cancer survival and assessing the effectiveness of healthcare delivery to cancer patients. With the aim of obtaining the most precise estimates of survival, it is necessary to use complete dates (month, day, and year components) in the calculation of the survival interval. The survival interval in months is calculated using complete dates, and the algorithm imputes missing components of dates when they are not available in central registry records.A,C,I,MFollow-up/Recurrence/DeathDNAACCR152015
1785Surv-Date Presumed AlivesurvDatePresumedAlive8The Surv-Date Presumed Alive is the last date for which complete death ascertainment is available from the registry at the time a file is transmitted. Because not all central cancer registries conduct active patient follow-up, it is necessary to have an option for calculating survival times based on the assumption that the registry has ascertained all available deaths (state/province and national), and persons not known to be deceased are presumed to be alive as of the last date for which complete death ascertainment is available. This variable is set in the survival program used to derive the seven survival variables. The survival program is available from your standard setter or NAACCR. **Example 1** Vital Status: Alive Date of Last Contact: 20111120 Study Cut-off Date: 20111231 Latest date for complete death ascertainment: 20111231 Surv-Date Presumed Alive: 20111231Valid dates..dateYYYYMMDDAdditional information about the survival algorithm and what specific values are assigned in given missing date situations are available here: [http://seer.cancer.gov/survivaltime/](http://seer.cancer.gov/survivaltime/).DTumorThe Surv-Date Presumed Alive is needed to be able to recalculate survival months if a different study cut-off date is used and provides flexibility to recalculate survival without needing to rerun the survival program on the original data.A,C,I,MFollow-up/Recurrence/DeathDNAACCR152015
1786Surv-Flag Presumed AlivesurvFlagPresumedAlive1This flag is generated by the program that creates Surv-Mos Presumed Alive [1787] and describes how complete the date information is that was used to calculate survival months. This item is one of seven survival variables designed to facilitate a common approach to survival analysis by NAACCR registries.0-3, 8,9, blank..digitsDTumorThe flag will enable analysts to easily select a subset of cases.A,C,I,MFollow-up/Recurrence/DeathDNAACCR152015
1787Surv-Mos Presumed AlivesurvMosPresumedAlive4Because not all central cancer registries conduct active patient follow-up, it is necessary to have an option for calculating survival times based on the assumption that the registry has ascertained all available deaths (state/province and national), and persons not known to be deceased are presumed to be alive as of the last date for which complete death ascertainment is available. The survival interval in months is calculated using the month, day, and year of the Surv-Date DX Recode \[1788\] and the month, day, and year of the Surv-Date Presumed Alive \[1785\]. The survival program is available from your standard setter or NAACCR. **Example of a case diagnosed in 2011 and submitted in 2013.** Date of submission: 20131101 Date of diagnosis: 20110915 Date of last contact: 20111017 Latest date for complete death ascertainment: 20111231 Vital status: Alive Study cutoff date: 20111231 Under the "presumed alive" scenario, 20111231 would be used as the endpoint for the survival calculation. The presumed alive survival time would be 3 months, while the survival time using the date of last contact (assuming active follow-up) would be 1 month.0000-9999, blank..A value of 9999 is for missing and matches the Surv-Flag Presumed Alive \[1786\] value of 9 or blank. Leading zeros will be used when needed to left fill the field.digitsRight justified, zero filledAdditional information about the algorithm and what specific values are assigned in given missing date situations are available here: [http://seer.cancer.gov/survivaltime/](http://seer.cancer.gov/survivaltime/).DTumorAccurate survival estimates are crucial for monitoring trends in population-based cancer survival and assessing the effectiveness of healthcare delivery to cancer patients. With the aim of obtaining the most precise estimates of survival, it is necessary to use complete dates (month, day, and year components) in the calculation of the survival interval. The survival interval in months is calculated using complete dates, and the algorithm imputes missing components of dates when they are not available in central registry records.A,C,I,MFollow-up/Recurrence/DeathDNAACCR152015
1788Surv-Date DX RecodesurvDateDxRecode8The survival date of diagnosis recode is calculated using the month, day, and year of the Date of Diagnosis \[390\]. If the Date of Diagnosis \[390\] has complete month and day information, the Surv-Date Dx Recode will be the same as the Date of Diagnosis \[390\]. If the day or month is unknown or not available, the values are imputed by the survival program used to derive the seven survival variables. The survival program is available from your standard setter or NAACCR. **Example 1** Date of diagnosis: 20111199 Date of Last Contact: 20111120 Surv-Date of DX Recode: 20111110 Note: The recoded value is the mid-point between 11/1 and 11/20. **Example 2** Date of diagnosis: 2011 Date of Last Contact: 20111120 Surv-Date of DX Recode: 20110611 Note: The recoded value is the mid-point between 20110101 and 20111120.Valid dates..dateYYYYMMDDAdditional information about the survival algorithm and what specific values are assigned in given missing date situations are available here: [http://seer.cancer.gov/survivaltime/](http://seer.cancer.gov/survivaltime/).DTumorThe Surv-Date DX Recode is needed to be able to match to a lifetable entry to obtain expected survival. If a case is diagnosed in January 2000, the first 12 months of expected survival will be from the 2000 life table. If a case is diagnosed in December 2000, only one month will be from the 2000 life table and then the 2001 life table is used.A,C,I,MFollow-up/Recurrence/DeathDNAACCR152015
1790Follow-Up SourcefollowUpSource1Records the source from which the latest follow-up information was obtained.0-5, 7-9Follow-Up Method (pre-96 CoC).RdigitsR*TumorFor 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.A,C,I,MUpdated SEERFollow-up/Recurrence/DeathR*CoC
1791Follow-up Source CentralfollowUpSourceCentral2This 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.00-12, 29-35, 39-43, 48-51, 59-65, 98, 99..digitsRight justified, zero filledRPatientFor 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.A,C,I,MUpdated SEERFollow-up/Recurrence/DeathRNAACCR112006
1800Next Follow-Up SourcenextFollowUpSource1Identifies the method planned for the next follow-up.0-5, 8, 9Next Follow-Up Method (pre-96 CoC).Rdigits.TumorA,C,I,MFollow-up/Recurrence/Death.CoC
1810Addr Current--CityaddrCurrentCity50Name 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.City name or UNKNOWNCity/Town--Current (CoC)..textMixed case letters, special characters only as allowed by USPS, embedded spaces allowed, left justified, blank filled.Patient"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.A,C,I,MFollow-up/Recurrence/DeathRSEER
1820Addr Current--StateaddrCurrentState2USPS 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].State--Current (CoC)..alphaSee EDITS table STATE.DBF in Appendix B; CD, US, XX, YY, ZZIn addition to the U.S. and Canadian postal service abbreviations.Patient"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.A,C,I,MFollow-up/Recurrence/DeathRSEER
1830Addr Current--Postal CodeaddrCurrentPostalCode9Postal 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.5-digit or 9-digit U.S. ZIP codes; 6- character Canadian postal codes; valid postal codes from other countries, 888888888, 999999999, 88888+4 blanks (U.S.), 99999+4 blanks (U.S.), 999999+3 blanks (Canada)Postal Code--Current (CoC)..textNumbers or upper case letters. No special characters or embedded spaces allowed. Left justified, blank filled.In addition to U.S., Canadian, and Foreign postal codes.Patient“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.A,C,I,MFollow-up/Recurrence/DeathRSEER
1832Addr Current--CountryaddrCurrentCountry3Country 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].International Standards Organization (ISO) 3166-1 Country Three Character Codes and custom codes: ZZN, ZZC, ZZS, ZZP, ZZE, ZZF, ZZA, ZZX, ZZU, XNI, XCB, XEN, XSC, XGR, XSL, CSK, YUG, XUM, XNF, XSD, XWF, XSF, XEF, XIF, XET, XAP, XIS, XCR, XOR, XSE, XMS, XCH, XML, XMC, XPL..alphaUpper caseUse 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.PatientCountry 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.A,C,I,MDemographicRNAACCR132013
1840County--CurrentcountyCurrent3Code 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 [**FIPS Codes for Counties and Equivalent Entities)**](https://apps.naaccr.org/data-dictionary/data-dictionary/version=24/chapter-view/fips-codes-for-counties-and-equivalent-entities/)**.** 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.See the FIPS Codes for Counties and Equivalent Entities Section. See EDITS table BPLACE.DBF in Appendix B for geocodes used by CoC for non-U.S. residents. Also 998, 999.._Note:_ This data item is no longer supported by CoC (as of January 1, 2003).digitsRight justified, zero filledIn addition to FIPS and geocodes.PatientThis item may be used in administrative reports to define a referral area.A,C,I,MFollow-up/Recurrence/Death.NAACCR
1842Follow-Up Contact--CityfollowUpContactCity50Name 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.City name or UNKNOWN..textMixed case letters, special characters only as allowed by USPS, embedded spaces allowed, left justified, blank filled.TumorSometimes 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.A,C,I,MFollow-up/Recurrence/Death.SEER5.11997
1844Follow-Up Contact--StatefollowUpContactState2USPS 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].See EDITS table STATE.DBF in Appendix B..alphaUpper caseIn addition to USPS and Canadian Postal Service abbreviations.TumorSometimes 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.A,C,I,MFollow-up/Recurrence/Death.SEER5.11997
1846Follow-Up Contact--PostalfollowUpContactPostal9Postal 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.5-digit or 9-digit U.S. ZIP codes; 6- character Canadian postal codes; valid postal codes from other countries, 888888888, 999999999, 88888+4 blanks (U.S.), 99999+4 blanks (U.S.), 999999+3 blanks (Canada)..textNumbers or upper case letters. No special characters or embedded spaces allowed. Left justified, blank filledIn addition to U.S., Canadian, and foreign postal codes.TumorSometimes 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.A,C,I,MFollow-up/Recurrence/Death.SEER5.11997
1847FollowUp Contact--CountryfollowupContactCountry3Country 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].Use the International Standards Organization (ISO) 3166-1 Country Three Character Codes, augmented by custom codes: ZZN, ZZC, ZZS, ZZP, ZZE, ZZF, ZZA, ZZX, ZZU, XNI, XCB, XEN, XSC, XGR, XSL, CSK, YUG, XUM, XNF, XSD, XWF, XSF, XEF, XIF, XET, XAP, XIS, XCR, XOR, XSE, XMS, XCH, XML, XMC, XPL. See Appendix B for complete list of country names and corresponding three character alpha codes...alphaUpper caseUse 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.TumorCountry 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.A,C,I,MDemographic.NAACCR132013
1850Unusual Follow-Up MethodunusualFollowUpMethod2User-defined numeric codes used to flag cases that need unusual follow-up methods.00-99..*Note:* This data item is no longer supported by CoC (as of January 1, 2003).digits.TumorA,C,I,MFollow-up/Recurrence/Death.NAACCR
1854No Patient Contact FlagnoPatientContactFlag1This data item is used to flag when a patient, family member, or provider notifies the central registry that the patient does not want to be contacted for research purposes. This data item will be used in combination with the Reporting Facility Restriction Flag to identify data that the central registry may not be allowed to release. All reportable tumor records associated with a case that has been flagged will continue to be released for routine national surveillance activities (e.g., reporting to NCI, CDC, and NAACCR) and local public health surveillance activities (e.g., linkage for routine registry operations, use in cancer concern investigations, etc.), as well as studies that do not involve patient contact. 0, 1..**Instructions for Coding:** * Record the flag that best describes whether the patient should or should not be contacted for research purposes. * Assign this flag at the person-level so that it can be used to flag release of any associated tumors. * When consolidating, code 1 takes precedence. * Blanks are not allowable values.  digitsNumeric.PatientCancer registries have an obligation to manage the appropriate use and release of cancer data. There are times when a patient, family member, or physician may indicate that the patient does not want to ever be contacted for research purposes; however, there is currently no standard NAACCR data item to flag cases where no patient contact is allowed. Central registries have captured this content using various codes and various fields such as Unusual Follow Up Method [1850], the SEER\*DMS Patient No Contact field, or the State Requestor field, which will be retired in v22. It is essential that both reporting facilities and central cancer registries have a standard way to capture and transmit a flag to indicate when the patient should not be contacted for research purposes. Creating a standard data item would allow comprehensive and standard collection and transmission of this important information. This flag would be assigned at the patient level so that when an individual has multiple primaries, release of data on any and all tumor records would be restricted. A,C,I,MFollow-up/Recurrence/DeathRNAACCR232023
1856Reporting Facility Restriction FlagreportingFacilityRestrictionFlag2This data item will flag tumor records that the central cancer registry may not be allowed to release for research and certain other types of uses due to the reporting facility (e.g., VA, DoD, interstate exchange). It is important to note that all cases, regardless of the reporting facility, can be released for routine surveillance reporting to NCI, CDC, and NAACCR, for which all reportable tumor records are to be submitted. This item will be used in combination with another newly proposed data item for “No Patient Contact Flag” to identify data that the registry may not be allowed to release.00, 01, 02, 03, 04, 05, 06, 07..\***Note** Code 00: This code is assigned if the tumor record is only reported by a facility without potential restrictions on release of data (e.g., in-state hospital, physician offices, pathology lab). The code is also assigned if the tumor record is reported by both a facility without restrictions and a facility listed below that potentially has restrictions. For example, if an in-state hospital and a VHA facility both report the same tumor, code 00 would be assigned upon consolidation. Allowable release: Code 00: These records can be released; however, the type of information released will depend on a registry’s policies/procedures/legislation/administrative rules. Codes 01-07: These records can be released, without permission from the reporting facility(ies), in these specific instances: * Release for routine national surveillance activities (e.g., reporting to NCI, CDC, and NAACCR) * Release of PII for public health surveillance activities (e.g., linkage for routine registry operations, use in cancer concern investigations, etc.) * Release of a limited data set to researchers conducting linkage studies (e.g., cohort ID plus cancer information) * Release of de-identified data Limitations on external release of PII for research: Code 00: Release of PII depends on a registry’s internal policies/procedures/legislation/administrative rules. Codes 01-07: Release of PII is dependent on a registry’s agreements with the reporting facility(ies) and is generally handled as follows: Codes 01-03 (records received from single reporting facility) may require that the registry seek permission from original reporting facility when PII is released. Code 04-07 (records received from multiple reporting facilities with potential restrictions) generally do not require approval for the registry to release PII.digitsNumeric.TumorCancer registries have an obligation to manage the appropriate use and release of cancer data received from reporting facilities. Some reporting facilities (e.g., VA, DoD, interstate exchange) have restrictions about when the receiving central registry is allowed to release of data reported by their facility. Often times these restrictions depend on the agreements between the central registry and the reporting facility and focus on patient contact studies, research, and certain other types of studies that involve release of PII. These restrictions do not apply to release of data for routine surveillance activities. It is essential to have a standard way for central registries to identify and exclude potentially non-releasable records from a file that is transmitted to external parties for purposes other than routine surveillance. Currently, there is no standard data item to flag records that are potentially non-releasable based on the reporting facility and the methods to identify these records differ between registries. Many central registries have already been capturing information on potentially non-releasable records, but not in a standard manner. Registries have captured this content using various codes and various fields such as Unusual Follow Up Method \[1850\] or the State Requestor field, which will be retired in v22. For those registries that do not have a specific data item, queries on the reporting facilities are run to identify non-releasable records. This newly proposed data item will provide a standard and more efficient way for registries to flag records that potentially should not be released based on the reporting facilities.A,C,I,MFollow-up/Recurrence/DeathRNAACCR232023
1860Recurrence Date--1strecurrenceDate1st8The date of the first recurrence of this tumor. See [**Data Descriptor Table**](https://apps.naaccr.org/data-dictionary/data-dictionary/version=24/chapter-view/data-descriptor-table/) for date format.Valid datesDate of First Recurrence (CoC).RdateYYYYMMDD.TumorA,C,I,MUpdated SEERFollow-up/Recurrence/DeathR*CoC
1880Recurrence Type--1strecurrenceType1st2Code for the type of first recurrence after a period of documented disease free intermission or remission.00, 04, 06, 10, 13-17, 20-22, 25-27, 30, 36, 40, 46, 51-60, 62, 70, 88, 99Type of First Recurrence (CoC).RdigitsRight justified, zero filled.TumorA,C,I,MUpdated SEERFollow-up/Recurrence/DeathR*CoC
1910Cause of DeathcauseOfDeath4Official underlying cause of death as coded from the death certificate in valid ICD-7, ICD-8, ICD-9, and ICD-10 codes.Valid ICD-7, ICD-8, ICD-9, and ICD-10 codes; also 0000, 7777, 7797Underlying Cause of Death (ICD Code) (pre-96 CoC), Underlying Cause of Death (SEER)R*.Revised Descriptions of Codes 7777 and 7797;text4 digits (for ICD-7, 8, 9); for ICD-10, upper case letter followed by 3 digits or upper case letter followed by 2 digits plus blank_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_](http://seer.cancer.gov/tools/codingmanuals/) for additional instructions.)RPatientCause 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.A,C,I,MFollow-up/Recurrence/DeathRSEER
1914SEER Cause Specific CODseerCauseSpecificCod1This variable was created for use in cause-specific survival and designates that the person died of their cancer. Adapted from <http://seer.cancer.gov/causespecific/>: Cause-specific survival is a net survival measure representing survival of a specified cause of death in the absence of other causes of death. Estimates are calculated by specifying the cause of death. Individuals who die of causes other than the specified cause are considered to be censored. This requires a cause of death variable that accurately captures all causes related to the specific cause. Vital records offices use algorithms to process causes of death from death certificates in order to identify a single, disease-specific, underlying cause of death. In some cases, attribution of a single cause of death may be difficult and misattribution may occur. For example a death may be attributed to the site of metastasis instead of the primary site. To capture deaths related to the specific cancer but not coded as such, the SEER cause-specific death classification variables are defined by taking into account causes of deaths in conjunction with tumor sequence (i.e., only one tumor or the first of subsequent tumors), site of the original cancer diagnosis, and comorbidities (e.g., AIDS and/or site-related diseases). The 'SEER cause-specific death classification' variable is used to obtain cancer-specific survival probability for a given cohort of cancer patients. Deaths attributed to the cancer of interest are treated as events and deaths from other causes are treated as censored observation. This variable is used in SEER\*Stat cause-specific survival and crude probability of death using cause of death information.0, 1, 8, 9..digitsDTumorThese changes will benefit the cancer surveillance community by facilitating the application of standard methods for survival analysis. Beginning with data collected in the November 2014 call for data, NAACCR has published *Cancer in North America Volume 4: Cancer Survival in the United States and Canada*, which provides cancer survival estimates on a wider population than was previously available. However, at present IMS must pre-process the datasets that are included in the NAACCR survival dataset to calculate the four new standard data items, SEER Cause Specific COD [1914], SEER Other COD [1915], Record Number Recode [1775], and Vital Status Recode [1762]. For registries that do not submit cause of death information to NAACCR, it is not possible to calculate the 'SEER cause-specific death classification' or 'SEER other cause of death classification' variables. The 4 new data items will assist individual registries in performing survival analyses using their own data.A,C,I,MFollow-up/Recurrence/DeathDSEER182018
1915SEER Other CODseerOtherCod1Using the same recoding logic as the ‘SEER cause-specific death classification’ variable, the ‘SEER other cause of death classification’ variable designates that the person died of causes other than their cancer. Adapted from <http://seer.cancer.gov/causespecific/>: The 'SEER other cause of death classification' variable is used to obtain the other-cause survival probability for a cohort of patients. It is used when deaths attributed to causes other than cancer are treated as events and deaths from cancer are treated as censored observation. This variable is used in the SEER\*Stat left-truncated life table session. -specific survival and crude probability of death using cause of death information.0, 1, 8, 9..digitsDTumorThese changes will benefit the cancer surveillance community by facilitating the application of standard methods for survival analysis. Beginning with data collected in the November 2014 call for data, NAACCR has published *Cancer in North America Volume 4: Cancer Survival in the United States and Canada*, which provides cancer survival estimates on a wider population than was previously available. However, at present IMS must pre-process the datasets that are included in the NAACCR survival dataset to calculate the four new standard data items, SEER Cause Specific COD [1914], SEER Other COD [1915], Record Number Recode [1775], and Vital Status Recode [1762]. For registries that do not submit cause of death information to NAACCR, it is not possible to calculate the 'SEER cause-specific death classification' or 'SEER other cause of death classification' variables. The 4 new data items will assist individual registries in performing survival analyses using their own data.A,C,I,MFollow-up/Recurrence/DeathDSEER182018
1920ICD Revision NumbericdRevisionNumber1Indicator for the coding scheme used to code the cause of death.0, 1, 7, 8, 9ICD Code Revision Used for Cause of Death (SEER)..digitsRPatientA,C,I,MFollow-up/Recurrence/DeathRSEER
1930Autopsyautopsy1Code indicating whether or not an autopsy was performed.0-2, 9..digits.PatientA,C,I,MFollow-up/Recurrence/Death.NAACCR
1942Place of Death--StateplaceOfDeathState2State or Province where the patient died and where certificate of death is filed. 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 PLACE OF DEATH--COUNTRY [1944]. It replaces the use of PLACE OF DEATH [1940].USPS or CanadaPost 2-character codes; CD, US, XX, YY, ZZ, BlankD.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](http://seer.cancer.gov/tools/codingmanuals/index.html)).alphaUpper caseRPatientThis field also helps carry out death clearance. When a reporting facility reports a place of death, the information can help in death certificate matching. It can also signal an out-of-state death for which the death certificate is to be requested.A,C,I,MDemographicRNAACCR132013
1944Place of Death--CountryplaceOfDeathCountry3Code for the country in which the patient died and where certificate of death is filed. 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 Place of Death--State \[1942\]. It replaces the use of Place of Death \[1940\].International Standards Organization (ISO) 3166-1 Country Three Character Codes augmented by custom codes: ZZN, ZZC, ZZS, ZZP, ZZE, ZZF, ZZA, ZZX, ZZU, XNI, XCB, XEN, XSC, XGR, XSL, CSK, YUG, XUM, XNF, XSD, XWF, XSF, XEF, XIF, XET, XAP, XIS, XCR, XOR, XSE, XMS, XCH, XML, XMC, XPL, Blank. See Appendix B for complete list of country names and corresponding three character alpha codes.D.alphaUpper caseUse 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 codesR*PatientPlace of death is helpful for carrying out death clearance. When a reporting facility reports a place of death that is outside of the registry’s country, the information can signal a death for which the death certificate will not be available from another state or through the NDI linkage.A,C,I,MDemographicRNAACCR132013
1960Site (73-91) ICD-O-1siteIcdO14Area for retaining the ICD-O-1 primary site code entered before conversion to ICD-0-2. The item name includes years 1973-91. However, some states may have used the codes for cases before 1973.1400-1999Primary Site (1973-91) (SEER)..digitsFour digits, first digit equals 1. Reference ICD-O-1 for valid entriesFor tumors diagnosed before 1992, contains the ICD-O-1 site code as originally coded, if available. Blank for tumors coded directly into ICD-O-2 (i.e., 1992 and later tumors).TumorA,C,I,MEdit Overrides/Conversion History/System AdminRHSEER
1971Histology (73-91) ICD-O-1histologyIcdO14Area 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. The item name includes years 1973-91. However, some states may have used the codes for cases before 1973.8000-9970..digitsReference ICD-O-1 for valid entriesFor 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).TumorA,C,I,MEdit Overrides/Conversion History/System AdminRHSEER
1972Behavior (73-91) ICD-O-1behaviorIcdO11Area for retaining behavior portion (1 digit) of the ICD-O-1 or field trial morphology codes entered before a conversion to ICD-O-2. 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.Reference ICD-O-1 for valid entries..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.digits.TumorA,C,I,MEdit Overrides/Conversion History/System AdminRHSEER
1973Grade (73-91) ICD-O-1gradeIcdO11Area 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. The item name includes years 1973-91. However, some states may have used the codes for cases before 1973.Reference ICD-O-1 for valid entries..digitsFor cases diagnosed before 1992, contains the ICD-O-1 or field trial 1-digit grade code as originally coded, if available.^18, 19^.TumorA,C,I,MEdit Overrides/Conversion History/System AdminRHSEER
1975Derived Summary Grade 2018derivedSummaryGrade20181Grade is a measure of the aggressiveness of the tumor. Grade and cell type are important prognostic indicators for many cancers. Due to changes in 2018, it is difficult to compare grade information from previous years. By developing a Derived Summary Grade data item, comparison of Grade over time (prior to 2018 compared to 2018+) will be much easier.  This data item will be derived from the following existing fields: * 3843: Grade Clinical * 3844: Grade Pathological * _Note: Prior to 2018, grade was collected prior to neoadjuvant therapy, which is why Grade Post-therapy Clin (yc) and Grade Post-Therapy (yp) are not part of the calculation_ This new data item will be applied to cases for 2018+ (would not be applicable for cases diagnosed prior to 2018). This would not be a conversion but deriving a new data item based on information already in the cancer registry systems. Once new cases are entered, then the Derived Summary Grade will be derived.1, 2, 3, 4, 5, 8, 9, A, B, C, D, E, H, L, M, S, BlankmixedDTumorThe algorithm for Derived Summary Grade is already used by the SEER program for schemas that need grade for EOD Stage group; however, that information is currently not stored anywhere. SEER will use the same algorithm to calculate the Derived Summary Grade and this data item will store that information. This algorithm will also make it possible for researchers to analyze grade over time more easily.A,C,I,MRevisedStage/Prognostic FactorsDSEER242024
1981Over-ride SS/NodesPosoverRideSsNodespos1Some 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)1 or blankOver-ride Summary Stage/Nodes Positive..digits.TumorSome 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 [**Standards for Cancer Registries, Standard Data Edits**](https://www.naaccr.org/standard-data-edits/).  **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.A,C,I,MEdit Overrides/Conversion History/System AdminRHNAACCR92001
1982Over-ride SS/TNM-NoverRideSsTnmN1Some 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)1 or blankOver-ride Summary Stage/TNM-N..digits.TumorSome 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 [**Standards for Cancer Registries, Standard Data Edits**](https://www.naaccr.org/standard-data-edits/). **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.A,C,I,MEdit Overrides/Conversion History/System AdminRHNAACCR
1983Over-ride SS/TNM-MoverRideSsTnmM1Some 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)1 or blankOver-ride Summary Stage/TNM-M..digits.TumorSome 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 [**Standards for Cancer Registries, Standard Data Edits**](https://www.naaccr.org/standard-data-edits/)**.** **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.A,C,I,MEdit Overrides/Conversion History/System AdminRHNAACCR92001
1985Over-ride Acsn/Class/SeqoverRideAcsnClassSeq1Some 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).1 or blankOver-ride Accession/Class of Case/Sequence..digits.TumorSome 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 [**Standards for Cancer Registries, Standard Data Edits**](https://www.naaccr.org/standard-data-edits/). **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.A,C,I,MEdit Overrides/Conversion History/System Admin.NAACCR92001
1986Over-ride HospSeq/DxConfoverRideHospseqDxconf1Some 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)1 or blankOver-ride Hospital Sequence/Diagnostic Confirmation..digits.TumorSome 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 [**Standards for Cancer Registries, Standard Data Edits**](https://www.naaccr.org/standard-data-edits/).  **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 > 5 and Sequence Number--Hospital > 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.A,C,I,MEdit Overrides/Conversion History/System Admin.NAACCR92001
1987Over-ride CoC-Site/TypeoverRideCocSiteType1Some 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)1 or blank..digits.TumorSome 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 [**Standards for Cancer Registries, Standard Data Edits**](https://www.naaccr.org/standard-data-edits/).  **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.A,C,I,MEdit Overrides/Conversion History/System Admin.NAACCR92001
1988Over-ride HospSeq/SiteoverRideHospseqSite1Some 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)1 or blankOver-ride Hospital Sequence/Site..digits.TumorSome 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 [**Standards for Cancer Registries, Standard Data Edits**](https://www.naaccr.org/standard-data-edits/). **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 less than 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.A,C,I,MEdit Overrides/Conversion History/System Admin.NAACCR92001
1989Over-ride Site/TNM-StgGrpoverRideSiteTnmStggrp1Some 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)1 or blank..digits.TumorSome 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 [**Standards for Cancer Registries, Standard Data Edits**](https://www.naaccr.org/standard-data-edits/).  **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.A,C,I,MEdit Overrides/Conversion History/System AdminRNAACCR92001
1990Over-ride Age/Site/MorphoverRideAgeSiteMorph1Some 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)1-3 or blankAge/Site/Histology Interfield Review (Interfield Edit 15) (SEER #3)..digitsRTumorSome 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 [**Standards for Cancer Registries, Standard Data Edits**](https://www.naaccr.org/standard-data-edits/). **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.A,C,I,MEdit Overrides/Conversion History/System AdminRSEER
1992Over-ride TNM StageoverRideTnmStage1Some 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, TNM Clin Stage Valid A- Ed 7 (CoC) * Primary Site, TNM Clin Stage Valid B- Ed 7 (CoC) * Primary Site, TNM Path Stage Valid A- Ed 7 (CoC) * Primary Site, TNM Path Stage Valid B- Ed 7 (CoC) These edits check T, N, and M combinations against stage group. Adding this over-ride allows the edit to pass when combinations of T, N, and M are entered that are not included in the stage tables used with the edits.   1, Blank..digits.TumorThis over-ride will allow registrars to enter combination of T, N, and M with a stage group that differs from the combinations documented in the AJCC Staging Manual.A,C,I,MEdit Overrides/Conversion History/System Admin.NAACCR182018
1993Over-ride TNM TisoverRideTnmTis1Some 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: * TNM Clin T, N, M, In Situ (CoC) * TNM Path T, N, M, In Situ (CoC) If the patient has a T value indicating in situ/ noninvasive, this edit verifies that the N, M, and stage group reflect in situ/noninvasive disease. However, there are certain circumstances where AJCC does allow a T value indicating in situ/noninvasive and N, M, and/or stage group that indicates invasive disease. An over-ride is required to accommodate these situations.  1, Blank..digits.TumorThis over-ride will allow registrars to enter combination of T, N, and M with a stage group that differs from the combinations documented in the AJCC Staging Manual.A,C,I,MEdit Overrides/Conversion History/System AdminRNAACCR182018
1994Over-ride TNM 3overRideTnm31Some 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.1, Blank..digits.TumorSome 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.A,C,I,MEdit Overrides/Conversion History/System Admin.NAACCR182018
2000Over-ride SeqNo/DxConfoverRideSeqnoDxconf1Some 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)1 or blankSequence Number/Diagnostic Confirmation Interfield Review (Interfield Edit 23)..digitsRTumorSome 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 [**Standards for Cancer Registries, Standard Data Edits**](https://www.naaccr.org/standard-data-edits/)**.** **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 >5) and tumor sequence number >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.A,C,I,MEdit Overrides/Conversion History/System AdminRSEER
2010Over-ride Site/Lat/SeqNooverRideSiteLatSeqno1Some 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.1 or blankSite/Histology/Laterality/Sequence Number Interrecord Review (Interrecord Edit 09)..digitsRTumorSome 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 [**Standards for Cancer Registries, Standard Data Edits**](https://www.naaccr.org/standard-data-edits/).  **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.A,C,I,MEdit Overrides/Conversion History/System AdminRSEER
2020Over-ride Surg/DxConfoverRideSurgDxconf1Some 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)1 or blankSurgery/Diagnostic Confirmation Interfield Review (Interfield Edit 46)..digitsRTumorSome 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 of [**Standards for Cancer Registries, Standard Data Edits**](https://www.naaccr.org/standard-data-edits/). **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.A,C,I,MEdit Overrides/Conversion History/System AdminRSEER
2030Over-ride Site/TypeoverRideSiteType1Some 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)1 or blankSite/Type Interfield Review (Interfield Edit 25)..digitsRTumorSome 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 [**Standards for Cancer Registries, Standard Data Edits**](https://www.naaccr.org/standard-data-edits/).  **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.A,C,I,MEdit Overrides/Conversion History/System AdminRSEER
2040Over-ride HistologyoverRideHistology1Some 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)1-3 or blankHistology/Behavior Interfield Review (Field Item Edit Morph)..digitsRTumorSome 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 [**Standards for Cancer Registries, Standard Data Edits**](https://www.naaccr.org/standard-data-edits/).  **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 > 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 > 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.A,C,I,MEdit Overrides/Conversion History/System AdminRSEER
2050Over-ride Report SourceoverRideReportSource1Some 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)1 or blankType of Reporting Source/Sequence Number Interfield Review (Interfield Edit 04) (Seer #7)..digitsRTumorSome 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 [**Standards for Cancer Registries, Standard Data Edits**](https://www.naaccr.org/standard-data-edits/).  **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.A,C,I,MEdit Overrides/Conversion History/System AdminRSEER
2060Over-ride Ill-define SiteoverRideIllDefineSite1Some 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)1 or blankSequence Number/Ill-defined Site Interfield Review (Interfield Edit 22)..digitsRTumorSome 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 [**Standards for Cancer Registries, Standard Data Edits**](https://www.naaccr.org/standard-data-edits/).  **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 \< 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.A,C,I,MEdit Overrides/Conversion History/System AdminRSEER
2070Over-ride Leuk, LymphomaoverRideLeukLymphoma1Some 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)1 or blankLeukemia or Lymphoma/Diagnostic Confirmation Interfield Review (Interfield Edit 48)..digitsRTumorSome 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 [**Standards for Cancer Registries, Standard Data Edits**](https://www.naaccr.org/standard-data-edits/).  **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.A,C,I,MEdit Overrides/Conversion History/System AdminRSEER
2071Over-ride Site/BehavioroverRideSiteBehavior1Some 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)1 or blankOver-ride Flag for Site/Behavior (IF39).._Note:_ The IF 39 edit does not allow _in situ_ cases 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.digitsRTumorSome 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 [**Standards for Cancer Registries, Standard Data Edits**](https://www.naaccr.org/standard-data-edits/).  **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.A,C,I,MEdit Overrides/Conversion History/System AdminRSEER5.11997
2072Over-ride Site/EOD/DX DtoverRideSiteEodDxDt1Some 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)1 or blankOver-ride Flag for Site/CS Extension/Diagnosis Date (IF176), Over-ride Flag for Site/EOD/Diagnosis Date (IF40) (SEER #13)..digits.TumorSome 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 [**Standards for Cancer Registries, Standard Data Edits**](https://www.naaccr.org/standard-data-edits/).  **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.A,C,I,MEdit Overrides/Conversion History/System AdminRSEER5.11997
2073Over-ride Site/Lat/EODoverRideSiteLatEod1Some 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)1 or blankOver-ride Flag for Site/Laterality/CS Extension (IF177), Over-ride Flag for Site/Laterality/EOD (IF41)..digits.TumorSome 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 [**Standards for Cancer Registries, Standard Data Edits**](https://www.naaccr.org/standard-data-edits/)**.** **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.A,C,I,MEdit Overrides/Conversion History/System AdminRSEER5.11997
2074Over-ride Site/Lat/MorphoverRideSiteLatMorph1Some 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)1 or blankOver-ride Flag for Site/Laterality/Morphology (IF42)..digitsRTumorSome 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 [**Standards for Cancer Registries, Standard Data Edits**](https://www.naaccr.org/standard-data-edits/)**.** **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”.A,C,I,MEdit Overrides/Conversion History/System AdminRSEER5.11997
2078Over-ride Name/Sex Assigned at BirthoverRideNameSex1Some 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: * Sex Assigned at Birth, Name-First, Date of Birth (NAACCR)1, Blank.._Note_: Leave blank if the program does not generate an error message for the edit Sex, Name-First, Date of Birth (NAACCR)Name RevisedReviseddigitsRPatientSome 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 [**Standards for Cancer Registries, Standard Data Edits**](https://www.naaccr.org/standard-data-edits/)**.** Over-ride flag as used in the EDITS Software Package Edits of the type Sex, Name does not allow extremely rare or nonexistent combinations of first name and sex, such as John/female.RevisedA,C,I,MRevisedEdit Overrides/Conversion History/System AdminRNAACCR182018
2085Date Case InitiateddateCaseInitiated8Date the electronic abstract is initiated in the reporting facility's cancer registry database. See [**Data Descriptor Table**](https://apps.naaccr.org/data-dictionary/data-dictionary/version=24/chapter-view/data-descriptor-table/) for date format. Standard edits check that no dates are later than the current date or the date completed.Valid date..dateYYYYMMDD.TumorThis item is used to assess and monitor the timeliness of reporting. Timeliness of abstracting (and reporting) is a concern for all standard-setting organizations and consequently, timeliness standards have been established. Examples of use are as follows: * This item can be used with the Date of 1^st^Contact \[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.A,C,I,MEdit Overrides/Conversion History/System Admin.NAACCR122010
2090Date Case CompleteddateCaseCompleted8The 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 [**Data Descriptor Table**](https://apps.naaccr.org/data-dictionary/data-dictionary/version=24/chapter-view/data-descriptor-table/) 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\].Valid date..dateYYYYMMDD.TumorA,C,I,MEdit Overrides/Conversion History/System Admin.NAACCR
2092Date Case Completed--CoCdateCaseCompletedCoc8Identifies the date that specified items are completed, based on the Class of Case, where those items pass the relevant edits. Follow-up information, including delayed treatment received elsewhere, may be coded after the Date Case Completed--CoC. See the current [_STORE_](http://www.facs.org/cancer/coc/fordsmanual.html) 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 [**Data Descriptor Table**](https://apps.naaccr.org/data-dictionary/data-dictionary/version=24/chapter-view/data-descriptor-table/) for date format.Valid date.DdateYYYYMMDD.TumorA,C,I,MEdit Overrides/Conversion History/System Admin.CoC122010
2100Date Case Last ChangeddateCaseLastChanged8Date the case was last changed or updated. See [**Data Descriptor Table**](https://apps.naaccr.org/data-dictionary/data-dictionary/version=24/chapter-view/data-descriptor-table/) for date format. Standard edits check that no dates are later than the current date.Valid date.DdateYYYYMMDD.TumorA,C,I,MEdit Overrides/Conversion History/System Admin.NAACCR
2110Date Case Report ExporteddateCaseReportExported8Date the reporting facility exports the electronic abstract to a file for transmission to the central registry. See [**Data Descriptor Table**](https://apps.naaccr.org/data-dictionary/data-dictionary/version=24/chapter-view/data-descriptor-table/) for date format. Standard edits check that no dates are later than the current date. Definitions may vary among registries and software providers.Valid dateDate Case Transmitted (pre-98 NAACCR)..dateYYYYMMDDRTumorA,C,I,MEdit Overrides/Conversion History/System AdminRNPCR
2111Date Case Report ReceiveddateCaseReportReceived8Date 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 [**Data Descriptor Table**](https://apps.naaccr.org/data-dictionary/data-dictionary/version=24/chapter-view/data-descriptor-table/) for date format.Valid date..dateYYYYMMDDRTumorThis 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.A,C,I,MEdit Overrides/Conversion History/System AdminRNPCR5.11997
2112Date Case Report LoadeddateCaseReportLoaded8Date 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 [**Data Descriptor Table**](https://apps.naaccr.org/data-dictionary/data-dictionary/version=24/chapter-view/data-descriptor-table/) for date format.Valid date..dateYYYYMMDDRTumorA,C,I,MEdit Overrides/Conversion History/System AdminRNPCR5.11997
2113Date Tumor Record AvailbldateTumorRecordAvailbl8Date 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 [**Data Descriptor Table**](https://apps.naaccr.org/data-dictionary/data-dictionary/version=24/chapter-view/data-descriptor-table/) for date format.Valid date..dateYYYYMMDDRTumorThis 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.A,C,I,MEdit Overrides/Conversion History/System AdminDNPCR5.11997
2116ICD-O-3 Conversion FlagicdO3ConversionFlag1Code specifying how the conversion of site and morphology codes from ICD-O-2 to ICD-O-3 was accomplished.Blank, 0, 1, 3..digitsRTumorA,C,I,MEdit Overrides/Conversion History/System AdminRSEER92001
2117Schema ID Version CurrentschemaIdVersionCurrent5This item indicates the version of EOD component of the SEER Staging API used to assign the 2018 and later staging fields of Schema ID, Grades, EOD input fields, SS2018, and SSDIs. This data item is recorded the first time the Schema ID is determined and should be updated each time the related input fields are modified.1.0-99.99R*DSchema ID Version Current is a code with up to 2 digits, a decimal and then up to 2 more digits. (e.g., 1.5, 10.12). The first two digits represent the major version number related to diagnosis year; the second two digits represent minor version changes with the diagnosis years. Minimum allowable value would be “1.0”. Maximum allowable value would be “99.99”.  Blanks would not be allowed. This data item will be generated by registry software. No coding instructions are required.Revised. Added code 3.3numericDTumorOver time, the definitions for Schema ID and the input codes and instructions for Grades, EOD, SS2018, and SSDI items may change. This item identifies the correct interpretation of information recorded.A,C,I,MEdit Overrides/Conversion History/System AdminDSEER212021
2118Schema ID Version OriginalschemaIdVersionOriginal5This item indicates the version of EOD component of the SEER Staging API used to assign the 2018 and later staging fields of Schema ID, Grades, EOD input fields, SS2018, and SSDIs. This data item is recorded the first time the Schema ID is determined. This data item should not be updated each time the related input fields are modified.1.0-99.99R*DSchema ID Version Original is a code with up to 2 digits, a decimal and then up to 2 more digits. (e.g., 1.5, 10.12). The first two digits represent the major version number related to diagnosis year; the second two digits represent minor version changes with the diagnosis years. Minimum allowable value would be “1.0”. Maximum allowable value would be “99.99”.  Blanks would not be allowed.   This data item will be generated by registry software. No coding instructions are required.Revised Added code 3.3numericDTumorOver time, the definitions for Schema ID and the input codes and instructions for Grades, EOD, SS2018, and SSDI items may change. This item identifies the original instructions used to code these items.A,C,I,MEdit Overrides/Conversion History/System AdminDSEER212021
2140CoC Coding Sys--CurrentcocCodingSysCurrent2Code the ACoS CoC coding system currently used in the record. CoC codes may be converted from an earlier version.00-09, 99Commission on Cancer Coding System-Current (CoC)..digitsRight justified, zero filledThis item is no longer required by CoC..TumorA,C,I,MEdit Overrides/Conversion History/System Admin.CoC
2150CoC Coding Sys--OriginalcocCodingSysOriginal2Code for the ACoS CoC coding system originally used to code the record.00-09, 99..digitsRight justified, zero filledThis item is no longer required by CoC..TumorA,C,I,MEdit Overrides/Conversion History/System Admin.CoC
2152CoC Accredited FlagcocAccreditedFlag1CoC Accredited Flag is assigned at the point and time of data abstraction to label an abstract being prepared for an analytic cancer case at a facility accredited by the Commission on Cancer (CoC). The flag may be assigned manually or can be defaulted by the registry’s software.0, 1, 2, Blank..digitsRTumorCoC-accredited facilities are required to collect certain data items including TNM staging. It is burdensome for central registries to maintain a list of accredited facilities, and the list changes frequently. The flag is a means of incorporating the accredited status into abstracts at the time of abstraction by someone who has knowledge of the status. The flag thus simplifies validating that required items have been abstracted by CoC-accredited facilities. The flag also allows cases to be stratified during analyses to identify those never seen at a CoC-accredited facility; e.g., percentage of all cases seen in at least one CoC-accredited facility, evaluation of outcomes by facility status. NPCR will use this flag for facility status stratification.A,C,I,MEdit Overrides/Conversion History/System AdminRNPCR182018
2156AJCC API Version CurrentajccApiVersionCurrent8This item indicates the version of the AJCC TNM API incorporated into the cancer registry software that created the record with TNM staging data in the 8th and later versions. It should be recorded the first time the AJCC Release ID (including a value of 08.01.00) is determined and should be updated each time the related input fields listed below are modified. If the registry software incorporates the AJCC API directly, the value is obtained from AJCC’s API.  If the software instead incorporates AJCC’s Cancer Surveillance API, the value can be returned from there. The value indicates the most recent time at least one of the related input items listed below was modified.   A valid value is required for all cases diagnosed 2018 or later that have values entered in the AJCC or related data items. Cases abstracted prior to implementation of this data item will be assigned a value of 08.XX.XX during the conversion to v21.Values of the form XX.YY.ZZ, BlankR*D*Note:* This data item will be generated by registry software. Blank is allowable in the case that no AJCC or related input items are coded.textCharacters may be alphanumeric and include decimal points..TumorOver time the definitions and other content contained in the AJCC’s API may change. This value indicates the most recent release used to modify at least one of the related input items listed below.A,C,I,MEdit Overrides/Conversion History/System AdminD*AJCC212021
2157AJCC API Version OriginalajccApiVersionOriginal8This item indicates the version of the AJCC API incorporated into the cancer registry software that created the record with TNM stage data in the 8^th^ and later versions. It should be recorded the first time the AJCC ID (including a value of 8) is determined. If the registry software incorporates the APCC API directly, the value is obtained from AJCC’s API. If the software instead incorporates AJCC’s Cancer Surveillance API, the value can be returned from there. A valid value is required for all cases diagnosed 2018 or later that have values entered in the AJCC or related data items. Cases abstracted prior to implementation of this data item will be assigned a value of 08.XX.XX during the conversion to v21. Values of the form XX.YY.ZZ, BlankR*DBlank is allowable in the case that no AJCC or related input items are coded. textCharacters may be alphanumeric and include decimal points..TumorOver time the definitions and other content contained in the AJCC’s API may change. This item identifies the original API content used to code the TNM data.A,C,I,MEdit Overrides/Conversion History/System AdminD*AJCC212021
2158AJCC Cancer Surveillance DLL Version CurrentajccCancerSurvApiVersionCurrent13This item indicates the most recently accessed version of the Cancer Surveillance .dll incorporated into the cancer registry software that created the record with stage data diagnosed 2018 and later. AJCC Cancer Surveillance DLL Version Current \[2158\] will be assigned based on the version of the AJCC Cancer Surveillance .dll in use in the registry software system. It must be updated every time a new version is incorporated into your system and all relevant cases should be updated to reflect the same value. * For cases diagnosed prior to 2018, this field should remain blank. * For cases diagnosed in 2018-2020, this field should be set to the AJCC Cancer Surveillance .dll version in use at the time of implementation. * For cases diagnosed in 2018 and later abstracted after implementation, use the AJCC Cancer Surveillance .dll version in use at the time the case is being abstracted. The value is obtained from the .dll.   Formerly: AJCC Cancer Surveillance API Version CurrentNumbers, decimal pointsAJCC Cancer Surveillance API Version CurrentR*DtextN[N].N[N].N[N].N[NNN] Four groups of one or more digits separated by periods. The first group identifies the underlying AJCC edition number. The second a major revision. The third a minor revision. The last group identifies the build. The value 08.01.05.0025 would represent the 8th edition, 1st major revision, 5th minor revision, and the 25th build of the API.This data item will be generated by registry software. The AJCC Cancer Surveillance API contains contents to support collection of AJCC's TNM, EOD, SSDIs, and directly entered Summary Stage 2018. The underlying contents are loaded from AJCC's API and SEER's web service. The API is versioned independently from the imported contents. The value indicates the version of the Cancer Surveillance API used most recently to code the items listed below and is obtained from the API. It should be recorded the first time the AJCC ID (including a value of XX) and/or Schema ID is determined and should be updated each time an updated AJCC Cancer Surveillance API is implemented. Related Input Fields * AJCC TNM Clin T (also Path and Post Therapy T) \[1001, 1011, 1021\] * AJCC TNM Clin N (also Path and Post Therapy N) \[1002, 1012, 1022\] * AJCC TNM Clin M (also Path and Post Therapy M) \[1003, 1013, 1023\] * AJCC TNM Clin Stage Group (also Path and Post Therapy Stage Group \[1004, 1014, 1024\]) * Summary Stage 2018 \[764\] * EOD Primary Tumor \[772\] * EOD Regional Nodes \[774\] * EOD Mets \[776\] * All SSDIs (see SSDI manual for complete list).DTumorOver time, the definitions and other content contained in the .dll may change. This item identifies the current .dll content used to code the items.A,C,I,MEdit Overrides/Conversion History/System Admin.AJCC212021
2159AJCC Cancer Surveillance DLL Version OriginalajccCancerSurvApiVersionOriginal13This item indicates the version of the AJCC Cancer Surveillance .dll incorporated into the cancer registry software that created the record with stage data diagnosed 2018 and later. It should be recorded the first time the AJCC ID (including a value of XX) and/or Schema ID are determined using the .dll. The value is obtained from the .dll. Formerly: AJCC Cancer Surveillance API Version OriginalNumbers, decimal pointsR*DtextN[N].N[N].N[N].N[NNN] Four groups of one or more digits separated by periods. The first group identifies the underlying AJCC edition number. The second a major revision. The third a minor revision. The last group identifies the build. The value 08.01.05.0025 would represent the 8th edition, 1st major revision, 5th minor revision, and the 25th build of the API.This data item will be generated by registry software.   The AJCC Cancer Surveillance API contains contents to support collection of AJCC’s TNM, EOD, and directly entered Summary Stage 2018. The underlying contents are loaded from AJCC’s API and SEER’s web service. The API is versioned independently from the imported contents.   The value indicates the version of the AJCC Cancer Surveillance API originally used to code the items listed below and is obtained from the API. It should be recorded the first time the AJCC ID (including a value of XX) and/or Schema ID is determined and should not be updated each time the related input fields are modified.  However, if changes made to the diagnosis and/or date of diagnosis result in a different AJCC ID and/or Schema ID, the value for AJCC Cancer Surveillance DLL Version Original should be reset.   **Related Input Fields** * AJCC TNM Clin T (also Path and Post Therapy T) \[1001, 1011, 1021\] * AJCC TNM Clin N (also Path and Post Therapy N) \[1002, 1012, 1022\] * AJCC TNM Clin M (also Path and Post Therapy M) \[1003, 1013, 1023\] * AJCC TNM Clin Stage Group (also Path and Post Therapy Stage Group \[1004, 1014, 1024\]) * Summary Stage 2018 \[764\] * EOD Primary Tumor \[772\] * EOD Regional Nodes \[774\] * EOD Mets \[776\] * All SSDIs (see SSDI manual for complete list).DTumorOver time, the definitions and other content contained in the .dll may change. This item identifies the original content used to code the items.A,C,I,MEdit Overrides/Conversion History/System Admin.AJCC212021
2170Vendor NamevendorName10System-generated. Name of the computer services vendor who programmed the system submitting the data. Abbreviate as necessary and keep a consistent name throughout all submissions. Include software version number where available. Code is self-assigned by vendor..Rtext.TumorThis is used to track which vendor and which software version submitted the case. It helps define the source and extent of a problem discovered in data submitted by a software provider.A,C,I,MEdit Overrides/Conversion History/System Admin.NAACCR12.22011
2230Name--LastnameLast40Last name of the patient.Spaces, hyphens and apostrophes are allowed. Do not use other punctuation.Last Name (CoC)RRtextMixed case, left justified. Truncate name if more than 40 characters long._Note: Refer to the SEER Program Coding and Staging Manual._RPatientA,C,MRevisedRevisedPatient-ConfidentialRSEER12.22011
2232Name--Birth SurnamenameBirthSurname40Last name (surname) of patient at birth, regardless of gender or marital status.  Other alternate names should be recorded in the data item, Name--Alias \[2280\].Embedded spaces, hyphens, apostrophes. No other special characters are allowed.R*RThe field should be left blank if the birth surname 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 was introduced to be a gender-neutral birth-surname data item, analogous to Name--Maiden \[2390\]. It is to have been populated in the 2021 conversion by values in \[2390\]. The original (Name--Maiden) data item had been supported by CoC until January 1, 2003.RevisedRevisedtextMixed case; Left-justified, and blank-filled.RPatientThis can be used to link reports on a person whose surname might be different on different documents. It is also useful when using a Spanish surname algorithm to categorize ethnicity.A,C,MRevisedRevisedPatient-ConfidentialRNAACCR212021
2240Name--FirstnameFirst40First name of the patient.Blanks, spaces, hyphens and apostrophes are allowed. Do not use other punctuation.First Name (CoC)R*RRevisedtextMixed case, left justified. Truncate name if more than 40 characters long._Note:_ The CoC [_STORE_](http://www.facs.org/cancer/coc/fordsmanual.html) 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: Refer to the SEER Program Coding and Staging Manual._RPatientA,C,MRevisedRevisedPatient-ConfidentialRSEER12.22011
2250Name--MiddlenameMiddle40Middle name or, if middle name is unavailable, middle initial of the patient.Blanks, spaces, hyphens and apostrophes are allowed. Do not use other punctuation.Middle Initial (pre-96 CoC), Middle Name (CoC)R*RtextMixed case, left justified. Truncate name if more than 40 characters long._Note_: _Refer to the SEER Program Coding and Staging Manual._RPatientA,C,MRevisedRevisedPatient-ConfidentialRSEER
2260Name--PrefixnamePrefix3Abbreviated title that precedes name in a letter (e.g., "Rev," "Ms").Name Prefix (CoC)..text*Note*: This data item is no longer supported by CoC (as of January 1, 2003)..PatientA,C,MPatient-Confidential.NAACCR12.22011
2270Name--SuffixnameSuffix3Title that follows a patient's last name, such as a generation order or credential status (e.g., "MD," "Jr.").Name Suffix (CoC)..text*Note*: This data item is no longer supported by CoC (as of January 1, 2003)..PatientA,C,MPatient-ConfidentialRNAACCR12.22011
2280Name--AliasnameAlias40Records an alternate name or “AKA” (also known as) used by the patient, if known. Note that the birth surname (AKA maiden name) is entered in Name--Birth Surname \[2232\].Blanks, spaces, hyphens, apostrophes are allowed; do not use other punctuation.Alias (CoC).RtextTruncate name if more than 40 characters long; this field may be updated if the name changes._Note_: This data item is no longer supported by CoC (as of January 1, 2003), but is maintained by NAACCR.RPatientThe update is needed to reflect that Maiden Name is no longer going to be used as of 2021.A,C,MRevisedRevisedPatient-ConfidentialRNAACCR
2290Name--Spouse/ParentnameSpouseParent60NAACCR has not adopted standards for this item. Use varies by area...text.TumorA,C,MPatient-Confidential.NAACCR12.22011
2300Medical Record NumbermedicalRecordNumber15Records medical record number used by the facility to identify the patient.Alphanumeric..*Note:* Other standard abbreviations may be used to indicate departments within the facility for patients without HIM numbers assigned.textRight justified, space filledIn addition to the medical record numberRTumorThis 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.A,C,MPatient-ConfidentialRNAACCR
2315Medicare Beneficiary IdentifiermedicareBeneficiaryIdentifier11Congress passed the Medicare Access and CHIP Reauthorization ACT to remove Social Security Number (SSN) from Medicare ID card and replace the existing Medicare Health Insurance Claim Numbers with a Medicare Beneficiary Identifier (MBI). The MBI will be a randomly generated identifier that will not include a SSN or any personal identifiable information.Alphanumeric, Blank..*Note*: The Medicare Beneficiary Identifier (MBI) is randomly generated and has 11 characters, consisting of numbers and letters, entered without dashes. The MBI format: <https://www.cms.gov/Medicare/New-Medicare-Card/Understanding-the-MBI-with-Format.pdf>textIn addition to MBIR*PatientThe MBI is a step to minimize the risk of identity theft for Medicare beneficiaries and reduce opportunities for fraud. In early 2018, CMB plans to issue new Medicare cards with an MBI. A Health Insurance Claim Number will still be assigned to each Medicare beneficiary and will still be used for internal data exchanges between CMS and the states, but the new MBI must be used in all interactions with the beneficiary, the provider community and all external partners. The collection of the MBI should not change how registries currently collect SSN.A,C,MPatient-Confidential.NAACCR182018
2320Social Security NumbersocialSecurityNumber9Records patient’s social security number. The number is entered without dashes and without any letter suffix. This is not always identical to the Medicare claim number.001010001-899999999, 999999999. Invalid values in this range exist...digits9 digits, no dashesIn addition to social security numberRPatientA,C,MPatient-ConfidentialRSEER
2330Addr at DX--No & StreetaddrAtDxNoStreet60The number and street address or rural mailing address of the patient's residence at the time the reportable tumor was diagnosed. Residential street address should not include PO Boxes. For consolidated records, street address may be based on reported or corrected residential address information.Valid address or UNKNOWNNumber and Street (pre-96 CoC), Patient Address (Number and Street) at Diagnosis (CoC)..textMixed case, embedded spaces, punctuation limited to periods, slashes, hyphens, and pound signs. Left justified, space filledIn addition to valid street addressRTumorThe address is part of the patient's demographic data and has multiple uses. It can be used to evaluate referral patterns, allows for the analysis of cancer cluster concerns, and supports epidemiological studies that use area-based social measures. **Coding Instructions and Summary of USPS Guidelines.** * This field is intended to store street address information for the patient’s physical, residential address. All efforts should be made to find the patient’s true street address and postal code, including reviewing relevant sources outside the medical record if available. A PO Box mailing address should only be recorded when no other address information is available in the medical record and no other information sources are available. * If the patient has multiple tumors, address at diagnosis may be different for each tumor. * Do not update this item if the patient’s residential address changes. Store updated address information in the affiliated current address data items. Only update based on improved information on the residential address at time of diagnosis. For instance, it is appropriate to correct an address during the geocoding or consolidation process. * Refer to the latest _STORE_ for residency rules. * Additional address information such as facility, nursing home, name of apartment complex, or a PO Box used for mailing purposes, should be entered in Addr At Dx--Supplementl \[2335\]. * U.S. addresses should conform to the U.S. Postal Service (USPS) Postal Addressing Standards. These standards are referenced in USPS Publication 28, Postal Addressing Standards. The current USPS Pub. 28 may be found and downloaded here: \<[http://pe.usps.gov/cpim/ftp/pubs/Pub28/pub28.pdf](http://pe.usps.gov/cpim/ftp/pubs/Pub28/pub28.pdf)\>. * The address should be fully spelled out with standardized use of abbreviations and punctuation per USPS postal addressing standards (USPS Pub. 28, available at link above). Mixed case allowed. * Canadian addresses should conform to the Canada Postal Guide. The current Canadian Postal Address Standards may be found here: \<[https://www.canadapost.ca/tools/pg/manual/PGaddress-e.pdf](https://www.canadapost.ca/tools/pg/manual/PGaddress-e.pdf)\>. * Punctuation marks should be avoided, except when punctuation is necessary to convey the meaning. Punctuation normally is limited to periods when the period carries meaning (e.g., 39.2 RD), slashes for fractional addresses (e.g., 101 1/2 Main St), and hyphens when the hyphen carries meaning (e.g., 289-01 Montgomery Ave). Use of the pound sign (#) to designate address units should be avoided whenever possible. The preferred notation is as follows: 102 Main St Apt 101. If a pound sign is used, there must be a space between the pound sign and the secondary number (e.g., 425 Flower Blvd # 72). * Abbreviations should be limited to those recognized by USPS standard abbreviations, these include, but are not limited, to the list below: (A complete list of recognized street abbreviations is provided in Appendix C of USPS Pub. 28 available at link above): | Abbreviation | Word | Abbreviation | Word | | --- | --- | --- | --- | | 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 |A,C,MPatient-ConfidentialRSEER
2335Addr at DX--SupplementladdrAtDxSupplementl60Provides the ability to store additional address information such as the name of a place or facility (for example a nursing home, apartment complex, jail or PO Box residential or other mailing address) at the time of diagnosis.Valid address or blankPatient Address (Number and Street) at Diagnosis--Supplemental (CoC)..textMixed case, embedded spaces, punctuation limited to periods, slashes, hyphens, and pound signs. Left justified, space filledRTumorSometimes the registry receives the name of a facility instead of a proper street address containing the street number, name, direction, and other elements necessary to locate an address on a street file for the purpose of geocoding. By having a second street address field to hold address information, the registry can look up and store the street address and not lose the facility name due to a shortage of space. The presence of a second street address field to hold additional address information also aids in follow-up. For instance, Addr At DX--No & Street [2330] should contain a street address only. However, it is important to retain any known PO Box information when linking for cohort studies or patient contact studies. Retaining facility name can also help correct errors in Addr At DX--No & Street [2330] or assist with geocoding or consolidation. Additionally, researchers can use this field to verify if geographic areas of high risk are driven by location of facilities, such as jails, nursing homes, or homeless shelters.   **Instructions for Coding** * Record the name of the place or facility (for example nursing home, apartment complex, prison/jail or group home) of the patient’s residence when the tumor was diagnosed. Do not use this item for information stored in other address items such as Addr At DX--NO & Street [2330]. * Record a full residential PO Box here (including city & zip code) or other non-physical, residential mailing address here. * Record HOMELESS here when the street address used is a shelter or diagnosing facility for persons with no usual residence. * If the patient has multiple tumors, address at diagnosis supplemental may be different for each tumor. * Do not update this item if the patient’s residential address changes. Store updated address information in the affiliated current address data items. Only update based on improved information on the residential address at time of diagnosis. For instance, it is appropriate to correct supplemental address during the geocoding or consolidation process. * Refer to *STORE* for residency rules. A,C,MPatient-ConfidentialRSEER102003
2350Addr Current--No & StreetaddrCurrentNoStreet60The 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](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](http://www.canadapost.ca)\>.Valid address or UNKNOWNPatient Address (Number and Street)-Current (CoC)..textMixed case, embedded spaces, punctuation limited to periods, slashes, hyphens, and pound signs. Left justified, space filled.Patient“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.): | Abbreviation | Word | Abbreviation | Word | | --- | --- | --- | --- | | 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).A,C,MPatient-ConfidentialRSEER
2352Latitudelatitude10Paired 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.Numbers, decimal point, negative sign..textR*TumorLatitude 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"A,C,MSEER; RevisedRevisedPatient-ConfidentialDNAACCR102003
2354Longitudelongitude11Paired 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.Numbers, decimal point, negative sign..textR*TumorLatitude 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"A,C,MSEER; RevisedRevisedPatient-ConfidentialDNAACCR102003
2355Addr Current--SupplementladdrCurrentSupplementl60This 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.Patient Address (Number and Street) Current--Supplemental (CoC)..textMixed case, embedded spaces, punctuation limited to periods, slashes, hyphens, and pound signs. Left justified, space filled.PatientSometimes 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.A,C,MPatient-ConfidentialR*SEER102003
2360Telephonetelephone10Current telephone number with area code for the patient. Number is entered without dashes.Any 10-digit number..*Note:* Prior to Version 5, Follow-Up Contact fields may have been used for patient current telephone in the NAACCR record layout.digits10-digit numberIn addition to valid telephone number.PatientA,C,MPatient-ConfidentialRSEER
2380DC State File NumberdcStateFileNumber12Death certificate identification number as assigned by the vital statistics office in the place recorded in Place of Death [1940].Any characters or blank..textRPatientA,C,MPatient-ConfidentialR*State12.22011
2392Follow-Up Contact--No&StfollowUpContactNost60The 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>...textMixed case, embedded spaces, punctuation limited to periods, slashes, hyphens, and pound signs. Left justified, space filled*Note:* Prior to Version 5, Follow-Up Contact fields may have been used for patient current address in the NAACCR record layout..TumorSometimes 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.A,C,MPatient-Confidential.SEER5.11997
2393Follow-Up Contact--SupplfollowUpContactSuppl60This 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...textMixed case, embedded spaces, punctuation limited to periods, slashes, hyphens, and pound signs. Left justified, space filled.TumorSometimes 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.A,C,MPatient-Confidential.SEER102003
2394Follow-Up Contact--NamefollowUpContactName60First 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...text.TumorSometimes 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.A,C,MPatient-Confidential.SEER5.11997
2410Institution Referred FrominstitutionReferredFrom10Identifies the facility that referred the patient to the reporting facility.10-digit numberFacility Referred From..textRight justified and zero filled*Note*: This item is not supported by CoC as of January 1, 2010, (the respective NPI item is required).In addition to CoC assigned codes.TumorThis 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.A,C,MHospital-Confidential.CoC
2415NPI--Inst Referred FromnpiInstReferredFrom10The 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.10-digit NPI code (9-digit NPI integer plus 1 check digit), blank.RdigitsOnly 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>.TumorThis number is used to document and monitor referral patterns.A,C,MHospital-Confidential.CMS11.12007
2420Institution Referred ToinstitutionReferredTo10Identifies the facility to which the patient was referred for further care.10-digit numberFacility Referred To..textRight justified and zero filled*Note*: This item is not supported by CoC as of January 1, 2010, (the respective NPI item is required).In addition to CoC assigned codes.TumorThis 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.A,C,MHospital-Confidential.CoC
2425NPI--Inst Referred TonpiInstReferredTo10The 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.10-digit NPI code (9-digit NPI integer plus 1 check digit), blank.RdigitsOnly 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>.TumorThis number is used to document and monitor referral patterns.A,C,MHospital-Confidential.CMS11.12007
2440Following RegistryfollowingRegistry10Records the FIN of the registry responsible for following the patient.10-digit number..digitsRight justified and zero filled *Note*: This item is not supported by CoC as of January 1, 2010, (the respective NPI item is required).In addition to CoC assigned codes.TumorThe 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.  A,C,MHospital-ConfidentialRHCoC
2445NPI--Following RegistrynpiFollowingRegistry10The 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.10-digit NPI code (9-digit NPI integer plus 1 check digit), blank..digitsOnly 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>.TumorThe number is essential to NCDB for monitoring data submissions, ensuring the accuracy of data, and identifying areas for special studies.A,C,MHospital-ConfidentialRH*CMS11.12007
2460Physician--ManagingphysicianManaging8Code for the physician who is responsible for the overall management of the patient during diagnosis and/or treatment for this cancer. Registry may use physicians’ medical license numbers or may create individual numbering systems.Attending Physician (pre-96 CoC), Managing Physician (CoC)..textLeft justified*Note*: This item is not supported by CoC as of January 1, 2010, (the respective NPI item is required).In addition to medical license numbers or facility-generated codes.TumorUsed to monitor patient care.A,C,MOther-Confidential.NAACCR
2465NPI--Physician--ManagingnpiPhysicianManaging10The 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.10-digit NPI code (9-digit NPI integer plus 1 check digit), blank..digitsOnly 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>.TumorUsed to monitor patient care.A,C,MOther-Confidential.CMS11.12007
2470Physician--Follow-UpphysicianFollowUp8Code for the physician currently responsible for the patient’s medical care. Registry may use physicians’ medical license numbers or may create individual numbering systems.Follow-Up Physician (pre-96 CoC), Following Physician (CoC)..textLeft justified*Note*: This item is not supported by CoC as of January 1, 2010, (the respective NPI item is required).In addition to medical license numbers or facility-generated codes.TumorUsed to monitor post-treatment patient care.A,C,MOther-ConfidentialRCoC
2475NPI--Physician--Follow-UpnpiPhysicianFollowUp10The 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.10-digit NPI codes (9-digit NPI integer plus 1 check digit), blank..digitsOnly 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>.TumorUsed to monitor post-treatment patient care.A,C,MOther-ConfidentialR*CMS11.12007
2480Physician--Primary SurgphysicianPrimarySurg8Code for physician who performed the most definitive surgical procedure. Registry may use physician’s medical license numbers or may create individual numbering systems.Primary Surgeon (CoC)..textLeft justified*Note*: This item is not supported by CoC as of January 1, 2010, (the respective NPI item is required).In addition to medical license numbers or facility-generated codes.TumorUsed to monitor patient surgical care.A,C,MOther-Confidential.CoC
2485NPI--Physician--Primary SurgnpiPhysicianPrimarySurg10The 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.10-digit NPI code (9-digit NPI integer plus 1 check digit), blank.RdigitsOnly 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>.TumorUsed to monitor patient surgical care.A,C,MOther-Confidential.CMS11.12007
2490Physician 3physician38Code for another physician involved in the care of the patient. Registry may use physicians’ medical license numbers or may create individual numbering systems.Other Physician (pre-96 CoC), Physician #3 (CoC)..textLeft justified *Note*: This item is not supported by CoC as of January 1, 2010, (the respective NPI item is required).In addition to medical license numbers or facility-generated codes.TumorUsed to monitor patient radiotherapy care.A,C,MOther-Confidential.CoC
2495NPI--Physician 3npiPhysician310The 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.10-digit NPI code (9-digit NPI integer plus 1 check digit), blankRadiation Oncologist (CoC).RdigitsOnly 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>.TumorUsed to monitor patient radiotherapy care.A,C,MOther-Confidential.CMS11.12007
2500Physician 4physician48Code for another physician involved in the care of the patient. Registry may use physicians’ medical license numbers or may create individual numbering systems.Other Physician (pre-96 CoC), Physician #4 (CoC)..textLeft justified*Note*: This item is not supported by CoC as of January 1, 2010, (the respective NPI item is required).In addition to medical license numbers or facility-generated codes.TumorUsed to monitor patient medical oncology care.A,C,MOther-Confidential.CoC
2505NPI--Physician 4npiPhysician410The 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.10-digit NPI code (9-digit NPI integer plus 1 check digit), blankMedical Oncologist (CoC).RdigitsOnly 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>.TumorUsed to monitor patient medical oncology care.A,C,MOther-Confidential.CMS11.12007
2508EHR ReportingehrReporting4000Cancer case reports transmitted from electronic health records (EHR) in the HL7 CDA (Clinical Document Architecture) format must adhere to specifications and requirements as defined by the Implementation Guide (IG) which has been adopted by the Office of the National Coordinator of for Health Information Technology. The IG specifies collection and transmission of cancer diagnosis fields including (but not limited to) primary site, histology, behavior, diagnosis date, and staging elements. The IG also specifies transmission of other data documented in the EHR as part of the care of the patient which are also standardized, but are not routinely collected by cancer registries in the same way or as discrete items. Examples of these are procedures, medications, smoking, and vital signs (i.e., height, weight, BMI). Currently, software tools such as CDC’s eMaRC Plus parse some EHR elements and map or translate these fields to NAACCR items. However, some data are not able to be mapped to discrete items. This new proposed field will allow central cancer registries to collect information from the EHR and map these data in the NAACCR record layout so that they can be included in the central registry database and be available to enhance surveillance data.Free text..**Examples of data to be collected in this field:** Family history Practice OID Smoking Status Tobacco Use Vital sign: height Vital sign: weight Vital sign: BMI Provider First Name Provider Last Name Provider Specialty Medication name, code Cancer-direct Procedures name, code, code system, date of procedure Care Plan: planned encounter EHR Vendor name, software and versiontext.TumorCentral cancer registries may wish to integrate EHR data, which are not already in the NAACCR record layout, into their databases. The EHR Reporting Field will allow central cancer registries to capture data that are received from EHR systems as discrete items. Collection of these data in this field will allow central cancer registries to assess ways in which the EHR data can be standardized in the NAACCR record layout in the future.A,C,MOther-Confidential.NAACCR182018
2520Text--DX Proc--PEtextDxProcPe4000Text area for manual documentation from the history and physical examination about the history of the current tumor and the clinical description of the tumor.Neither carriage return nor line feed characters allowed..**Data Item(s) to be verified/validated using the text entered in this field** After manual entry of the text field, ensure that the text entered both agrees with the coded values and clearly justifies the selected codes in the following fields: | **Item name** | **Item number** | | --- | --- | | Date of Diagnosis | 390 | | Primary Site | 400 | | Laterality | 410 | | Histologic Type ICD-O-3 | 522 | | Grade | 440 | | Collaborative Stage variables | 2800-2930 | | Diagnostic confirmation | 490 | | RX Hosp--Surg Prim Site | 670 | | RX Hosp--Scope Reg LN Sur | 672 | | RX Hosp--Surg Oth Rg/Dis | 674 | | RX Summ--Surg Prim Site | 1290 | | RX Summ--Scope Reg LN Sur | 1292 | | RX Summ--Surg Oth Reg/Dis | 1294 | | SEER Summary Stage 2000 | 759 | | SEER Summary Stage 1977 | 760 | | Regional Nodes Positive | 820 | | Regional Nodes Examined | 830 | | RX Date Surgery | 1200 | | Reason for No Surgery | 1340 | | RX Summ--Surg/Rad Seq | 1380 | | RX Summ--Systemic/Sur Seq | 1639 | | Summary Stage 2018 | 764 | | AJCC TNM Data Items | 1001-1036 | | EOD Data Items | 772-776 | | Site-specific SSDI Data Items | 3801-3937 |textFree textR^TumorText documentation is an essential component of a complete electronic report and is heavily utilized for quality control and special studies. Text is needed to justify coded values and to document supplemental information not transmitted within coded values. High-quality text documentation facilitates consolidation of information from multiple reporting sources at the central registry. The text field must contain a description that has been entered by the reporter independently from the code(s). If software generates text automatically from codes, the text cannot be utilized to check coded values. Information documenting the disease process should be entered manually from the medical record **and should not be generated electronically from coded values**.  **Instructions** * Prioritize entered information in the order of the fields listed below. * Text automatically generated from coded data is not acceptable. * NAACCR-approved abbreviations should be utilized (see Appendix G). * Do not repeat information from other text fields. * Additional comments can be continued in empty text fields, including Remarks. For text documentation that is continued from one text field to another, use asterisks or other symbols to indicate the connection with preceding text. * If information is missing from the record, state that it is missing. * Do not include irrelevant information. * Do not include information that the registry is not authorized to collect. _Note:_ For software that allows unlimited text, NAACCR recommends that the software indicate to the reporter the portion of the text that will be transmitted to the central registry.  **Suggestions for text:** * Date of physical exam * Age, sex, race/ethnicity * History that relates to cancer diagnosis * Primary site * Histology (if diagnosis prior to this admission) * Tumor location * Tumor size * Palpable lymph nodes * Record positive and negative clinical findings. Record positive results first * Impression (when stated and pertains to cancer diagnosis) * Treatment planA,MText-DiagnosisRNPCR
2530Text--DX Proc--X-ray/ScantextDxProcXRayScan4000Text area for manual documentation from all X-rays, scan, and/or other imaging examinations that provide information about staging.Neither carriage return nor line feed characters allowed..**Data Item(s) to be verified/validated using the text entered in this field** After manual entry of the text field, ensure that the text entered both agrees with the coded values and clearly justifies the selected codes in the following fields: | **Item name** | **Item number** | | --- | --- | | Date of Diagnosis | 390 | | RxSumm--Dx/Stg Proc | 1350 | | Primary Site | 400 | | Laterality | 410 | | Histology (92-00) ICD-O-2 | 420 | | Histologic Type ICD-O-3 | 522 | | Collaborative Stage variables | 2800-2930 | | SEER Summary Stage 2000 | 759 | | SEER Summary Stage 1977 | 760 | | Summary Stage 2018 | 764 | | AJCC TNM Data Items | 1001-1036 | | EOD Data Items | 772-776 | | Site-specific SSDI Data Items | 3901-3937 |textFree textR^TumorText documentation is an essential component of a complete electronic report and is heavily utilized for quality control and special studies. Text is needed to justify coded values and to document supplemental information not transmitted within coded values. High-quality text documentation facilitates consolidation of information from multiple reporting sources at the central registry. The text field must contain a description that has been entered by the reporter independently from the code(s). If software generates text automatically from codes, the text cannot be utilized to check coded values. Information documenting the disease process should be entered manually from the medical record **and should not be generated electronically from coded values**.  **Instructions** * Prioritize entered information in the order of the fields listed below. * Text automatically generated from coded data is not acceptable. * NAACCR-approved abbreviations should be utilized (see Appendix G). * Do not repeat information from other text fields. * Additional comments can be continued in empty text fields, including Remarks. For text documentation that is continued from one text field to another, use asterisks or other symbols to indicate the connection with preceding text. * If information is missing from the record, state that it is missing. * Do not include irrelevant information. * Do not include information that the registry is not authorized to collect. _Note:_ For software that allows unlimited text, NAACCR recommends that the software indicate to the reporter the portion of the text that will be transmitted to the central registry.  **Suggestions for text:** * Date(s) and type(s) of X-ray/Scan(s) * Primary site * Histology (if given) * Tumor location * Tumor size * Lymph nodes * Record positive and negative clinical findings. Record positive results first * Distant disease or metastasisA,MText-DiagnosisRNPCR
2540Text--DX Proc--ScopestextDxProcScopes4000Text area for manual documentation from endoscopic examinations that provide information for staging and treatment.Neither carriage return nor line feed characters allowed..**Data Item(s) to be verified/validated using the text entered in this field** After manual entry of the text field, ensure that the text entered both agrees with the coded values and clearly justifies the selected codes in the following fields: | **Item name** | **Item number** | | --- | --- | | Date of Diagnosis | 390 | | RX Summ--Dx/Stg Proc | 1350 | | Diagnostic Confirmation | 490 | | Primary Site | 400 | | Laterality | 410 | | Histology (92-00) ICD-O-2 | 420 | | Histologic Type ICD-O-3 | 522 | | Collaborative Stage variables | 2800-2930 | | SEER Summary Stage 1977 | 760 | | SEER Summary Stage 2000 | 759 | | RX Hosp--Surg Prim Site | 670 | | RX Date Surgery | 1200 | | Summary Stage 2018 | 764 | | Ajcc TNM Data Items | 1001-1036 | | EOD Data Items | 772-776 | | Site-specific SSDI Data Items | 3801-3937 |textFree textR^TumorText documentation is an essential component of a complete electronic report and is heavily utilized for quality control and special studies. Text is needed to justify coded values and to document supplemental information not transmitted within coded values. High-quality text documentation facilitates consolidation of information from multiple reporting sources at the central registry. The text field must contain a description that has been entered by the reporter independently from the code(s). If software generates text automatically from codes, the text cannot be utilized to check coded values. Information documenting the disease process should be entered manually from the medical record **and should not be generated electronically from coded values**.  **Instructions** * Prioritize entered information in the order of the fields listed below. * Text automatically generated from coded data is not acceptable. * NAACCR-approved abbreviations should be utilized (see Appendix G). * Do not repeat information from other text fields. * Additional comments can be continued in empty text fields, including Remarks. For text documentation that is continued from one text field to another, use asterisks or other symbols to indicate the connection with preceding text. * If information is missing from the record, state that it is missing. * Do not include irrelevant information. * Do not include information that the registry is not authorized to collect. _Note:_ For software that allows unlimited text, NAACCR recommends that the software indicate to the reporter the portion of the text that will be transmitted to the central registry. **Suggestions for text:** * Date(s) of endoscopic exam(s) * Primary site * Histology (if given) * Tumor location * Tumor size * Record site and type of endoscopic biopsy * Record positive and negative clinical findings. Record positive results firstA,MText-DiagnosisRNPCR
2550Text--DX Proc--Lab TeststextDxProcLabTests4000Text area for manual documentation of information from laboratory examinations other than cytology or histopathology.Neither carriage return nor line feed characters allowed..**Data Item(s) to be verified/validated using the text entered in this field:** After manual entry of the text field, ensure that the text entered both agrees with the coded values and clearly justifies the selected codes in the following fields: | **Item name** | **Item number** | | --- | --- | | Primary Site | 400 | | Grade | 440 | | Diagnostic Confirmation | 490 | | Collaborative Stage variables | 2800-2930 | | Date of Diagnosis | 390 | | Summary Stage 2018 | 764 | | AJCC TNM Data Items | 1001-1036 | | EOD Data Items | 772-776 | | Site-specific SSDI Data Items | 3801-3937 |textFree textR^TumorText documentation is an essential component of a complete electronic report and is heavily utilized for quality control and special studies. Text is needed to justify coded values and to document supplemental information not transmitted within coded values. High-quality text documentation facilitates consolidation of information from multiple reporting sources at the central registry. The text field must contain a description that has been entered by the reporter independently from the code(s). If software generates text automatically from codes, the text cannot be utilized to check coded values. Information documenting the disease process should be entered manually from the medical record **and should not be generated electronically from coded values**.  **Instructions** * Prioritize entered information in the order of the fields listed below. * Text automatically generated from coded data is not acceptable. * NAACCR-approved abbreviations should be utilized (see Appendix G). * Do not repeat information from other text fields. * Additional comments can be continued in empty text fields, including Remarks. For text documentation that is continued from one text field to another, use asterisks or other symbols to indicate the connection with preceding text. * If information is missing from the record, state that it is missing. * Do not include irrelevant information. * Do not include information that the registry is not authorized to collect. _Note:_ For software that allows unlimited text, NAACCR recommends that the software indicate to the reporter the portion of the text that will be transmitted to the central registry.  **Suggestions for text:** * Type of lab test/tissue specimen(s) * Record both positive and negative findings. Record positive test results first. * Information can include tumor markers, serum and urine electrophoresis, special studies, etc. * Date(s) of lab test(s) * Tumor markers included, but are not limited to: * Breast Cancer – Estrogen Receptor Assay (ERA), Progesterone Receptor Assay (PRA), Her2/neu. * Prostate Cancer – Prostatic Specific Antigen (PSA) * Testicular Cancer – Human Chorionic Gonadotropin (hCG), Alpha Fetoprotein (AFP), Lactate Dehydrogenase (LDH)A,MText-DiagnosisRNPCR
2560Text--DX Proc--OptextDxProcOp4000Text area for manual documentation of all surgical procedures that provide information for staging.Neither carriage return nor line feed characters allowed..**Data Item(s) to be verified/validated using the text entered in this field** After manual entry of the text field, ensure that the text entered both agrees with the coded values and clearly justifies the selected codes in the following fields: | **Item name** | **Item number** | | --- | --- | | Date of Diagnosis | 390 | | RX Summ--Dx/Stg Proc | 1350 | | Diagnostic Confirmation | 490 | | Primary Site | 400 | | RX Hosp--Dx/Stg Proc | 740 | | RX Summ--Surg Prim Site | 1290 | | Collaborative Stage variables | 2800-2930 | | SEER Summary Stage 1977 | 760 | | SEER Summary Stage 2000 | 759 | | Reason for No Surgery | 1340 | | Summary Stage 2018 | 764 | | AJCC TNM Data Items | 1001-1036 | | EOD Data Items | 772-776 | | Site-specific SSDI Data Items | 3801-3937 |textFree textR^TumorText documentation is an essential component of a complete electronic report and is heavily utilized for quality control and special studies. Text is needed to justify coded values and to document supplemental information not transmitted within coded values. High-quality text documentation facilitates consolidation of information from multiple reporting sources at the central registry. The text field must contain a description that has been entered by the reporter independently from the code(s). If software generates text automatically from codes, the text cannot be utilized to check coded values. Information documenting the disease process should be entered manually from the medical record **and should not be generated electronically from coded values**.  **Instructions** * Prioritize entered information in the order of the fields listed below. * Text automatically generated from coded data is not acceptable. * NAACCR-approved abbreviations should be utilized (see Appendix G). * Do not repeat information from other text fields. * Additional comments can be continued in empty text fields, including Remarks. For text documentation that is continued from one text field to another, use asterisks or other symbols to indicate the connection with preceding text. * If information is missing from the record, state that it is missing. * Do not include irrelevant information. * Do not include information that the registry is not authorized to collect. _Note:_ For software that allows unlimited text, NAACCR recommends that the software indicate to the reporter the portion of the text that will be transmitted to the central registry.  **Suggestions for text:** * Dates and descriptions of biopsies and all other surgical procedures from which staging information was derived * Number of lymph nodes removed * Size of tumor removed * Documentation of residual tumor * Evidence of invasion of surrounding areas * Reason primary site surgery could not be completedA,MText-DiagnosisRNPCR
2570Text--DX Proc--PathtextDxProcPath4000Text area for manual documentation of information from cytology and histopathology reports.Neither carriage return nor line feed characters allowed..**Data Item(s) to be verified/validated using the text entered in this field** After manual entry of the text field, ensure that the text entered both agrees with the coded values and clearly justifies the selected codes in the following fields: | **Item name** | **Item number** | | --- | --- | | Date of Diagnosis | 390 | | Primary Site | 400 | | Laterality | 410 | | Histologic Type ICD-O-3 | 522 | | Grade | 440 | | Collaborative Stage variables | 2800-2930 | | Diagnostic confirmation | 490 | | RX Hosp--Surg Prim Site | 670 | | RX Hosp--Scope Reg LN Sur | 672 | | RX Hosp--Surg Oth Rg/Dis | 674 | | RX Summ--Surg Prim Site | 1290 | | RX Summ--Scope Reg LN Sur | 1292 | | RX Summ--Surg Oth Reg/Dis | 1294 | | SEER Summary Stage 2000 | 759 | | SEER Summary Stage 1977 | 760 | | Regional Nodes Positive | 820 | | Regional Nodes Examined | 830 | | RX Date Surgery | 1200 | | Reason for No Surgery | 1340 | | RX Summ--Surg/Rad Seq | 1380 | | RX Summ--Systemic/Sur Seq | 1639 | | Summary Stage 2018 | 764 | | AJCC TNM Data Items | 1001-1036 | | Directly-assigned EOD Data Items | 772-776 | | Site-specific SSDI Data Items | 3801-3937 |textFree textR^TumorText documentation is an essential component of a complete electronic report and is heavily utilized for quality control and special studies. Text is needed to justify coded values and to document supplemental information not transmitted within coded values. High-quality text documentation facilitates consolidation of information from multiple reporting sources at the central registry. The text field must contain a description that has been entered by the reporter independently from the code(s). If software generates text automatically from codes, the text cannot be utilized to check coded values. Information documenting the disease process should be entered manually from the medical record **and should not be generated electronically from coded values**.  **Instructions** * Prioritize entered information in the order of the fields listed below. * Text automatically generated from coded data is not acceptable. * NAACCR-approved abbreviations should be utilized (see Appendix G). * Do not repeat information from other text fields. * Additional comments can be continued in empty text fields, including Remarks. For text documentation that is continued from one text field to another, use asterisks or other symbols to indicate the connection with preceding text. * If information is missing from the record, state that it is missing. * Do not include irrelevant information. * Do not include information that the registry is not authorized to collect. _Note:_ For software that allows unlimited text, NAACCR recommends that the software indicate to the reporter the portion of the text that will be transmitted to the central registry.  **Suggestions for text:** * Date(s) of procedure(s) * Anatomic source of specimen * Type of tissue specimen(s) * Tumor type and grade (include all modifying adjectives, i.e., predominantly, with features of, with foci of, elements of, etc.) * Gross tumor size * Extent of tumor spread * Involvement of resection margins * Number of lymph nodes involved and examined * Record both positive and negative findings. Record positive test results first. * Note if pathology report is a slide review or a second opinion from an outside source, i.e., AFIP, Mayo, etc. * Record any additional comments from the pathologist, including differential diagnoses considered and any ruled out or favoredA,MText-DiagnosisRNPCR
2580Text--Primary Site TitletextPrimarySiteTitle100Text area for manual documentation of information regarding the primary site and laterality of the tumor being reported.Neither carriage return nor line feed characters allowed..**Data Item(s) to be verified/validated using the text entered in this field** After manual entry of the text field, ensure that the text entered both agrees with the coded values and clearly justifies the selected codes in the following fields: | **Item name** | **Item number** | | --- | --- | | Primary site | 400 | | Laterality | 410 |textFree textR^TumorText documentation is an essential component of a complete electronic report and is heavily utilized for quality control and special studies. Text is needed to justify coded values and to document supplemental information not transmitted within coded values. High-quality text documentation facilitates consolidation of information from multiple reporting sources at the central registry. The text field must contain a description that has been entered by the reporter independently from the code(s). If software generates text automatically from codes, the text cannot be utilized to check coded values. Information documenting the disease process should be entered manually from the medical record **and should not be generated electronically from coded values**.  **Instructions** * Prioritize entered information in the order of the fields listed below. * Text automatically generated from coded data is not acceptable. * NAACCR-approved abbreviations should be utilized (see Appendix G). * Do not repeat information from other text fields. * Additional comments can be continued in empty text fields, including Remarks. For text documentation that is continued from one text field to another, use asterisks or other symbols to indicate the connection with preceding text. * If information is missing from the record, state that it is missing. * Do not include irrelevant information. * Do not include information that the registry is not authorized to collect. _Note:_ For software that allows unlimited text, NAACCR recommends that the software indicate to the reporter the portion of the text that will be transmitted to the central registry.  **Suggestions for text:** * State the specific location of the primary site, including subsite. * Include available information on tumor lateralityA,MText-DiagnosisRNPCR
2590Text--Histology TitletextHistologyTitle100Text area for manual documentation of information regarding the histologic type, behavior, and grade (differentiation) of the tumor being reported.Neither carriage return nor line feed characters allowed..**Data Item(s) to be verified/validated using the text entered in this field** After manual entry of the text field, ensure that the text entered both agrees with the coded values and clearly justifies the selected codes in the following fields: | **Item name** | **Item number** | | --- | --- | | Histology (92-00) ICD-O-2 | 420 | | Behavior (92-00) ICD-O-2 | 430 | | Histologic Type ICD-O-3 | 522 | | Behavior Code ICD-O-3 | 523 | | Grade | 440 |textFree textR^TumorText documentation is an essential component of a complete electronic report and is heavily utilized for quality control and special studies. Text is needed to justify coded values and to document supplemental information not transmitted within coded values. High-quality text documentation facilitates consolidation of information from multiple reporting sources at the central registry. The text field must contain a description that has been entered by the reporter independently from the code(s). If software generates text automatically from codes, the text cannot be utilized to check coded values. Information documenting the disease process should be entered manually from the medical record **and should not be generated electronically from coded values**.  **Instructions** * Prioritize entered information in the order of the fields listed below. * Text automatically generated from coded data is not acceptable. * NAACCR-approved abbreviations should be utilized (see Appendix G). * Do not repeat information from other text fields. * Additional comments can be continued in empty text fields, including Remarks. For text documentation that is continued from one text field to another, use asterisks or other symbols to indicate the connection with preceding text. * If information is missing from the record, state that it is missing. * Do not include irrelevant information. * Do not include information that the registry is not authorized to collect. _Note:_ For software that allows unlimited text, NAACCR recommends that the software indicate to the reporter the portion of the text that will be transmitted to the central registry.  **Suggestions for text:** * Information on histologic type and behavior * Information on differentiation from scoring systems such as Gleason’s Score, Bloom-Richardson Grade, etc.A,MText-DiagnosisRNPCR
2600Text--StagingtextStaging4000Additional text area for staging information not already entered in other Text fields.Neither carriage return nor line feed characters allowed..**Data Item(s) to be verified/validated using the text entered in this field** After manual entry of the text field, ensure that the text entered both agrees with the coded values and clearly justifies the selected codes in the following fields: | **Item name** | **Item number** | | --- | --- | | RxDate Dx/Stg Proc | 1280 | | Collaborative Stage variables | 2800-2930 | | SEER Summary Stage 1977 | 760 | | SEER Summary Stage 2000 | 759 | | Regional Nodes Positive | 820 | | Regional Nodes Examined | 830 | | RX Hosp--Surg Prim Site | 670 | | RX Summ--Surg Prim Site | 1290 | | RX Hosp--Scope Reg LN Sur | 672 | | RX Summ--Scope Reg LN Sur | 1292 | | RX Hosp--Surg Oth Rg/Dis | 674 | | RX Summ--Surg Oth Reg/Dis | 1294 | | Mult Tum Rpt as One Prim | 444 | | Lateraltiy | 410 |textFree textR^TumorText documentation is an essential component of a complete electronic report and is heavily utilized for quality control and special studies. Text is needed to justify coded values and to document supplemental information not transmitted within coded values. High-quality text documentation facilitates consolidation of information from multiple reporting sources at the central registry. The text field must contain a description that has been entered by the reporter independently from the code(s). If software generates text automatically from codes, the text cannot be utilized to check coded values. Information documenting the disease process should be entered manually from the medical record **and should not be generated electronically from coded values**.  **Instructions** * Prioritize entered information in the order of the fields listed below. * Text automatically generated from coded data is not acceptable. * NAACCR-approved abbreviations should be utilized (see Appendix G). * Do not repeat information from other text fields. * Additional comments can be continued in empty text fields, including Remarks. For text documentation that is continued from one text field to another, use asterisks or other symbols to indicate the connection with preceding text. * If information is missing from the record, state that it is missing. * Do not include irrelevant information. * Do not include information that the registry is not authorized to collect. _Note:_ For software that allows unlimited text, NAACCR recommends that the software indicate to the reporter the portion of the text that will be transmitted to the central registry. **Suggestions for text:** * Date(s) of procedure(s), including clinical procedures, that provided information for assigning stage * Organs involved by direct extension * Size of tumor * Status of margins * Number and sites of positive lymph nodes * Site(s) of distant metastasis * Physician's specialty and commentsA,MText-DiagnosisRNPCR
2610RX Text--SurgeryrxTextSurgery4000Text area for information describing all surgical procedures performed as part of treatment.Neither carriage return nor line feed characters allowed..textFree text**Data Item(s) to be verified/validated using the text entered in this field** After manual entry of the text field, ensure that the text entered both agrees with the coded values and clearly justifies the selected codes in the following fields: | **Item name** | **Item number** | | --- | --- | | Date Initial RX SEER | 1260 | | Date 1st Crs RX CoC | 1270 | | RX Date Surgery | 1200 | | RX Summ--Surg Prim Site | 1290 | | RX Hosp--Surg Prim Site | 670 | | RX Summ--Scope Reg LN Sur | 1292 | | RX Hosp--Scope Reg LN Sur | 672 | | RX Summ--Surg Oth Reg/Dis | 1294 | | RX Hosp--Surg Oth Reg/Dis | 674 | | Reason for No Surgery | 1340 | | RX Summ--Surgical Margins | 1320 | | RX Hosp--Palliative Proc | 3280 | | RX Summ--Palliative Proc | 3270 | | Text--Place of Diagnosis | 2690 | | RX Summ--Surg/Rad Seq | 1380 | | RX Summ--Systemic/Sur Seq | 1639 |R^TumorText documentation is an essential component of a complete electronic report and is heavily utilized for quality control and special studies. Text is needed to justify coded values and to document supplemental information not transmitted within coded values. High-quality text documentation facilitates consolidation of information from multiple reporting sources at the central registry. The text field must contain a description that has been entered by the reporter independently from the code(s). If software generates text automatically from codes, the text cannot be utilized to check coded values. Information documenting the disease process should be entered manually from the medical record **and should not be generated electronically from coded values**.  **Instructions** * Prioritize entered information in the order of the fields listed below. * Text automatically generated from coded data is not acceptable. * NAACCR-approved abbreviations should be utilized (see Appendix G). * Do not repeat information from other text fields. * Additional comments can be continued in empty text fields, including Remarks. For text documentation that is continued from one text field to another, use asterisks or other symbols to indicate the connection with preceding text. * If information is missing from the record, state that it is missing. * Do not include irrelevant information. * Do not include information that the registry is not authorized to collect. _Note:_ For software that allows unlimited text, NAACCR recommends that the software indicate to the reporter the portion of the text that will be transmitted to the central registry.  **Suggestions for text:** * Date of each procedure. * Type(s) of surgical procedure(s), including excisional biopsies and surgery to other and distant sites. * Lymph nodes removed. * Regional tissues removed. * Metastatic sites. * Facility where each procedure was performed. * Record positive and negative findings. Record positive findings first. * Other treatment information, e.g., planned procedure aborted; unknown if surgery performed.A,MText-TreatmentRNPCR
2620RX Text--Radiation (Beam)rxTextRadiation4000Text area for manual documentation of information regarding treatment of the tumor being reported with beam radiation.Neither carriage return nor line feed characters allowed..textFree text**Data Item(s) to be verified/validated using the text entered in this field** After manual entry of the text field, ensure that the text entered both agrees with the coded values and clearly justifies the selected codes in the following fields: | **Item name** | **Item number** | | --- | --- | | Date Initial RX SEER | 1260 | | Date 1st Crs RX CoC | 1270 | | RX Summ--Radiation | 1360 | | RX Summ--Surg/Rad Seq | 1380 | | Reason For No Radiation | 1430 | | RX Date Radiation | 1210 | | Rad Regional RX Modality | 1570 | | RX Hosp--Radiation | 690 | | RX Date Rad Ended | 3220 | | RX Summ--Rad to CNS | 1370 | | Rad--No of Treatment Vol | 1520 | | Rad--Regional Dose cGy | 1510 | | Rad Treatment Volume | 1540 | | Rad Location of RX | 1550 | | Rad Boost RX Modality | 3200 | | Rad Boost Dose cGy | 3210 | | Phase I dose per Fraction | 1501 | | Phase II dose per Fraction | 1511 | | Phase III dose per Fraction | 1521 | | Phase I Number of Fractions | 1503 | | Phase II Number of Fractions | 1513 | | Phase III Number of Fractions | 1523 | | Phase I Radiation Treatment Modality | 1506 | | Phase II Radiation Treatment Modality | 1516 | | Phase III Radiation Treatment Modality | 1526 |R^TumorText documentation is an essential component of a complete electronic report and is heavily utilized for quality control and special studies. Text is needed to justify coded values and to document supplemental information not transmitted within coded values. High-quality text documentation facilitates consolidation of information from multiple reporting sources at the central registry. The text field must contain a description that has been entered by the reporter independently from the code(s). If software generates text automatically from codes, the text cannot be utilized to check coded values. Information documenting the disease process should be entered manually from the medical record **and should not be generated electronically from coded values**.  **Instructions** * Prioritize entered information in the order of the fields listed below. * Text automatically generated from coded data is not acceptable. * NAACCR-approved abbreviations should be utilized (see Appendix G). * Do not repeat information from other text fields. * Additional comments can be continued in empty text fields, including Remarks. For text documentation that is continued from one text field to another, use asterisks or other symbols to indicate the connection with preceding text. * If information is missing from the record, state that it is missing. * Do not include irrelevant information. * Do not include information that the registry is not authorized to collect. _Note:_ For software that allows unlimited text, NAACCR recommends that the software indicate to the reporter the portion of the text that will be transmitted to the central registry. **Suggestions for text:** * Date radiation treatment began * Where treatment was given, e.g., at this facility, at another facility * Type(s) of beam radiation, e.g., Orthovoltage, Cobalt 60, MV X-rays, Electrons, Mixed modalities * Other treatment information, e.g., patient discontinued after 5 treatments; unknown if radiation was givenA,MText-TreatmentRNPCR
2630RX Text--Radiation OtherrxTextRadiationOther4000Text area for manual documentation of information regarding treatment of the tumor being reported with radiation other than beam radiation. This includes brachytherapy and systemic radiation therapy.Neither carriage return nor line feed characters allowed..textFree text**Data Item(s) to be verified/validated using the text entered in this field** After manual entry of the text field, ensure that the text entered both agrees with the coded values and clearly justifies the selected codes in the following fields: | **Item name** | **Item number** | | --- | --- | | Date Initial RX SEER | 1260 | | Date 1st Crs RX CoC | 1270 | | RX Summ--Radiation | 1360 | | RX Summ--Surg/Rad Seq | 1380 | | Reason For No Radiation | 1430 | | RX Date Radiation | 1210 | | Rad Regional RX Modality | 1570 | | RX Hosp--Radiation | 690 | | RX Date Rad Ended | 3220 | | RX Summ--Rad to CNS | 1370 | | Rad--No of Treatment Vol | 1520 | | Rad--Regional Dose cGy | 1510 | | Rad Treatment Volume | 1540 | | Rad Location of RX | 1550 | | Rad Boost RX Modality | 3200 | | Rad Boost Dose cGy | 3210 | | Phase I dose per Fraction | 1501 | | Phase II dose per Fraction | 1511 | | Phase III dose per Fraction | 1521 | | Phase I Number of Fractions | 1503 | | Phase II Number of Fractions | 1513 | | Phase III Number of Fractions | 1523 | | Phase I Radiation Treatment Modality | 1506 | | Phase II Radiation Treatment Modality | 1516 | | Phase III Radiation Treatment Modality | 1526 |R^TumorText documentation is an essential component of a complete electronic report and is heavily utilized for quality control and special studies. Text is needed to justify coded values and to document supplemental information not transmitted within coded values. High-quality text documentation facilitates consolidation of information from multiple reporting sources at the central registry. The text field must contain a description that has been entered by the reporter independently from the code(s). If software generates text automatically from codes, the text cannot be utilized to check coded values. Information documenting the disease process should be entered manually from the medical record **and should not be generated electronically from coded values**. **Instructions** * Prioritize entered information in the order of the fields listed below. * Text automatically generated from coded data is not acceptable. * NAACCR-approved abbreviations should be utilized (see Appendix G). * Do not repeat information from other text fields. * Additional comments can be continued in empty text fields, including Remarks. For text documentation that is continued from one text field to another, use asterisks or other symbols to indicate the connection with preceding text. * If information is missing from the record, state that it is missing. * Do not include irrelevant information. * Do not include information that the registry is not authorized to collect. _Note:_ For software that allows unlimited text, NAACCR recommends that the software indicate to the reporter the portion of the text that will be transmitted to the central registry.  **Suggestions for text:** * Date treatment was started * Where treatment was given, e.g., at this facility, at another facility * Type(s) of nonbeam radiation, e.g., High Dose rate brachytherapy, seed implant, Radioisotopes (I-131) * Other treatment information, e.g., unknown if radiation was givenA,MText-TreatmentRNPCR
2640RX Text--ChemorxTextChemo4000Text area for manual documentation of information regarding chemotherapy treatment of the reported tumor.Neither carriage return nor line feed characters allowed..text**Data Item(s) to be verified/validated using the text entered in this field** After manual entry of the text field, ensure that the text entered both agrees with the coded values and clearly justifies the selected codes in the following fields: | **Item name** | **Item number** | | --- | --- | | Date Initial RX SEER | 1260 | | Date 1st Crs RX CoC | 1270 | | RX Hosp--Chemo | 700 | | RX Date Systemic | 3230 | | RX Summ--Tranplnt/Endocr | 3250 | | RX Summ--Chemo | 1390 | | RX Date Chemo | 1220 | | RX Summ--Systemic/Sur Seq | 1639 |R^TumorText documentation is an essential component of a complete electronic report and is heavily utilized for quality control and special studies. Text is needed to justify coded values and to document supplemental information not transmitted within coded values. High-quality text documentation facilitates consolidation of information from multiple reporting sources at the central registry. The text field must contain a description that has been entered by the reporter independently from the code(s). If software generates text automatically from codes, the text cannot be utilized to check coded values. Information documenting the disease process should be entered manually from the medical record **and should not be generated electronically from coded values**.  **Instructions** * Prioritize entered information in the order of the fields listed below. * Text automatically generated from coded data is not acceptable. * NAACCR-approved abbreviations should be utilized (see Appendix G). * Do not repeat information from other text fields. * Additional comments can be continued in empty text fields, including Remarks. For text documentation that is continued from one text field to another, use asterisks or other symbols to indicate the connection with preceding text. * If information is missing from the record, state that it is missing. * Do not include irrelevant information. * Do not include information that the registry is not authorized to collect. _Note:_ For software that allows unlimited text, NAACCR recommends that the software indicate to the reporter the portion of the text that will be transmitted to the central registry.  **Suggestions for text:** * Date chemotherapy began * Where treatment was given, e.g., at this facility, at another facility * Type of chemotherapy, e.g., name of agent(s) or protocol * Other treatment information, e.g., treatment cycle incomplete, unknown if chemotherapy was givenA,MText-TreatmentRNPCR
2650RX Text--HormonerxTextHormone4000Text area for information about hormonal treatment.Neither carriage return nor line feed characters allowed..textFree text**Data Item(s) to be verified/validated using the text entered in this field** After manual entry of the text field, ensure that the text entered both agrees with the coded values and clearly justifies the selected codes in the following fields: | **Item name** | **Item number** | | --- | --- | | Date Initial RX SEER | 1260 | | Date 1st Crs RX CoC | 1270 | | RX Hosp--Hormone | 710 | | RX Date Systemic | 3230 | | RX Summ--Tranplnt/Endocr | 3250 | | RX Summ--Hormone | 1400 | | RX Date Hormone | 1230 | | RX Summ--Systemic/Sur Seq | 1639 |R^TumorText documentation is an essential component of a complete electronic report and is heavily utilized for quality control and special studies. Text is needed to justify coded values and to document supplemental information not transmitted within coded values. High-quality text documentation facilitates consolidation of information from multiple reporting sources at the central registry. The text field must contain a description that has been entered by the reporter independently from the code(s). If software generates text automatically from codes, the text cannot be utilized to check coded values. Information documenting the disease process should be entered manually from the medical record **and should not be generated electronically from coded values**.  **Instructions** * Prioritize entered information in the order of the fields listed below. * Text automatically generated from coded data is not acceptable. * NAACCR-approved abbreviations should be utilized (see Appendix G). * Do not repeat information from other text fields. * Additional comments can be continued in empty text fields, including Remarks. For text documentation that is continued from one text field to another, use asterisks or other symbols to indicate the connection with preceding text. * If information is missing from the record, state that it is missing. * Do not include irrelevant information. * Do not include information that the registry is not authorized to collect. _Note:_ For software that allows unlimited text, NAACCR recommends that the software indicate to the reporter the portion of the text that will be transmitted to the central registry. **Suggestions for text:** * Date treatment was started * Where treatment was given, e.g., at this facility, at another facility * Type of hormone or antihormone, e.g., Tamoxifen * Type of endocrine surgery or radiation, e.g., orchiectomy * Other treatment information, e.g., treatment cycle incomplete; unknown if hormones were givenA,MText-TreatmentRNPCR
2660RX Text--BRMrxTextBrm4000Text area for manual documentation of information regarding the treatment of the tumor being reported with biological response modifiers or immunotherapy.Neither line break nor line feed characters allowed..text**Data Item(s) to be verified/validated using the text entered in this field** After manual entry of the text field, ensure that the text entered both agrees with the coded values and clearly justifies the selected codes in the following fields: | **Item name** | **Item number** | | --- | --- | | Date Initial RX SEER | 1260 | | Date 1st Crs RX CoC | 1270 | | RX Hosp--BRM | 720 | | RX Date Systemic | 3230 | | RX Summ--Tranplnt/Endocr | 3250 | | RX Summ--BRM | 1410 | | RX Date BRM | 1240 | | RX Summ--Systemic/Sur Seq | 1639 |R^TumorText documentation is an essential component of a complete electronic report and is heavily utilized for quality control and special studies. Text is needed to justify coded values and to document supplemental information not transmitted within coded values. High-quality text documentation facilitates consolidation of information from multiple reporting sources at the central registry. The text field must contain a description that has been entered by the reporter independently from the code(s). If software generates text automatically from codes, the text cannot be utilized to check coded values. Information documenting the disease process should be entered manually from the medical record **and should not be generated electronically from coded values**.  **Instructions** * Prioritize entered information in the order of the fields listed below. * Text automatically generated from coded data is not acceptable. * NAACCR-approved abbreviations should be utilized (see Appendix G). * Do not repeat information from other text fields. * Additional comments can be continued in empty text fields, including Remarks. For text documentation that is continued from one text field to another, use asterisks or other symbols to indicate the connection with preceding text. * If information is missing from the record, state that it is missing. * Do not include irrelevant information. * Do not include information that the registry is not authorized to collect. _Note:_ For software that allows unlimited text, NAACCR recommends that the software indicate to the reporter the portion of the text that will be transmitted to the central registry.  **Suggestions for text:** * Date treatment began * Where treatment was given, e.g., at this facility, at another facility * Type of BRM agent, e.g., Interferon, BCG * BRM procedures, e.g., bone marrow transplant, stem cell transplant * Other treatment information, e.g., treatment cycle incomplete; unknown if BRM was givenA,MText-TreatmentRNPCR
2670RX Text--OtherrxTextOther4000Text area for manual documentation of information regarding the treatment of the tumor being reported with treatment that cannot be defined as surgery, radiation, or systemic therapy. This includes experimental treatments (when the mechanism of action for a drug is unknown), and blinded clinical trials. If the mechanism of action for the experimental drug is known, code to the appropriate treatment field.Neither carriage return nor line feed characters allowed..textFree text**Data Item(s) to be verified/validated using the text entered in this field** After manual entry of the text field, ensure that the text entered both agrees with the coded values and clearly justifies the selected codes in the following fields: | **Item name** | **Item number** | | --- | --- | | Date Initial RX SEER | 1260 | | Date 1st Crs RX CoC | 1270 | | RX Summ--Other | 1420 | | RX Date Other | 1250 | | RX Hosp--Other | 730 |R^TumorText documentation is an essential component of a complete electronic report and is heavily utilized for quality control and special studies. Text is needed to justify coded values and to document supplemental information not transmitted within coded values. High-quality text documentation facilitates consolidation of information from multiple reporting sources at the central registry. The text field must contain a description that has been entered by the reporter independently from the code(s). If software generates text automatically from codes, the text cannot be utilized to check coded values. Information documenting the disease process should be entered manually from the medical record **and should not be generated electronically from coded values**.  **Instructions** * Prioritize entered information in the order of the fields listed below. * Text automatically generated from coded data is not acceptable. * NAACCR-approved abbreviations should be utilized (see Appendix G). * Do not repeat information from other text fields. * Additional comments can be continued in empty text fields, including Remarks. For text documentation that is continued from one text field to another, use asterisks or other symbols to indicate the connection with preceding text. * If information is missing from the record, state that it is missing. * Do not include irrelevant information. * Do not include information that the registry is not authorized to collect. _Note:_ For software that allows unlimited text, NAACCR recommends that the software indicate to the reporter the portion of the text that will be transmitted to the central registry. **Suggestions for text:** * Date treatment was started * Where treatment was given, e.g., at this facility, at another facility * Type of other treatment, e.g., blinded clinical trial, hyperthermia * Other treatment information, e.g., treatment cycle incomplete; unknown if other treatment was givenA,MText-TreatmentRNPCR
2680Text--RemarkstextRemarks4000Text area for information that is given only in coded form elsewhere or for which the abstract provides no other place. Overflow data can also be placed here. Problematic coding issues can also be discussed in this section.Neither carriage return nor line feed characters allowed..textFree text.TumorText documentation is an essential component of a complete electronic report and is heavily utilized for quality control and special studies. Text is needed to justify coded values and to document supplemental information not transmitted within coded values. High-quality text documentation facilitates consolidation of information from multiple reporting sources at the central registry.  **Instructions** * NAACCR-approved abbreviations should be utilized (see Appendix G). * Do not repeat information from other text fields. * Additional comments from other text fields can be continued in the Remarks field. For text documentation that is continued from one text field to another, use asterisks or other symbols to indicate the connection with preceding text. * If information is missing from the record, state that it is missing. * Do not include irrelevant information. * Do not include information that the registry is not authorized to collect. _Note:_ For software that allows unlimited text, NAACCR recommends that the software indicate to the reporter the portion of the text that will be transmitted to the central registry.  **Suggestions for text:** * Smoking history * Family and personal history of cancer * Comorbidities * Information on sequence numbers if a person was diagnosed with another primary out-of-state or before the registry’s reference date * Place of birth * Justification of over-ride flags * Information clarifying anything unusual such as reason for reporting a case seemingly not reportable for that facility or reason for coding numerous fields as “unknown.”A,MText-MiscellaneousRNPCR
2690Text--Place of DiagnosistextPlaceOfDiagnosis60Text area for manual documentation of the facility, physician office, city, state, or county where the diagnosis was made.Neither carriage return nor line feed characters allowedPlace of Diagnosis..textFree text.TumorText documentation is an essential component of a complete electronic report and is heavily utilized for quality control and special studies. Text is needed to justify coded values and to document supplemental information not transmitted within coded values. High-quality text documentation facilitates consolidation of information from multiple reporting sources at the central registry. **Instructions** * Prioritize entered information in the order of the fields listed below. * NAACCR-approved abbreviations should be utilized (see Appendix G). * Do not repeat information from other text fields. * Additional comments can be continued in empty text fields, including Remarks. For text documentation that is continued from one text field to another, use asterisks or other symbols to indicate the connection with preceding text. * If information is missing from the record, state that it is missing. * Do not include irrelevant information. * Do not include information that the registry is not authorized to collect. _Note:_ For software that allows unlimited text, NAACCR recommends that the software indicate to the reporter the portion of the text that will be transmitted to the central registry. **Suggestions for text:** * The complete name of the hospital or the physician office where diagnosis occurred. The initials of a hospital are not adequate. * For out-of-state residents and facilities, include the city and the state where the medical facility is located. **Data Item(s) to be verified/validated using the text entered in this field** After manual entry of the text field, ensure that the text entered both agrees with the coded values and clearly justifies the selected codes in the following fields: **Item Numbers:** 2410, 2420, 500, 540, 610, 670, 740A,MText-Miscellaneous.NPCR
2800CS Tumor SizecsTumorSize3Records the largest dimension or diameter of the **primary tumor** in millimeters.000-999 (site-specific)RH*RHdigitsRight justified, zero filledSee the most current version of the *Collaborative Stage Data Collection System* (<http://cancerstaging.org>),^13^ for rules and site-specific codes and coding structures.RH*TumorTumor size at diagnosis is an independent prognostic indicator for many tumors and it is used by Collaborative Staging to derive some TNM-T codes.A,C,I,MStage/Prognostic FactorsRH*AJCC102003
2810CS ExtensioncsExtension3Identifies 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.000-999 (site-specific)RH*RH*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.digitsRight justified, zero filledSee the most current version of the *Collaborative Stage Data Collection System* (<http://cancerstaging.org>),^13^ for rules and site-specific codes and coding structures.RH*TumorTumor extension at diagnosis is a prognostic indicator used by Collaborative Staging to derive some TNM-T codes and some SEER Summary Stage codes.A,C,I,MStage/Prognostic FactorsRH*AJCC102003
2820CS Tumor Size/Ext EvalcsTumorSizeExtEval1Records how the codes for the two items CS Tumor Size [2800] and CS Extension [2810] were determined, based on the diagnostic methods employed.0-9 (site-specific)CS TS/Ext-Eval, CS Tumor Size/Extension EvaluationRH*RHdigitsSee the most current version of the *Collaborative Stage Data Collection System* (<http://cancerstaging.org>),^13^ for rules and site-specific codes and coding structures.RH*TumorThis 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.A,C,I,MStage/Prognostic FactorsRH*AJCC102003
2830CS Lymph NodescsLymphNodes3Identifies the regional lymph nodes involved with cancer at the time of diagnosis.000-999 (site-specific)CS Lymph Nodes (SEER EOD)RH*RH*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.digitsRight justified, zero filledSee the most current version of the *Collaborative Stage Data Collection System* (<http://cancerstaging.org>),^13^ for rules and site-specific codes and coding structures.RH*TumorThe 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.A,C,I,MStage/Prognostic FactorsRH*AJCC102003
2840CS Lymph Nodes EvalcsLymphNodesEval1Records how the code for CS Lymph Nodes [2830] was determined, based on the diagnostic methods employed.0-9 (site-specific)CS Reg Nodes Eval, CS Regional Nodes EvaluationRH*RHdigitsSee the most current version of the *Collaborative Stage Data Collection System* ([**http://cancerstaging.org**](http://cancerstaging.org)),^13^ for rules and site-specific codes and coding structures.RH*TumorThis 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.A,C,I,MStage/Prognostic FactorsRH*AJCC
2850CS Mets at DXcsMetsAtDx2Identifies the distant site(s) of metastatic involvement at time of diagnosis.00-99 (site-specific)CS Metastasis at DiagnosisRH*RHdigitsRight justified, zero filledSee the most current version of the** **Collaborative Stage Data Collection System** **(<http://cancerstaging.org\>),^13^ for rules and site-specific codes and coding structures.RH*TumorThe 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.A,C,I,MStage/Prognostic FactorsRH*AJCC102003
2851CS Mets at Dx-BonecsMetsAtDxBone1Identifies the presence of distant metastatic involvement of bone at time of diagnosis.0, 1, 8, 9RH*RH*Note:* This includes only the bone, not the bone marrow.digitsSee the most current version of the *Collaborative Stage Data Collection System* (<http://cancerstaging.org>),^13^ for rules and site-specific codes and coding structures..TumorThe 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.A,C,I,MStage/Prognostic FactorsRHAJCC122010
2852CS Mets at Dx-BraincsMetsAtDxBrain1The 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.0, 1, 8, 9RH*RH*Note:* This includes only the brain, not spinal cord or other parts of the central nervous system.digitsSee the most current version of the *Collaborative Stage Data Collection System* (<http://cancerstaging.org>),^13^ for rules and site-specific codes and coding structures..TumorThe 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.A,C,I,MStage/Prognostic FactorsRHAJCC122010
2853CS Mets at Dx-LivercsMetsAtDxLiver1Identifies the presence of distant metastatic involvement of the liver at time of diagnosis.0, 1, 8, 9RH*RH*Note:* This includes only the liver.digitsSee the most current version of the *Collaborative Stage Data Collection System* (<http://cancerstaging.org>),^13^ for rules and site-specific codes and coding structures..TumorThe 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.A,C,I,MStage/Prognostic FactorsRHAJCC122010
2854CS Mets at Dx-LungcsMetsAtDxLung1Identifies the presence of distant metastatic involvement of the lung at time of diagnosis.0, 1, 8, 9RH*RH*Note:* This includes only the lung, not pleura or pleural fluid.digitsSee the most current version of the *Collaborative Stage Data Collection System* (<http://cancerstaging.org>),^13^ for rules and site-specific codes and coding structures..TumorThe 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.A,C,I,MStage/Prognostic FactorsRHAJCC122010
2860CS Mets EvalcsMetsEval1Records how the code for CS Mets at Dx [2850] was determined based on the diagnostic methods employed.0-9 (site-specific)CS Metastasis EvaluationRH*RHdigitsSee the most current version of the *Collaborative Stage Data Collection System* (<http://cancerstaging.org>),^13^ for rules and site-specific codes and coding structures.RH*TumorThis 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.A,C,I,MStage/Prognostic FactorsRH*AJCC102003
2861CS Site-Specific Factor 7csSiteSpecificFactor73Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.000-999 (site-specific)RH*RHdigitsRight justified, zero filledThe 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.RH*TumorSite-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.A,C,I,MStage/Prognostic FactorsRHAJCC122010
2862CS Site-Specific Factor 8csSiteSpecificFactor83Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.000-999 (site-specific)RH*RHdigitsRight justified, zero filledThe 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.RH*TumorSite-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.A,C,I,MStage/Prognostic FactorsRHAJCC122010
2863CS Site-Specific Factor 9csSiteSpecificFactor93Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.000-999 (site-specific)RH*RHdigitsRight justified, zero filledThe 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.RH*TumorSite-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.A,C,I,MStage/Prognostic FactorsRHAJCC122010
2864CS Site-Specific Factor10csSiteSpecificFactor103Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.000-999 (site-specific)RH*RHdigitsRight justified, zero filledThe 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.RH*TumorSite-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.A,C,I,MStage/Prognostic FactorsRHAJCC122010
2865CS Site-Specific Factor11csSiteSpecificFactor113Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.000-999 (site-specific)RH*RHdigitsRight justified, zero filledThe 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.RH*TumorSite-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.A,C,I,MStage/Prognostic FactorsRHAJCC122010
2866CS Site-Specific Factor12csSiteSpecificFactor123Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.000-999 (site-specific)RH*RHdigitsRight justified, zero filledThe 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.RH*TumorSite-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.A,C,I,MStage/Prognostic FactorsRHAJCC122010
2867CS Site-Specific Factor13csSiteSpecificFactor133Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.000-999 (site-specific)RH*RHdigitsRight justified, zero filledThe 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.RH*TumorSite-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.A,C,I,MStage/Prognostic FactorsRHAJCC122010
2868CS Site-Specific Factor14csSiteSpecificFactor143Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.000-999 (site-specific)RH*RHdigitsRight justified, zero filledThe 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.RH*TumorSite-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.A,C,I,MStage/Prognostic FactorsRHAJCC122010
2869CS Site-Specific Factor15csSiteSpecificFactor153Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.000-999 (site-specific)RH*RHdigitsRight justified, zero filledThe 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.RH*TumorSite-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.A,C,I,MStage/Prognostic FactorsRHAJCC122010
2870CS Site-Specific Factor16csSiteSpecificFactor163Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.000-999 (site-specific)RH*RHdigitsRight justified, zero filledThe 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.RH*TumorSite-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.A,C,I,MStage/Prognostic FactorsRHAJCC122010
2871CS Site-Specific Factor17csSiteSpecificFactor173Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.000-999 (site-specific)RH*RHdigitsRight justified, zero filledThe 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.RH*TumorSite-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.A,C,I,MStage/Prognostic FactorsRHAJCC122010
2872CS Site-Specific Factor18csSiteSpecificFactor183Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.000-999 (site-specific)RH*RHdigitsRight justified, zero filledThe 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..TumorSite-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.A,C,I,MStage/Prognostic FactorsRHAJCC122010
2873CS Site-Specific Factor19csSiteSpecificFactor193Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.000-999 (site-specific)RH*RHdigitsRight justified, zero filledThe 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..TumorSite-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.A,C,I,MStage/Prognostic FactorsRHAJCC122010
2874CS Site-Specific Factor20csSiteSpecificFactor203Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.000-999 (site-specific)RH*RHdigitsRight justified, zero filledThe 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..TumorSite-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.A,C,I,MStage/Prognostic FactorsRHAJCC122010
2875CS Site-Specific Factor21csSiteSpecificFactor213Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.000-999 (site-specific)RH*RHdigitsRight justified, zero filledThe 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..TumorSite-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.A,C,I,MStage/Prognostic FactorsRHAJCC122010
2876CS Site-Specific Factor22csSiteSpecificFactor223Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.000-999 (site-specific)RH*RHdigitsRight justified, zero filledThe 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..TumorSite-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.A,C,I,MStage/Prognostic FactorsRHAJCC122010
2877CS Site-Specific Factor23csSiteSpecificFactor233Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.000-999 (site-specific)RH*RHdigitsRight justified, zero filledThe 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..TumorSite-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.A,C,I,MStage/Prognostic FactorsRHAJCC122010
2878CS Site-Specific Factor24csSiteSpecificFactor243Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.000-999 (site-specific)RH*RHdigitsRight justified, zero filledThe 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..TumorSite-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.A,C,I,MStage/Prognostic FactorsRHAJCC122010
2879CS Site-Specific Factor25csSiteSpecificFactor253Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.000-999 (site-specific)RH*RHdigitsRight justified, zero filledThe 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.RH*TumorCS 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.A,C,I,MStage/Prognostic FactorsRHAJCC122010
2880CS Site-Specific Factor 1csSiteSpecificFactor13Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.000-999 (site-specific)RH*RHdigitsRight justified, zero filledThe 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.RH*TumorSite-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.A,C,I,MStage/Prognostic FactorsRHAJCC102003
2890CS Site-Specific Factor 2csSiteSpecificFactor23Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.000-999 (site-specific)RH*RHdigitsRight justified, zero filledThe 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.RH*TumorSite-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.A,C,I,MStage/Prognostic FactorsRHAJCC102003
2900CS Site-Specific Factor 3csSiteSpecificFactor33Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.000-999 (site-specific)RH*RHdigitsRight justified, zero filledThe 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.RH*TumorSite-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.A,C,I,MStage/Prognostic FactorsRHAJCC102003
2910CS Site-Specific Factor 4csSiteSpecificFactor43Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.000-999 (site-specific)RH*RHdigitsRight justified, zero filledThe 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.RH*TumorSite-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.A,C,I,MStage/Prognostic FactorsRHAJCC102003
2920CS Site-Specific Factor 5csSiteSpecificFactor53Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.000-999 (site-specific)RH*RHdigitsRight justified, zero filledThe 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.RH*TumorSite-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.A,C,I,MStage/Prognostic FactorsRHAJCC102003
2930CS Site-Specific Factor 6csSiteSpecificFactor63Identifies additional information needed to generate stage, or prognostic factors that have an effect on stage or survival.000-999 (site-specific)RH*RHdigitsRight justified, zero filledThe 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.RH*TumorSite-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.A,C,I,MStage/Prognostic FactorsRHAJCC102003
2935CS Version Input OriginalcsVersionInputOriginal6This 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.Valid 6-digit CS version numberCS Version 1STRH*RHCS 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.digits6-digit numberSee the most current version of the *Collaborative Stage Data Collection System* (<http://cancerstaging.org>),^13^ for rules and site-specific codes and coding structures.R*TumorOver time, the input codes and instructions for CS items may change. This item identifies the correct interpretation of input CS items.A,C,I,MStage/Prognostic FactorsRH*AJCC
2936CS Version DerivedcsVersionDerived6This 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.Valid 6-digit CS version numberCS Version LatestDHDHCS 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.text6-digit numberSee the most current version of the *Collaborative Stage Data Collection System* (<http://cancerstaging.org>),^13^ for rules and site-specific codes and coding structures.RH*TumorThe 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.A,C,I,MStage/Prognostic FactorsD*AJCC
2937CS Version Input CurrentcsVersionInputCurrent6This 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.Valid 6-digit CS version numberRH*RHCS 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.digits6-digit numberSee the most current version of the *Collaborative Stage Data Collection System* (<http://cancerstaging.org>),^13^ for rules and site-specific codes and coding structures.R*TumorOver time, the input codes and instructions for CS items may change. This item identifies the correct interpretation of input CS items.A,C,I,MStage/Prognostic FactorsRH*AJCC122010
2940Derived AJCC-6 TderivedAjcc6T2This data item belongs to the Collaborative Stage (CS) Data Collection System which is based on the *AJCC Cancer Staging Manual*, 6th and 7th editions. AJCC T, N, M plus descriptors and AJCC staging components are composed of combinations of characters, numbers, and/or special characters and can be of varying lengths. To more easily handle these components a numeric code was assigned to each unique category for each T, N, M plus descriptors and AJCC stage for 6th and 7th editions. This field contains the numeric representation for the AJCC 6th edition “T” and is derived from CS coded fields using the CS algorithm. This numeric representation is referred to as the “storage” code and its associated label is referred to as the “display” code. Explanations of the “storage” codes and their corresponding “display” codes can be found in the most current version of the *Collaborative Stage Data Collection System* (<https://cancerstaging.org/cstage/Pages/default.aspx>).^13^ The display code should be used for display on the screen and in reports.Site-specific (derived from Collaborative Stage fields), blankDerived AJCC T, Derived TDHDHdigitsSee the most current version of the *Collaborative Stage Data Collection System* (<https://cancerstaging.org/cstage/Pages/default.aspx>),^13^ for rules and site-specific codes and coding structures..TumorThe 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.A,C,I,MStage/Prognostic FactorsDHAJCC102003
2950Derived AJCC-6 T DescriptderivedAjcc6TDescript1This data item belongs to the Collaborative Stage (CS) Data Collection System which is based on the *AJCC Cancer Staging Manual*, 6th and 7th editions. AJCC T, N, M plus descriptors and AJCC staging components are composed of combinations of characters, numbers, and/or special characters and can be of varying lengths. To more easily handle these components a numeric code was assigned to each unique category for each T, N, M plus descriptors and AJCC stage for 6th and 7th editions. This field contains the numeric representation for the AJCC 6th edition “T Descriptor” and is derived from CS coded fields using the CS algorithm. This numeric representation is referred to as the “storage” code and its associated label is referred to as the “display” code. Explanations of the “storage” codes and their corresponding “display” codes can be found in the most current version of the *Collaborative Stage Data Collection System* (<https://cancerstaging.org/cstage/Pages/default.aspx>).^13^ The display code should be used for display on the screen and in reports.c, p, a, y, N, and blank (derived from Collaborative Stage fields)Derived 6 T Descriptor Storage Code, Derived AJCC T DescriptorDHDHtextSee the most current version of the *Collaborative Stage Data Collection System* (<https://cancerstaging.org/cstage/Pages/default.aspx>),^13^ for rules and site-specific codes and coding structures..TumorThe 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.A,C,I,MStage/Prognostic FactorsDHAJCC102003
2960Derived AJCC-6 NderivedAjcc6N2This data item belongs to the Collaborative Stage (CS) Data Collection System which is based on the *AJCC Cancer Staging Manual*, 6th and 7th editions. AJCC T, N, M plus descriptors and AJCC staging components are composed of combinations of characters, numbers, and/or special characters and can be of varying lengths. To more easily handle these components a numeric code was assigned to each unique category for each T, N, M plus descriptors and AJCC stage for 6th and 7th editions. This field contains the numeric representation for AJCC 6th edition “N” and is derived from CS coded fields using the CS algorithm. This numeric representation is referred to as the “storage” code and its associated label is referred to as the “display” code. Explanations of the “storage” codes and their corresponding “display” codes can be found in the most current version of the *Collaborative Stage Data Collection System* (<https://cancerstaging.org/cstage/Pages/default.aspx>).^13^ The display code should be used for display on the screen and in reports.Site-specific (derived from Collaborative Stage fields), blankDerived 6 N Descriptor Storage Code, Derived AJCC NDHDHdigitsSee the most current version of the *Collaborative Stage Data Collection System* (<https://cancerstaging.org/cstage/Pages/default.aspx>),^13^ for rules and site-specific codes and coding structures..TumorThe 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.A,C,I,MStage/Prognostic FactorsDHAJCC102003
2970Derived AJCC-6 N DescriptderivedAjcc6NDescript1This data item belongs to the Collaborative Stage (CS) Data Collection System which is based on the *AJCC Cancer Staging Manual*, 6th and 7th editions. AJCC T, N, M plus descriptors and AJCC staging components are composed of combinations of characters, numbers, and/or special characters and can be of varying lengths. To more easily handle these components a numeric code was assigned to each unique category for each T, N, M plus descriptors and AJCC stage for 6th and 7th editions. This field contains the numeric representation for AJCC 6th edition “N Descriptor” and is derived from CS coded fields using the CS algorithm. This numeric representation is referred to as the “storage” code and its associated label is referred to as the “display” code. Explanations of the “storage” codes and their corresponding “display” codes can be found in the most current version of the *Collaborative Stage Data Collection System* (<https://cancerstaging.org/cstage/Pages/default.aspx>).^13^ The display code should be used for display on the screen and in reports.c, p, a, y, N, and blank (derived from Collaborative Stage fields)Derived 6 N Descriptor Storage Code, Derived AJCC N DescriptorDHDHtextSee the most current version of the *Collaborative Stage Data Collection System* (<https://cancerstaging.org/cstage/Pages/default.aspx>),^13^ for rules and site-specific codes and coding structures..TumorThe 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.A,C,I,MStage/Prognostic FactorsDHAJCC102003
2980Derived AJCC-6 MderivedAjcc6M2This data item belongs to the Collaborative Stage (CS) Data Collection System which is based on the AJCC Cancer Staging Manual, 6th and 7th editions. AJCC T, N, M plus descriptors and AJCC staging components are composed of combinations of characters, numbers, and/or special characters and can be of varying lengths. To more easily handle these components a numeric code was assigned to each unique category for each T, N, M plus descriptors and AJCC stage for 6th and 7th editions. This field contains the numeric representation for AJCC 6th edition “M” and is derived from CS coded fields using the CS algorithm. This numeric representation is referred to as the “storage” code and its associated label is referred to as the “display” code. Explanations of the “storage” codes and their corresponding “display” codes can be found in the most current version of the Collaborative Stage Data Collection System (<https://cancerstaging.org/cstage/Pages/default.aspx>).^13^ The display code should be used for display on the screen and in reports.Site-specific (derived from Collaborative Stage fields), blankDerived 6 M Storage Code, Derived AJCC MDHDHdigitsSee the most current version of the *Collaborative Stage Data Collection System* (<https://cancerstaging.org/cstage/Pages/default.aspx>),^13^ for rules and site-specific codes and coding structures..TumorThe 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.A,C,I,MStage/Prognostic FactorsDHAJCC102003
2990Derived AJCC-6 M DescriptderivedAjcc6MDescript1This data item belongs to the Collaborative Stage (CS) Data Collection System which is based on the *AJCC Cancer Staging Manual*, 6th and 7th editions. AJCC T, N, M plus descriptors and AJCC staging components are composed of combinations of characters, numbers, and/or special characters and can be of varying lengths. To more easily handle these components a numeric code was assigned to each unique category for each T, N, M plus descriptors and AJCC stage for 6th and 7th editions. This field contains the numeric representation for AJCC 6th edition “M Descriptor” and is derived from CS coded fields using the CS algorithm. This numeric representation is referred to as the “storage” code and its associated label is referred to as the “display” code. Explanations of the “storage” codes and their corresponding “display” codes can be found in the most current version of the *Collaborative Stage Data Collection System* (<https://cancerstaging.org/cstage/Pages/default.aspx>).^13^ The display code should be used for display on the screen and in reports.c, p, a, y, N, and blank (derived from Collaborative Stage fields)Derived 6 M Descriptor Storage Code, Derived AJCC M DescriptorDHDHtextSee the most current version of the *Collaborative Stage Data Collection System* (<https://cancerstaging.org/cstage/Pages/default.aspx>),^13^ for rules and site-specific codes and coding structures..TumorThe 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.A,C,I,MStage/Prognostic FactorsDHAJCC
3000Derived AJCC-6 Stage GrpderivedAjcc6StageGrp2This data item belongs to the Collaborative Stage (CS) Data Collection System which is based on the *AJCC Cancer Staging Manual*, 6th and 7th editions. AJCC T, N, M plus descriptors and AJCC staging components are composed of combinations of characters, numbers, and/or special characters and can be of varying lengths. To more easily handle these components a numeric code was assigned to each unique category for each T, N, M plus descriptors and AJCC stage for 6th and 7th editions. This field contains the numeric representation for the AJCC 6th edition “Stage Group” and is derived from CS coded fields using the CS algorithm. This numeric representation is referred to as the “storage” code and its associated label is referred to as the “display” code. Explanations of the “storage” codes and their corresponding “display” codes can be found in the most current version of the *Collaborative Stage Data Collection System* (<https://cancerstaging.org/cstage/Pages/default.aspx>).^13^ The display code should be used for display on the screen and in reports.Site-specific (derived from Collaborative Stage fields)Derived 6 Stage Group Storage Code, Derived AJCC Stage GroupDHDHdigitsSee the most current version of the *Collaborative Stage Data Collection System* (<https://cancerstaging.org/cstage/Pages/default.aspx>),^13^ for rules and site-specific codes and coding structures..TumorThe 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.A,C,I,MStage/Prognostic FactorsDHAJCC102003
3010Derived SS1977derivedSs19771This item is the derived “SEER Summary Stage 1977” from the CS algorithm (or EOD codes) effective with 2004 diagnosis.0-5, 7, 8, 9 (derived from Collaborative Stage fields)Derived SEER Summary Stage 1977DHDHdigitsSee the most current version of the** **Collaborative Stage Data Collection System** **(<https://cancerstaging.org/cstage/Pages/default.aspx\>),^13^ for rules and site-specific codes and coding structures..TumorThe 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.A,C,I,MUpdated SEERStage/Prognostic FactorsDHAJCC102003
3020Derived SS2000derivedSs20001This item is the derived “SEER Summary Stage 2000” from the CS algorithm (or EOD codes) effective with 2004 diagnosis.0-5, 7, 8, 9 (derived from Collaborative Stage fields)Derived SEER Summary Stage 2000DHDHdigitsSee the most current version of the *Collaborative Stage Data Collection System* (<https://cancerstaging.org/cstage/Pages/default.aspx>),^13^ for rules and site-specific codes and coding structures.RH*TumorThe 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.A,C,I,MStage/Prognostic FactorsDHAJCC102003
3030Derived AJCC--FlagderivedAjccFlag1Flag to indicate whether the derived AJCC stage was derived from CS or EOD codes.1, 2, blankAJCC Conversion Flag.DHdigits.TumorA,C,I,MStage/Prognostic FactorsDHAJCC102003
3040Derived SS1977--FlagderivedSs1977Flag1Flag to indicate whether the derived SEER Summary Stage 1977 was derived from CS or EOD codes.1, 2, blankSS1977 Conversion Flag.DHdigitsSee the most current version of the** **Collaborative Stage Data Collection System** **(<https://cancerstaging.org/cstage/Pages/default.aspx\>),^13^ for rules and site-specific codes and coding structures..TumorThe 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.A,C,I,MUpdated SEERStage/Prognostic FactorsDHAJCC102003
3050Derived SS2000--FlagderivedSs2000Flag1Flag to indicate whether the derived SEER Summary Stage 2000 was derived from CS or EOD codes.1, 2, blankSS2000 Conversion Flag.DHdigitsSee the most current version of the** **Collaborative Stage Data Collection System** **(<https://cancerstaging.org/cstage/Pages/default.aspx\>),^13^ for rules and site-specific codes and coding structures.RH*TumorThe 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.A,C,I,MUpdated SEERStage/Prognostic FactorsDHAJCC102003
3100Archive FINarchiveFin10This field identifies the CoC Facility Identification Number (FIN) of the facility at the time it originally accessioned the tumor.10-digit number.RdigitsRight justified, zero filled.TumorWhen 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.A,C,I,MHospital-Specific.CoC102003
3105NPI--Archive FINnpiArchiveFin10This 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.10-digit NPI code (9-digit NPI integer plus 1 check digit), blank.RdigitsOnly 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>.TumorThe NPI-Archive FIN is the functional equivalent of Archive FIN [3100].A,C,I,MHospital-Specific.CMS11.12007
3165ICD Revision ComorbidicdRevisionComorbid1This item indicates the coding system in which the Comorbidities and Complications (secondary diagnoses) codes are provided.0, 1, 9, blankICD Revision Comorbidities..digits.TumorThe 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 *[STORE](http://www.facs.org/cancer/coc/fordsmanual.html)* would be re-assessed at the same time.A,C,I,MStage/Prognostic Factors.CoC112006
3170RX Date Mst Defn SrgrxDateMostDefinSurg8Date of most definitive surgical resection of the primary site performed as part of the first course of treatment. See [**Data Descriptor Table**](https://apps.naaccr.org/data-dictionary/data-dictionary/version=24/chapter-view/data-descriptor-table/) for date format. Use RX DATE MST DEFN SRG FLAG \[3171\] if there is no appropriate or known date for this item.   Formerly RX Date--Most Defin Surg.Valid datesDate of Most Definitive Surgical Resection of the Primary Site, RX Date--Most Defin Surg.RdateYYYYMMDDR*TumorThis item is used to measure lag time between diagnosis and the most definitive surgery of the primary site or survival following the procedure. It also is used in conjunction with RX Date Surg Disch \[3180\] to calculate the duration of hospitalization following the most definitive primary site surgical procedure to evaluate treatment efficacy.A,C,I,MUpdated SEERTreatment-1st CourseR*CoC102003
3180RX Date Surg DischrxDateSurgicalDisch8Records the date the patient was discharged following primary site surgery. The date corresponds to the event recorded in RX Date Mst Defn Srg \[3170\]. See Chapter [**Data Descriptor Table**](https://apps.naaccr.org/data-dictionary/data-dictionary/version=24/chapter-view/data-descriptor-table/) for date format. Use RX DATE SURG DISCH FLAG \[3181\] if there is no appropriate or known date for this item.   Formerly RX Date--Surgical Disch.Valid datesDate of Surgical Discharge, RX Date--Surgical Disch.RdateYYYYMMDD.TumorLength of stay is an important quality-of-care and financial measure among hospital administrations, those who fund public and private health care, and public health users. This date, in conjunction with the data item RX Date Mst Defn Srg \[3170\], will allow for the calculation of a patient’s length of hospitalization associated with primary site surgery.A,C,I,MTreatment-1st Course.CoC102003
3190Readm Same Hosp 30 DaysreadmSameHosp30Days1Records a readmission to the same hospital within 30 days of discharge following hospitalization for surgical resection of the primary site for the same illness.0-3, 9Readmission to the Same Hospital Within 30 Days of Surgical Discharge.Rdigits.TumorThis data item provides information related to the quality of care. A patient may have a readmission related to the primary diagnosis on discharge if the length of stay was too short, and then needed to return due to problems or complications. A patient may also need to be readmitted if discharge planning and/or follow-up instructions were ineffective. It is important to distinguish a planned from an unplanned readmission, since a planned readmission is not an indicator of quality of care problems.A,C,I,MTreatment-1st Course.CoC102003
3220RX Date Rad EndedrxDateRadiationEnded8The date on which the patient completes or receives the last radiation treatment at any facility. See [**Data Descriptor Table**](https://apps.naaccr.org/data-dictionary/data-dictionary/version=24/chapter-view/data-descriptor-table/) for date format. Use RX DATE RAD ENDED FLAG \[3221\] if there is no appropriate or known date for this item.   Formerly RX Date--Radiation Ended.Valid datesDate Radiation Ended, RX Date--Radiation Ended.RdateYYYYMMDD.TumorThe length of time over which radiation therapy is administered to a patient is a factor in tumor control and treatment morbidity. It is useful in evaluating the quality-of-care and the success of patient support programs designed to maintain continuity of treatment.A,C,I,MTreatment-1st Course.CoC102003
3230RX Date SystemicrxDateSystemic8Date of initiation of systemic therapy that is part of the first course of treatment. Systemic therapy includes the administration of chemotherapy agents, hormone agents, biological response modifiers, bone marrow transplants, stem cell harvests, and surgical and/or radiation endocrine therapy. See [**Data Descriptor Table**](https://apps.naaccr.org/data-dictionary/data-dictionary/version=24/chapter-view/data-descriptor-table/) for date format. Use RX DATE SYSTEMIC FLAG \[3231\] if there is no appropriate or known date for this item.   Formerly RX Date--Systemic.Valid datesDate Systemic Therapy Started, RX Date--Systemic.RdateYYYYMMDD.TumorCollecting dates for each treatment modality allows the sequencing of multiple treatments and aids in the evaluation of time intervals from diagnosis to treatment and from treatment to recurrence.A,C,I,MTreatment-1st CourseRCCoC102003
3250RX Summ--Transplnt/EndocrrxSummTransplntEndocr2Identifies systemic therapeutic procedures administered as part of the first course of treatment at this and all other facilities. If none of these procedures were administered then this item records the reason they were not performed. These include bone marrow transplants, stem cell harvests, surgical and/or radiation endocrine therapy.00, 10-12, 20, 30, 40, 82, 85-88, 99Hematologic Transplant and Endocrine Procedures.RdigitsRight justified, zero filledRefer to the most recent version of *STORE* for additional instructions.RTumorThis data item allows the evaluation of patterns of treatment, which involve the alteration of the immune system or change the patient’s response to tumor cells but do not involve the administration of antineoplastic agents.A,C,I,MTreatment-1st CourseRCoC102003
3270RX Summ--Palliative ProcrxSummPalliativeProc1Identifies any care provided in an effort to palliate or alleviate symptoms. Palliative care is performed to relieve symptoms and may include surgery, radiation therapy, systemic therapy (chemotherapy, hormone therapy, or other systemic drugs), and/or pain management therapy.0-7, 9Palliative Care, Palliative Procedure.Rdigits.TumorThis data item allows reporting facilities to track care that is considered palliative rather than diagnostic or curative intent.A,C,I,MTreatment-1st Course.CoC102003
3280RX Hosp--Palliative ProcrxHospPalliativeProc1Identifies care provided at the reporting facility in an effort to palliate or alleviate symptoms. Palliative procedures may include surgery, radiation therapy, systemic therapy (chemotherapy, hormone therapy, or other systemic drugs), and/or pain management.0-7, 9Palliative Care at this Facility, Palliative Procedure at this Facility.Rdigits.TumorThis data item allows reporting facilities to track care that is considered palliative rather than diagnostic or curative in intent. If central registries wish to study types of palliative care given at particular facilities, the facility-level fields must be used. Facility-specific fields allow studies of detailed referral patterns and treatment by type of healthcare setting. Knowing what palliative procedures and care was performed at a particular facility also helps resolve consolidation issues.A,C,I,MHospital-Specific.CoC102003
3300RuralUrban Continuum 1993ruralurbanContinuum19932The RuralUrban Continuum (1993) codes (usually known as the Beale Codes) separate counties into four metropolitan and six non-metropolitan categories, based on the size their populations and form a classification scheme that distinguishes metropolitan counties by size and non-metropolitan counties by degree of urbanization and proximity to metro areas. These codes can be derived electronically, using patients’ state and county at diagnosis, so registrars do not need to provide them. FIPS state and county code mappings to Beale Codes can be obtained in an Excel file at <http://www.ers.usda.gov/data-products/rural-urban-continuum-codes.aspx> . The code is a 10-point continuum, transmitted in standard NAACCR record form with a leading 0, (00-09). Abstractors do not enter these codes. Areas that are not included in the Rural-Urban Continuum code table, such as Canadian provinces/territories and U.S. territories (other than Puerto Rico) will be coded 98. Records for non-residents of the state of the reporting institution (County at DX = 998) also will be coded 98. If Addr at DX--State is XX, YY or ZZ, or if County at DX = 999, the Rural-Urban Continuum will be coded 99.00-09, 98, 99, blankBeale Code..digitsRight justified, zero filledDTumorCategorizing counties by population size helps researchers investigate geographic correlates of the burden of cancer in the area of interest.A,C,I,MDemographicDNAACCR102003
3310RuralUrban Continuum 2003ruralurbanContinuum20032The RuralUrban Continuum (2003) codes (usually known as the Beale Codes) separate counties into four metropolitan and six non-metropolitan categories, based on the size their populations and form a classification scheme that distinguishes metropolitan counties by size and non-metropolitan counties by degree of urbanization and proximity to metro areas. These codes can be derived electronically, using patients’ state and county at diagnosis, so registrars do not need to provide them. FIPS state and county code mappings to Beale Codes can be obtained in an Excel file at <http://www.ers.usda.gov/data-products/rural-urban-continuum-codes.aspx>. The code is a 9-point continuum, transmitted in standard NAACCR record form with a leading 0, (01-09). Abstractors do not enter these codes. Areas that are not included in the Rural-Urban Continuum code table, such as Canadian provinces/territories and U.S. territories (other than Puerto Rico) will be coded 98. Records for non-residents of the state of the reporting institution (County at DX = 998) also will be coded 98. If Addr at DX--State is XX, YY or ZZ, or if County at DX = 999, the Rural-Urban Continuum will be coded 99.01-09, 98, 99, blankBeale Code, RuralUrban Continuum 2000..digitsRight justified, zero filledDTumorCategorizing counties by population size helps researchers investigate geographic correlates of the burden of cancer in the area of interest.A,C,I,MDemographicDNAACCR102003
3312RuralUrban Continuum 2013ruralurbanContinuum20132Comment: The RuralUrban Continuum (2013) codes separate counties into four metropolitan and six non-metropolitan categories, based on the size their populations and form a classification scheme that distinguishes metropolitan counties by size and non-metropolitan counties by degree of urbanization and proximity to metro areas. These codes can be derived electronically, using patients’ state and county at diagnosis, so registrars do not need to provide them. FIPS state and county code mappings to Beale Codes can be obtained in an Excel file athttp://www.ers.usda.gov/Data/RuralUrbanContinuumCodes. The code is a 9-point continuum, transmitted in standard NAACCR record form with a leading 0, (01-09). Abstractors do not enter these codes. Areas that are not included in the Rural-Urban Continuum code table, such as Canadian provinces/territories and U.S. territories (other than Puerto Rico) will be coded 98. Records for non-residents of the state of the reporting institution (County at DX = 998) also will be coded 98. If Addr at DX–State is XX, YY or ZZ, or if County at DX = 999, the Rural-Urban Continuum will be coded 99.01-09, 98, 99, blankBeale Code..digitsRight justified, zero-filledDTumorCategorizing counties by population size helps researchers investigate geographic correlates of the burden of cancer in the area of interest.A,C,I,MDemographicDNAACCR162016
3400Derived AJCC-7 TderivedAjcc7T3This item is the derived AJCC “T” staging element from coded fields using the CS algorithm. Effective for cases diagnosed 2010+.000-999Derived 7 T Storage CodeDHDHdigitsRight justified, zero filledSee the most current version of the *Collaborative Stage Data Collection System* (<https://cancerstaging.org/cstage/Pages/default.aspx>),^13^ for rules and site-specific codes and coding structures.RH*TumorDerived AJCC-7 T can be used to evaluate disease spread at diagnosis, plan and track treatment patterns, and analyze outcomes.A,C,I,MStage/Prognostic FactorsDHAJCC122010
3402Derived AJCC-7 T DescriptderivedAjcc7TDescript1This item is the derived AJCC “T Descriptor” from coded fields using the CS algorithm. Effective for cases diagnosed 2010+.c, p, a, y, N, blankDerived 7 T Descript Storage CodeDHDHtextSee the most current version of the *Collaborative Stage Data Collection System* (<https://cancerstaging.org/cstage/Pages/default.aspx>),^13^ for rules and site-specific codes and coding structures.RH*TumorDerived AJCC-7 T Descript can be used in analysis to differentiate the timing of staging with respect to the treatment process.A,C,I,MStage/Prognostic FactorsDHAJCC122010
3410Derived AJCC-7 NderivedAjcc7N3This item is the derived AJCC “N” staging element from coded fields using the CS algorithm. Effective for cases diagnosed 2010+.000-999Derived 7 N Storage CodeDHDHdigitsRight justified, zero filledSee the most current version of the *Collaborative Stage Data Collection System* (<https://cancerstaging.org/cstage/Pages/default.aspx>),^13^ for rules and site-specific codes and coding structures.RH*TumorThe CS Derived AJCC-7 N can be used to evaluate disease spread at diagnosis, plan and track treatment patterns, and analyze outcomes.A,C,I,MStage/Prognostic FactorsDHAJCC122010
3412Derived AJCC-7 N DescriptderivedAjcc7NDescript1This item is the derived AJCC “N Descriptor” from coded fields using the CS algorithm. Effective for cases diagnosed 2010+.c, p, a, y, N, blankDerived 7 N Descript Storage CodeDHDHtextSee the most current version of the *Collaborative Stage Data Collection System* (<https://cancerstaging.org/cstage/Pages/default.aspx>),^13^ for rules and site-specific codes and coding structures.RH*TumorDerived AJCC-7 N Descript can be used in analysis to differentiate the timing of staging with respect to the treatment process.A,C,I,MStage/Prognostic FactorsDHAJCC122010
3420Derived AJCC-7 MderivedAjcc7M3This item is the derived AJCC “M” staging element from coded fields using the CS algorithm. Effective for cases diagnosed 2010+.000-999Derived 7 M Storage CodeDHDHdigitsRight justified, zero filledSee the most current version of the *Collaborative Stage Data Collection System* (<https://cancerstaging.org/cstage/Pages/default.aspx>),^13^ for rules and site-specific codes and coding structures.RH*TumorDerived AJCC-7 M can be used to evaluate disease spread at diagnosis, plan and track treatment patterns, and analyze outcomes.A,C,I,MStage/Prognostic FactorsDHAJCC122010
3422Derived AJCC-7 M DescriptderivedAjcc7MDescript1This item is the derived AJCC “M Descriptor” from coded fields using the CS algorithm. Effective for cases diagnosed 2010+.c, p, a, y, N, blankDerived 7 M Descript Storage CodeDHDHtextSee the most current version of the *Collaborative Stage Data Collection System* (<https://cancerstaging.org/cstage/Pages/default.aspx>),^13^ for rules and site-specific codes and coding structures.RH*TumorDerived AJCC-7 M Descript can be used in analysis to differentiate the timing of staging with respect to the treatment process.A,C,I,MStage/Prognostic FactorsDHAJCC122010
3430Derived AJCC-7 Stage GrpderivedAjcc7StageGrp3This item is the derived AJCC “Stage Group” from coded fields using the CS algorithm. Effective for cases diagnosed 2010+.000-999Derived 7 Stage Grp Storage CodeDHDHdigitsRight justified, zero filledSee the most current version of the *Collaborative Stage Data Collection System* (<https://cancerstaging.org/cstage/Pages/default.aspx>),^13^ for rules and site-specific codes and coding structures.RH*TumorThe CS Derived AJCC-7 Stage Group can be used to evaluate disease spread at diagnosis, plan and track treatment patterns, and analyze outcomes.A,C,I,MStage/Prognostic FactorsDHAJCC122010
3605Derived SEER Path Stg GrpderivedSeerPathStgGrp5This data item is needed to store the results of the derived algorithmic calculation of Derived SEER Pathologic Stage Group.0, 0A, 0IS, 1,1A, 1A1, 1A2, 1B, 1B1, 1B2, 1C, 1S, 2, 2A, 2A1, 2A2, 2B, 2C, 3, 3A, 3B, 3C, 3C1, 3C2, 4, 4A, 4A1, 4A2, 4B, 4C, OC, 88, 99, Blank..textUpper-case alphanumeric, left justified.TumorThe 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.A,C,I,MStage/Prognostic FactorsDHSEER
3610Derived SEER Clin Stg GrpderivedSeerClinStgGrp5This data item is needed to store the results of the derived algorithmic calculation of Derived SEER Clinical Stage Group.0, 0A, 0IS, 1,1A, 1A1, 1A2, 1B, 1B1, 1B2, 1C, 1S, 2, 2A, 2A1, 2A2, 2B, 2C, 3, 3A, 3B, 3C, 3C1, 3C2, 4, 4A, 4A1, 4A2, 4B, 4C, OC, 88, 99, Blank..textUpper-case alphanumeric, left justified.TumorThe 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.A,C,I,MStage/Prognostic FactorsDHSEER162016
3614Derived SEER Cmb Stg GrpderivedSeerCmbStgGrp5This data item is needed to store the results of the derived algorithmic calculation of SEER Combined Stage Group. 0, 0A, 0IS, 1,1A, 1A1, 1A2, 1B, 1B1, 1B2, 1C, 1S, 2, 2A, 2A1, 2A2, 2B, 2C, 3, 3A, 3B, 3C, 3C1, 3C2, 4, 4A, 4A1, 4A2, 4B, 4C, OC, 88, 99, Blank..textUpper-case alphanumeric, Left justified.TumorRationale 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.A,C,I,MStage/Prognostic FactorsDHSEER162016
3616Derived SEER Combined TderivedSeerCombinedT5This new data item is needed to store the results of the derived algorithmic calculation of Derived SEER Combined T.See AJCC Cancer Staging Manual and FORDS Manual; also 88, blank..textUpper-case alphanumeric, left justified, blank filledSee the most recent versions of the *AJCC Cancer Staging Manual* and *STORE* manual.TumorThe 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.A,C,I,MStage/Prognostic FactorsDHSEER
3618Derived SEER Combined NderivedSeerCombinedN5This item is used to store the results of the source information selected for the derived algorithmic calculation of Combined T, N, and M.See AJCC Cancer Staging Manual and FORDS Manual; also 88, blank..textUpper-case alphanumeric, left justified, blank filledSee the most recent versions of the *AJCC Cancer Staging Manual* and *STORE* manual.TumorThe 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.A,C,I,MStage/Prognostic FactorsDHSEER
3620Derived SEER Combined MderivedSeerCombinedM5This item is used to store the results of the source information selected for the derived algorithmic calculation of Combined T, N, and M.See AJCC Cancer Staging Manual and FORDS Manual; also 88, blank..textUpper-case alphanumeric, left justified, blank filledSee the most recent versions of the *AJCC Cancer Staging Manual* and *STORE* manual.TumorThe 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.A,C,I,MStage/Prognostic FactorsDHSEER162016
3622Derived SEER Cmb T SrcderivedSeerCmbTSrc1This item is needed to store the results of the source information selected for the derived algorithmic calculation of Derived SEER Combined T [3616].1, 2, 3, 9Derived SEER Combined T Source..digits.TumorA,C,I,MStage/Prognostic FactorsDHSEER162016
3624Derived SEER Cmb N SrcderivedSeerCmbNSrc1This item is needed to store the results of the source information selected for the derived algorithmic calculation of Derived SEER Combined N [3618].1, 2, 3, 9Derived SEER Combined N Source..digits.TumorA,C,I,MStage/Prognostic FactorsDHSEER
3626Derived SEER Cmb M SrcderivedSeerCmbMSrc1This item is needed to store the results of the source information selected for the derived algorithmic calculation of Derived SEER Combined M \[3620\].1, 2, 3, 9Derived SEER Combined M Source..digits.TumorA,C,I,MStage/Prognostic FactorsDHSEER162016
3700SEER Site-Specific Fact 1seerSiteSpecificFact12A two character field to be used when information for a particular primary site needs to be collected by SEER.10, 11, 20, 21, 30, 31, 40, 41, 50, 51, 70, 71, 97, 99, Blank..**Note 1:** There is evidence that human papilloma virus (HPV) plays a role in the pathogenesis of some cancers. HPV testing may be performed for prognostic purposes; testing may also be performed on metastatic sites to aid in determination of the primary site. **Note 2:** Record the results of any HPV testing performed on pathological specimens including surgical and cytological (from cell blocks) tissue from the primary tumor or a metastatic site, including lymph nodes. Do not record the results of blood tests or serology. **Note 3:** There are several methods for determination of HPV status. The most frequently used test is IHC for p16 expression which is surrogate marker for HPV infection. The rest of the tests (based on ISH, PCR, RT-PCR technologies) detect the viral DNA or RNA.  **Note 4:** HPV-type 16 refers to virus type and is different from p16 overexpression (p16+). **Note 5:** Codes 10-51 are hierarchical; use the highest code that applies. **Note 6:** For cases in the Oropharynx HPV-Mediated p16+ schema. * If an additional HPV test is done in addition to p16, code those test results in this data item. * If no additional HPV test is done, code 11 in this data item (Schema Discriminator 2 coded to 2). **Note 7:** For cases in the Oropharynx (p16-) schema. * If an additional HPV test is done in addition to p16, code those test results in this data item. * If no additional HPV test is done. * Code 10 in this data item if Shema Discriminator 2 is coded to 1. * Code 99 in this data item if Schema Discriminator 2 is coded to 9.numericTo be determined for each site where needed. Refer to the most current version of the** [**SEER Program Coding and Staging** **Manual](http://seer.cancer.gov/tools/codingmanuals/), for details.\\.TumorThis field is a place holder when site-specific information is needed for SEER.A,C,I,MStage/Prognostic FactorsRSEER122010
3702SEER Site-Specific Fact 2seerSiteSpecificFact21A one character field to be used when information for a particular primary site needs to be collected by SEER.0-9, blank..digitsTo be determined for each site where needed. Refer to the most current version of the[*SEER Program Coding and Staging* ***Manual***](http://seer.cancer.gov/tools/codingmanuals/)***,*^3^**for details..TumorThis field is a place holder when site-specific information is needed for SEER.A,C,I,MStage/Prognostic Factors.SEER122010
3704SEER Site-Specific Fact 3seerSiteSpecificFact31A one character field to be used when information for a particular primary site needs to be collected by SEER.0-9, blank..digitsTo be determined for each site where needed. Refer to the most current version of the[*SEER Program Coding and Staging* ***Manual***](http://seer.cancer.gov/tools/codingmanuals/)***,*^3^**for details..TumorThis field is a place holder when site-specific information is needed for SEER.A,C,I,MStage/Prognostic Factors.SEER122010
3706SEER Site-Specific Fact 4seerSiteSpecificFact41A one character field to be used when information for a particular primary site needs to be collected by SEER.0-9, blank..digitsTo be determined for each site where needed. Refer to the most current version of the[*SEER Program Coding and Staging* ***Manual***](http://seer.cancer.gov/tools/codingmanuals/)***,*^3^**for details..TumorThis field is a place holder when site-specific information is needed for SEER.A,C,I,MStage/Prognostic Factors.SEER122010
3708SEER Site-Specific Fact 5seerSiteSpecificFact51A one character field to be used when information for a particular primary site needs to be collected by SEER.0-9, blank..digitsTo be determined for each site where needed. Refer to the most current version of the[*SEER Program Coding and Staging* ***Manual***](http://seer.cancer.gov/tools/codingmanuals/)***,*^3^**for details..TumorThis field is a place holder when site-specific information is needed for SEER.A,C,I,MStage/Prognostic Factors.SEER122010
3710SEER Site-Specific Fact 6seerSiteSpecificFact61A one character field to be used when information for a particular primary site needs to be collected by SEER.0-9, blank..digitsTo be determined for each site where needed. Refer to the most current version of the [*SEER Program Coding and Staging* ***Manual***](http://seer.cancer.gov/tools/codingmanuals/)***,*^3^**for details..TumorThis field is a place holder when site-specific information is needed for SEER.A,C,I,MStage/Prognostic Factors.SEER122010
3750Over-ride CS 1overRideCs11Some 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.1, blank.RHdigits.TumorSome 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.A,C,I,MEdit Overrides/Conversion History/System Admin.AJCC12.12011
3751Over-ride CS 2overRideCs21Some 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.1, blank.RHdigits.TumorSome 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.A,C,I,MEdit Overrides/Conversion History/System Admin.AJCC12.12011
3752Over-ride CS 3overRideCs31Some 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.1, blank.RHdigits.TumorSome 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.A,C,I,MEdit Overrides/Conversion History/System Admin.AJCC12.12011
3753Over-ride CS 4overRideCs41Some 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.1, blank.RHdigits.TumorSome 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.A,C,I,MEdit Overrides/Conversion History/System Admin.AJCC12.12011
3754Over-ride CS 5overRideCs51Some 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.1, blank.RHdigits.TumorSome 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.A,C,I,MEdit Overrides/Conversion History/System Admin.AJCC12.12011
3755Over-ride CS 6overRideCs61Some 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.1, blank.RHdigits.TumorSome 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.A,C,I,MEdit Overrides/Conversion History/System Admin.AJCC12.12011
3756Over-ride CS 7overRideCs71Some 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.1, blank.RHdigits.TumorSome 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.A,C,I,MEdit Overrides/Conversion History/System Admin.AJCC12.12011
3757Over-ride CS 8overRideCs81Some 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.1, blank.RHdigits.TumorSome 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.A,C,I,MEdit Overrides/Conversion History/System Admin.AJCC12.12011
3758Over-ride CS 9overRideCs91Some 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.1, blank.RHdigits.TumorSome 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.A,C,I,MEdit Overrides/Conversion History/System Admin.AJCC12.12011
3759Over-ride CS 10overRideCs101Some 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.1, blank.RHdigits.TumorSome 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.A,C,I,MEdit Overrides/Conversion History/System Admin.AJCC
3760Over-ride CS 11overRideCs111Some 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.1, blank.RHdigits.TumorSome 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.A,C,I,MEdit Overrides/Conversion History/System Admin.AJCC12.12011
3761Over-ride CS 12overRideCs121Some 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.1, blank.RHdigits.TumorSome 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.A,C,I,MEdit Overrides/Conversion History/System Admin.AJCC
3762Over-ride CS 13overRideCs131Some 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.1, blank.RHdigits.TumorSome 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.A,C,I,MEdit Overrides/Conversion History/System Admin.AJCC12.12011
3763Over-ride CS 14overRideCs141Some 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.1, blank.RHdigits.TumorSome 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.A,C,I,MEdit Overrides/Conversion History/System Admin.AJCC12.12011
3764Over-ride CS 15overRideCs151Some 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.1, blank.RHdigits.TumorSome 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.A,C,I,MEdit Overrides/Conversion History/System Admin.AJCC12.12011
3765Over-ride CS 16overRideCs161Some 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.1, blank.RHdigits.TumorSome 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.A,C,I,MEdit Overrides/Conversion History/System Admin.AJCC12.12011
3766Over-ride CS 17overRideCs171Some 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.1, blank.RHdigits.TumorSome 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.A,C,I,MEdit Overrides/Conversion History/System Admin.AJCC12.12011
3767Over-ride CS 18overRideCs181Some 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.1, blank.RHdigits.TumorSome 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.A,C,I,MEdit Overrides/Conversion History/System Admin.AJCC12.12011
3768Over-ride CS 19overRideCs191Some 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.1, blank.RHdigits.TumorSome 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.A,C,I,MEdit Overrides/Conversion History/System Admin.AJCC12.12011
3769Over-ride CS 20overRideCs201Some 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.1, blankDirect Summary Stage 2000 Flag.RHdigitsRHTumorSome 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.A,C,I,MEdit Overrides/Conversion History/System AdminRHAJCC/NPCR12.12011
3780Secondary Diagnosis 1secondaryDiagnosis17Records the patient’s preexisting medical conditions, factors influencing health status, and/or complications for the treatment of this cancer. Both are considered secondary diagnoses. Preexisting 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. ICD-10-CM codes are 7 characters long, where each character represents an aspect of the condition or procedure: the 7 characters indicate 'section', 'body system', 'root operation', 'body part', 'approach', 'device', and 'qualifier', respectively (see ICD-10-PCS Reference Manual for additional information).A00.0 - B99.9, E00.0 - E89.89, G00.0 - P96.9, R00.0 - S99.929, T36.0 - T50.996, Y62.0 - Y84.9, Z14.0 - Z22.9, Z68.1 - Z68.54, Z80.0 - Z80.9, Z85.0 - Z86.03, Z86.1 - Z99.89 \tSecondary Dx ICD-10 1.RtextLeft justified, starting with a character, there will be a presumed decimal point between the third and fourth characters in the reported value.TumorThe current Comorbidity and complication items are based on ICD-9-CM codes and only allow 5 characters, with the introduction of ICD-10-CM in to common use the NAACCR transmission record needs to be able to carry these new codes (that are longer in length and different in structure).A,C,I,MStage/Prognostic FactorsR*CoC132013
3782Secondary Diagnosis 2secondaryDiagnosis27Records the patient’s preexisting medical conditions, factors influencing health status, and/or complications for the treatment of this cancer. Both are considered secondary diagnoses. Preexisting 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. ICD-10-CM codes are 7 characters long, where each character represents an aspect of the condition or procedure: the 7 characters indicate 'section', 'body system', 'root operation', 'body part', 'approach', 'device', and 'qualifier', respectively (see ICD-10-PCS Reference Manual for additional information).A00.0 - B99.9, E00.0 - E89.89, G00.0 - P96.9, R00.0 - S99.929, T36.0 - T50.996, Y62.0 - Y84.9, Z14.0 - Z22.9, Z68.1 - Z68.54, Z80.0 - Z80.9, Z85.0 - Z86.03, Z86.1 - Z99.89Secondary Dx ICD10 2.RtextLeft justified, starting with a character, there will be a presumed decimal point between the third and fourth characters in the reported value .TumorThe current Comorbidity and complication items are based on ICD-9-CM codes and only allow 5 characters, with the introduction of ICD-10-CM in to common use the NAACCR transmission record needs to be able to carry these new codes (that are longer in length and different in structure).A,C,I,MStage/Prognostic FactorsR*CoC132013
3784Secondary Diagnosis 3secondaryDiagnosis37Records the patient’s preexisting medical conditions, factors influencing health status, and/or complications for the treatment of this cancer. Both are considered secondary diagnoses. Preexisting 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. ICD-10-CM codes are 7 characters long, where each character represents an aspect of the condition or procedure: the 7 characters indicate 'section', 'body system', 'root operation', 'body part', 'approach', 'device', and 'qualifier', respectively (see ICD-10-PCS Reference Manual for additional information). A00.0 - B99.9, E00.0 - E89.89, G00.0 - P96.9, R00.0 - S99.929, T36.0 - T50.996, Y62.0 - Y84.9, Z14.0 - Z22.9, Z68.1 - Z68.54, Z80.0 - Z80.9, Z85.0 - Z86.03, Z86.1 - Z99.89Secondary Dx ICD10 3.RtextLeft justified, starting with a character, there will be a presumed decimal point between the third and fourth characters in the reported value .TumorThe current Comorbidity and complication items are based on ICD-9-CM codes and only allow 5 characters, with the introduction of ICD-10-CM in to common use the NAACCR transmission record needs to be able to carry these new codes (that are longer in length and different in structure).A,C,I,MStage/Prognostic FactorsR*CoC132013
3786Secondary Diagnosis 4secondaryDiagnosis47Records the patient’s preexisting medical conditions, factors influencing health status, and/or complications for the treatment of this cancer. Both are considered secondary diagnoses. Preexisting 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. ICD-10-CM codes are 7 characters long, where each character represents an aspect of the condition or procedure: the 7 characters indicate 'section', 'body system', 'root operation', 'body part', 'approach', 'device', and 'qualifier', respectively (see ICD-10-PCS Reference Manual for additional information).A00.0 - B99.9, E00.0 - E89.89, G00.0 - P96.9, R00.0 - S99.929, T36.0 - T50.996, Y62.0 - Y84.9, Z14.0 - Z22.9, Z68.1 - Z68.54, Z80.0 - Z80.9, Z85.0 - Z86.03, Z86.1 - Z99.89Secondary Dx ICD10 4.RtextLeft justified, starting with a character, there will be a presumed decimal point between the third and fourth characters in the reported value .TumorThe current Comorbidity and complication items are based on ICD-9-CM codes and only allow 5 characters, with the introduction of ICD-10-CM in to common use the NAACCR transmission record needs to be able to carry these new codes (that are longer in length and different in structure).A,C,I,MStage/Prognostic FactorsR*CoC
3788Secondary Diagnosis 5secondaryDiagnosis57Records the patient’s preexisting medical conditions, factors influencing health status, and/or complications for the treatment of this cancer. Both are considered secondary diagnoses. Preexisting 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. ICD-10-CM codes are 7 characters long, where each character represents an aspect of the condition or procedure: the 7 characters indicate 'section', 'body system', 'root operation', 'body part', 'approach', 'device', and 'qualifier', respectively (see ICD-10-PCS Reference Manual for additional information).A00.0 - B99.9, E00.0 - E89.89, G00.0 - P96.9, R00.0 - S99.929, T36.0 - T50.996, Y62.0 - Y84.9, Z14.0 - Z22.9, Z68.1 - Z68.54, Z80.0 - Z80.9, Z85.0 - Z86.03, Z86.1 - Z99.89Secondary Dx ICD10 5.RtextLeft justified, starting with a character, there will be a presumed decimal point between the third and fourth characters in the reported value.TumorThe current Comorbidity and complication items are based on ICD-9-CM codes and only allow 5 characters, with the introduction of ICD-10-CM in to common use the NAACCR transmission record needs to be able to carry these new codes (that are longer in length and different in structure).A,C,I,MStage/Prognostic FactorsR*CoC132013
3790Secondary Diagnosis 6secondaryDiagnosis67Records the patient’s preexisting medical conditions, factors influencing health status, and/or complications for the treatment of this cancer. Both are considered secondary diagnoses. Preexisting 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. ICD-10-CM codes are 7 characters long, where each character represents an aspect of the condition or procedure: the 7 characters indicate 'section', 'body system', 'root operation', 'body part', 'approach', 'device', and 'qualifier', respectively (see ICD-10-PCS Reference Manual for additional information).A00.0 - B99.9, E00.0 - E89.89, G00.0 - P96.9, R00.0 - S99.929, T36.0 - T50.996, Y62.0 - Y84.9, Z14.0 - Z22.9, Z68.1 - Z68.54, Z80.0 - Z80.9, Z85.0 - Z86.03, Z86.1 - Z99.89Secondary Dx ICD10 6.RtextLeft justified, starting with a character, there will be a presumed decimal point between the third and fourth characters in the reported value .TumorThe current Comorbidity and complication items are based on ICD-9-CM codes and only allow 5 characters, with the introduction of ICD-10-CM in to common use the NAACCR transmission record needs to be able to carry these new codes (that are longer in length and different in structure).A,C,I,MStage/Prognostic FactorsR*CoC132013
3792Secondary Diagnosis 7secondaryDiagnosis77Records the patient’s preexisting medical conditions, factors influencing health status, and/or complications for the treatment of this cancer. Both are considered secondary diagnoses. Preexisting 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. ICD-10-CM codes are 7 characters long, where each character represents an aspect of the condition or procedure: the 7 characters indicate 'section', 'body system', 'root operation', 'body part', 'approach', 'device', and 'qualifier', respectively (see ICD-10-PCS Reference Manual for additional information).A00.0 - B99.9, E00.0 - E89.89, G00.0 - P96.9, R00.0 - S99.929, T36.0 - T50.996, Y62.0 - Y84.9, Z14.0 - Z22.9, Z68.1 - Z68.54, Z80.0 - Z80.9, Z85.0 - Z86.03, Z86.1 - Z99.89Secondary Dx ICD10 7.RtextLeft justified, starting with a character, there will be a presumed decimal point between the third and fourth characters in the reported value .TumorThe current Comorbidity and complication items are based on ICD-9-CM codes and only allow 5 characters, with the introduction of ICD-10-CM in to common use the NAACCR transmission record needs to be able to carry these new codes (that are longer in length and different in structure).A,C,I,MStage/Prognostic FactorsR*CoC132013
3794Secondary Diagnosis 8secondaryDiagnosis87Records the patient’s preexisting medical conditions, factors influencing health status, and/or complications for the treatment of this cancer. Both are considered secondary diagnoses. Preexisting 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. ICD-10-CM codes are 7 characters long, where each character represents an aspect of the condition or procedure: the 7 characters indicate 'section', 'body system', 'root operation', 'body part', 'approach', 'device', and 'qualifier', respectively (see ICD-10-PCS Reference Manual for additional information).A00.0 - B99.9, E00.0 - E89.89, G00.0 - P96.9, R00.0 - S99.929, T36.0 - T50.996, Y62.0 - Y84.9, Z14.0 - Z22.9, Z68.1 - Z68.54, Z80.0 - Z80.9, Z85.0 - Z86.03, Z86.1 - Z99.89Secondary Dx ICD10 8.RtextLeft justified, starting with a character, there will be a presumed decimal point between the third and fourth characters in the reported value .TumorThe current Comorbidity and complication items are based on ICD-9-CM codes and only allow 5 characters, with the introduction of ICD-10-CM in to common use the NAACCR transmission record needs to be able to carry these new codes (that are longer in length and different in structure).A,C,I,MStage/Prognostic FactorsR*CoC132013
3796Secondary Diagnosis 9secondaryDiagnosis97Records the patient’s preexisting medical conditions, factors influencing health status, and/or complications for the treatment of this cancer. Both are considered secondary diagnoses. Preexisting 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. ICD-10-CM codes are 7 characters long, where each character represents an aspect of the condition or procedure: the 7 characters indicate 'section', 'body system', 'root operation', 'body part', 'approach', 'device', and 'qualifier', respectively (see ICD-10-PCS Reference Manual for additional information).A00.0 - B99.9, E00.0 - E89.89, G00.0 - P96.9, R00.0 - S99.929, T36.0 - T50.996, Y62.0 - Y84.9, Z14.0 - Z22.9, Z68.1 - Z68.54, Z80.0 - Z80.9, Z85.0 - Z86.03, Z86.1 - Z99.89Secondary Dx ICD10 9.RtextLeft justified, starting with a character, there will be a presumed decimal point between the third and fourth characters in the reported value .TumorThe current Comorbidity and complication items are based on ICD-9-CM codes and only allow 5 characters, with the introduction of ICD-10-CM in to common use the NAACCR transmission record needs to be able to carry these new codes (that are longer in length and different in structure).A,C,I,MStage/Prognostic FactorsR*CoC132013
3798Secondary Diagnosis 10secondaryDiagnosis107Records the patient’s preexisting medical conditions, factors influencing health status, and/or complications for the treatment of this cancer. Both are considered secondary diagnoses. Preexisting 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. ICD-10-CM codes are 7 characters long, where each character represents an aspect of the condition or procedure: the 7 characters indicate 'section', 'body system', 'root operation', 'body part', 'approach', 'device', and 'qualifier', respectively (see ICD-10-PCS Reference Manual for additional information).A00.0 - B99.9, E00.0 - E89.89, G00.0 - P96.9, R00.0 - S99.929, T36.0 - T50.996, Y62.0 - Y84.9, Z14.0 - Z22.9, Z68.1 - Z68.54, Z80.0 - Z80.9, Z85.0 - Z86.03, Z86.1 - Z99.89Secondary Dx ICD10 10.RtextLeft justified, starting with a character, there will be a presumed decimal point between the third and fourth characters in the reported value .TumorThe current Comorbidity and complication items are based on ICD-9-CM codes and only allow 5 characters, with the introduction of ICD-10-CM in to common use the NAACCR transmission record needs to be able to carry these new codes (that are longer in length and different in structure).A,C,I,MStage/Prognostic FactorsR*CoC132013
3800Schema IDschemaId5The derived values in this data item link Site-Specific Data Items (including grade data items) with the appropriate site/histology grouping and accounts for every combination of primary site and histology. The values for this data item are derived based on primary site, histology, and schema discriminator fields (when required). The derived values link Site-Specific Data Items with the appropriate site/histology grouping. For example, the Schema ID for an adenocarcinoma of the lung is 00360. This value links the Site-Specific Data Items associated with adenocarcinoma of the lung: Separate Tumor Nodules [3929], Visceral and Parietal Pleural Invasion [3937], and Pleural Effusion [3913]. The Schema ID would also link to the appropriate grade data items an adenocarcinoma of the lung. The AJCC ID [995] code for Lung is 36. The AJCC ID [995] would link to the AJCC TNM Data items (Clin T, Clin N, Etc.) specific to Lung.   AJCC ID [995] will not be assigned when a site/histology combination is not eligible for TNM staging. See the NAACCR Site-Specific Data Item webpage for codesDDEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.textSee the NAACCR Site-Specific Data Item webpage for codesDTumorThe purpose of the derived Schema ID is to link the appropriate Site-Specific Data Items with the patient’s primary site/histology. This data item is similar to AJCC ID [995], but includes additional site/histologies that may not be eligible for TNM staging using the current AJCC Staging Manual. AJCC ID [995] is left blank if a case is not eligible for TNM Staging using the current AJCC Staging Manual. Separating AJCC ID [995] and the Schema ID allows coding of Site-Specific Data Items for site/histology combinations that are not eligible for an AJCC Stage, but are eligible for Summary Stage. This data item will also be used to develop edits and could potentially be used for analysis.A,C,I,MStage/Prognostic FactorsDNAACCR182018
3801Chromosome 1p: Loss of Heterozygosity (LOH)chromosome1pLossHeterozygosity1Chromosome 1p: Loss of Heterozygosity (LOH) refers to the loss of genetic material normally found on the short arm of one of the patient's two copies of chromosome 1. Codeletion of Chromosome 1p and 19q is a diagnostic, prognostic and predictive marker for gliomas and is strongly associated with the oligodendroglioma phenotype.0, 1, 6-9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorChromosome 1p: Loss of Heterozygosity (LOH) is a Registry Data Collection Variable in AJCC. It was previously collected as Brain, CS SSF #5.A,C,I,MStage/Prognostic FactorsRSNAACCR182018
3802Chromosome 19q: Loss of Heterozygosity (LOH)chromosome19qLossHeterozygosity1Chromosome 19q: Loss of Heterozygosity (LOH) refers to the loss of genetic material normally found on the long arm of one of the patient's two copies of chromosome 19. Codeletion of Chromosome 1p and 19q is a diagnostic, prognostic and predictive marker for gliomas and is strongly associated with the oligodendroglioma phenotype.0, 1, 6-9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorChromosome 19q: Loss of Heterozygosity (LOH) is a Registry Data Collection Variable in AJCC. It was previously collected as Brain, CS SSF #6.A,C,I,MStage/Prognostic FactorsRSNAACCR182018
3803Adenoid Cystic Basaloid PatternadenoidCysticBasaloidPattern5Adenoid Cystic Basaloid Pattern, the presence of a basaloid pattern on pathological examination, is a prognostic factor for adenoid cystic carcinoma of the lacrimal gland.0.0-100.0, XXX.5, XXX.8, XXX.9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.text.TumorAdenoid Cystic Basaloid Pattern is a Registry Data Collection Variable in AJCC 8. This data item was previously collected as Lacrimal Gland, CS SSF# 6.A,C,I,MRevised; 8/29/2025 SEER revised "RS" to "RC"RevisedStage/Prognostic FactorsRCNAACCR
3804Adenopathyadenopathy1Adenopathy is defined as the presence of lymph nodes greater than 1.5 cm on physical examination (PE) and is part of the staging criteria for Chronic Lymphocytic Leukemia/Small Lymphocytic Lymphoma (CLL/SLL).0, 1, 5, 9RAI Classification: AdenopathyRS*RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorAdenopathy is a prognostic factor required for staging of Chronic Lymphocytic Leukemia/Small Lymphocytic Lymphoma (CLL/SLL) in AJCC 8th edition, Chapter 79, *Hodgkin and Non-Hodgkin Lymphomas*.A,C,I,MStage/Prognostic FactorsRSNAACCR182018
3805AFP Post-Orchiectomy Lab ValueafpPostOrchiectomyLabValue7AFP (Alpha Fetoprotein) Post-Orchiectomy Lab Value refers to the lowest AFP value measured post-orchiectomy. AFP is a serum tumor marker that is often elevated in patients with nonseminomatous germ cell tumors of the testis. The Post-Orchiectomy lab value is used to monitor response to therapy.0.0, 0.1-99999.9, XXXXX.1, XXXXX.7, XXXXX.8, XXXXX.9Testis Serum Markers: AFP (Alpha Fetoprotein) Post-Orchiectomy Lab Value.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.text.TumorAFP (Alpha Fetoprotein) Post-Orchiectomy Lab Value is a Registry Data Collection Variable in AJCC. It was previously collected as Testis CS SSF# 12.A,C,I,MStage/Prognostic FactorsRCNAACCR182018
3806AFP Post-Orchiectomy RangeafpPostOrchiectomyRange1AFP (Alpha Fetoprotein) Post-Orchiectomy Range identifies the range category of the lowest AFP value measured post-orchiectomy. AFP is a serum tumor marker that is often elevated in patients with nonseminomatous germ cell tumors of the testis. The Post-Orchiectomy lab value is used to monitor response to therapy.0-5, 7-9Testis Serum Markers: AFP (Alpha Fetoprotein) Post-Orchiectomy Range.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorAFP (Alpha Fetoprotein) Post-Orchiectomy Range is a Registry Data Collection Variable in AJCC. AFP (Alpha Fetoprotein) Post-Orchiectomy Range is used to assign the S Category Pathological and was previously collected as Testis CS SSF# 13.A,C,I,MRevised; 8/29/2025 SEER revised "RS" to "RC"RevisedStage/Prognostic FactorsRCNAACCR182018
3807AFP Pre-Orchiectomy Lab ValueafpPreOrchiectomyLabValue7AFP (Alpha Fetoprotein) Pre-Orchiectomy Lab Value refers to the AFP value measured prior to treatment. AFP is a tumor marker that is often elevated in patients with nonseminomatous germ cell tumors of the testis.0.0, 0.1-99999.9, XXXXX.1, XXXXX.7, XXXXX.8, XXXXX.9Testis Serum Markers: AFP (Alpha Fetoprotein) Pre-Orchiectomy Lab Value.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.text.TumorAFP (Alpha Fetoprotein) Pre-Orchiectomy Lab Value is a Registry Data Collection Variable in AJCC. It was previously collected as Testis CS SSF# 6.A,C,I,MStage/Prognostic FactorsRCNAACCR182018
3808AFP Pre-Orchiectomy RangeafpPreOrchiectomyRange1AFP (Alpha Fetoprotein) Pre-Orchiectomy Range identifies the range category of the highest AFP value measured prior to treatment. AFP is a serum tumor marker that is often elevated in patients with nonseminomatous germ cell tumors of the testis.0-4, 7-9Testis Serum Markers: AFP (Alpha Fetoprotein) Pre-Orchiectomy Range.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorAFP (Alpha Fetoprotein) Pre-Orchiectomy Range is a Registry Data Collection Variable in AJCC. AFP (Alpha Fetoprotein) Pre-Orchiectomy Range is used to assign the S Category Clinical and was previously collected as Testis CS SSF# 7.A,C,I,MRevised; 8/29/2025 SEER revised "RS" to "RC"RevisedStage/Prognostic FactorsRCNAACCR182018
3809AFP Pretreatment InterpretationafpPretreatmentInterpretation1AFP (Alpha Fetoprotein) Pretreatment Interpretation, a nonspecific serum protein that generally is elevated in the setting of hepatocellular carcinoma (HCC), is a prognostic factor for liver cancer.0-2, 7-9AFP (Alpha Fetoprotein) Pretreatment Interpretation RS*RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorAFP (Alpha Fetoprotein) Pretreatment Interpretation is a Registry Data Collection Variable in AJCC. This data item was previously collected for Liver, CS SSF# 1.A,C,I,MStage/Prognostic FactorsRCNAACCR182018
3810AFP Pretreatment Lab ValueafpPretreatmentLabValue6AFP (Alpha Fetoprotein) Pretreatment Lab Value is a nonspecific serum protein that generally is elevated in the setting of hepatocellular carcinoma (HCC). This data item pertains to the pre-treatment lab value.0.0, 0.1-9999.9, XXXX.1, XXXX.2, XXXX.8, XXXX.9AFP (Alpha Fetoprotein) Pretreatment Lab Value.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.text.TumorAFP (Alpha Fetoprotein) Pretreatment Lab Value is a Registry Data Collection Variable in AJCC. This data item was previously collected for Liver, CS SSF# 3.A,C,I,MStage/Prognostic FactorsRCNAACCR182018
3811Anemiaanemia1Anemia is defined by a deficiency of red blood cells or of hemoglobin in the blood. In staging of Chronic Lymphocytic Leukemia/Small Lymphocytic Leukemia (CLL/SLL), anemia is defined as Hgb less than 11.0 g/dL.0, 1, 5, 6, 7, 9RAI Classification: AnemiaRS*RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorAnemia is a prognostic factor required for staging of Chronic Lymphocytic Leukemia/Small Lymphocytic Lymphoma (CLL/SLL) in AJCC 8th edition, Chapter 79, *Hodgkin and Non-Hodgkin Lymphomas*.A,C,I,MStage/Prognostic FactorsRSNAACCR182018
3812B symptomsbSymptoms1B symptoms refer to systemic symptoms of fever, night sweats, and weight loss which can be associated with both Hodgkin lymphoma and some non-Hodgkin lymphomas. The presence of B symptoms is a prognostic factor for some lymphomas.0, 1, 8, 9RS*RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorB symptoms is a Registry Data Collection Variable in AJCC. This data item was previously collected for Lymphomas, SSF# 2.A,C,I,MStage/Prognostic FactorsRSNAACCR182018
3813Bilirubin Pretreatment Total Lab ValuebilirubinPretxTotalLabValue5Bilirubin Pretreatment Total Lab Value records the bilirubin value prior to treatment. Bilirubin level is an indicator of how effectively the liver excretes bile and is required to calculate the Model for End-Stage Liver Disease (MELD) score used to assign priority for liver transplant.0.0, 0.1-999.9, XXX.1, XXX.7, XXX.8, XXX.9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.text.TumorBilirubin Pretreatment Total Lab Value is a Registry Data Collection Variable in AJCC. This data item was previously collected as Liver, CS SSF# 6.A,C,I,MStage/Prognostic FactorsRCNAACCR182018
3814Bilirubin Pretreatment Unit of MeasurebilirubinPretxUnitOfMeasure1Bilirubin Pretreatment Unit of Measure identifies the unit of measure for the bilirubin value measured prior to treatment. Bilirubin is commonly measured in units of Milligrams/deciliter (mg/dL) in the United States and Micromoles/liter (umol/L) in Canada and Europe.1, 2, 7-9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorBilirubin Pretreatment is a Registry Data Collection Variable in AJCC. Bilirubin Pretreatment Unit of Measure is needed to identify the unit in which bilirubin is measured and was previously collected as Liver, CS SSF# 7.A,C,I,MStage/Prognostic FactorsRCNAACCR182018
3815Bone InvasionboneInvasion1Bone invasion, the presence or absence of bone invasion based on imaging, is a prognostic factor for soft tissue sarcomas.0, 1, 8, 9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorBone Invasion is a Registry Data Collection Variable in AJCC. This data item was previously collected for Soft Tissue, SSF# 3.A,C,I,MRevised; 8/29/2025 SEER revised "RS" to "RC"RevisedStage/Prognostic FactorsRCNAACCR182018
3816Brain Molecular MarkersbrainMolecularMarkers2Multiple brain molecular markers have become standard pathology components necessary for diagnosis. This data item captures clinically important brain cancer subtypes identified by molecular markers that are not distinguishable by ICD-O-3 codes.01-23, 85-88, 99..Each Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits**Definition** If a mutation or alteration is in the name of the histopathology, it is required for diagnosis as it helps distinguish among clinically important subtypes within ICD-O-3.  * _IDH mutation status_ distinguishes between clinically important subtypes within ICD-O-3 9400/3, Diffuse astrocytoma and 9401/3, Anaplastic astrocytoma. * _IDH mutant and 1p/19q co-deletion_ distinguishes between clinically important subtypes within ICD-O-3 code 9450/3, Oligodendroglioma and 9451/3, Anaplastic Oligodendroglioma. * _IDH-wildtype_ distinguishes clinically important subtypes within ICD-O-3 9400/3, Diffuse astrocytoma, 9401/3, Anaplastic astrocytoma and 9440/3, Glioblastoma, Epithelioid glioblastoma and Glioblastoma, NOS (note that the new ICD-O-3 code 9445/3 applies to Glioblastoma, IDH-mutant; information regarding this subtype is not collected using this data item). * _SHH-activation and TP53-wildtype_ distinguishes between clinically important subtypes within ICD-O-3 histology code 9471/3, Medulloblastoma. * _C19MC alteration_ status distinguishes a clinically important highly aggressive subtype within ICD-O-3 9478/3, Embryonal tumor with multilayered rosettes. * _Pediatric-type diffuse low-grade gliomas_: 9385/3 Diffuse hemispheric glioma, H3-G34-mutant, Diffuse midline glioma, H3 K27-altered, Diffuse pediatric-type high-grade glioma, H3-wildtype and IDH-wildtype, and Infant-type hemispheric glioma. * _Ependymal tumors_ are distinguished by mutations required for diagnosis among clinically important subtypes: 9396/3 Posterior fossa group A (PFA) ependymoma, Posterior fossa group B (PFB) ependymoma, Spinal ependymoma, \_MYCN\_-amplified, Supratentorial ependymoma, _YAPI_ fusion-positive, and Supratentorial ependymoma, _ZFTA_ fusion-positive. * _Pediatric-type diffuse low-grade gliomas_ are distinguished among subtypes by mutations required for diagnosis: 9421/1 Diffuse astrocytoma, \_MYB\_-or \_MYBL1\_-altered, Diffuse low-grade glioma, MAPK pathway-altered, and Pilocytic astrocytoma. * _Circumscribed astrocytic tumors_ are distinguished among subtypes by mutations required for diagnosis: 9430/3 Astroblastoma, MN1-altered and Astroblastoma. * _Other CNS embryonal tumors_ are distinguished among subtypes by mutations required for diagnosis: 9500/3 CNS neuroblastoma\_, FOXR2\_-activated, CNS tumor with _BCOR_ internal tandem duplication, and Neuroblastoma, NOS.Note 1:** This data item was introduced in 2018 and applied to the following ICD-O-3 histology codes 9400/3, 9401/3, 9440/3, 9450/3, 9451/3, 9471/3, 9478/3. * These are codes 01-09 and are applicable for cases diagnosed 2018+ and are in ICD-O-3 order. **Note 2:** In 2022, the 5th edition of the CNS WHO Blue Book was released and the following histologies were added 9385/3, 9396/3, 9421/1, 9430/3, 9500/3. * These are codes 10-23 and are applicable for cases diagnosed 2024+ and are in ICD-O-3 order. **Note 3:** If a microscopically confirmed histology is not included in this list, assign, code 85.  * If your case is not microscopically confirmed, code 99. **Note 4:** Physician statement of histologic subtype can be used to code this data item.   **Note 5:** See Brain Molecular Markers in the SSDI Manual, in the Definition section for more information on the different histologies. **Examples****:* 1. Biopsy of brain tumor, microscopic confirmation diagnosis: Diffuse Astrocytoma (9400/3). Additional testing done, and IDH-mutant is identified. Code 01.  2. Biopsy of brain tumor, microscopic confirmation diagnosis: Anaplastic astrocytoma (9401/3). No further testing or results unknown. Code 99. 3. MRI of brain tumor, clinical diagnosis: glioblastoma. No further workup. Code 99. 4. Biopsy of brain tumor, microscopic confirmation diagnosis: Mixed glioma (9382/3). Code 85RSTumorCollection of these clinically important brain cancer subtypes has been recommended by CBTRUS.A,C,I,MStage/Prognostic FactorsRSNAACCR182018
3817Breslow Tumor ThicknessbreslowTumorThickness4Breslow Tumor Thickness, the measurement of the thickness of a melanoma as defined by Dr. Alexander Breslow, is a prognostic factor for Melanoma of the Skin.0.0, 0.1-99.9, XX.1, A.01-A9.9, AX.0, XX.8, XX.9RS*RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.textRSTumorBreslow Tumor Thickness is a Registry Data Collection Variable in AJCC. It was previously collected as Melanoma Skin, CS SSF# 1.A,C,I,MStage/Prognostic FactorsRSNAACCR182018
3818CA-125 Pretreatment Interpretationca125PretreatmentInterpretation1Carbohydrate Antigen 125 (CA-125) is a tumor marker that is useful for following the response to therapy in patients with ovarian cancer, who may have elevated levels of this marker.0-2, 7-9: CA-125 (Carbohydrate Antigen 125) Pretreatment InterpretationRS*RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorPreoperative CA-125 is a Registry Data Collection Variable listed in AJCC. It was previously collected as Ovary, CS SSF# 1.A,C,I,MStage/Prognostic FactorsRSNAACCR182018
3819CEA Pretreatment InterpretationceaPretreatmentInterpretation1CEA (Carcinoembryonic Antigen) Pretreatment Interpretation refers to the interpretation of the CEA value prior to treatment. CEA is a glycoprotein that is produced by adenocarcinomas from all sites as well as many squamous cell carcinomas of the lung and other sites. CEA may be measured in blood, plasma or serum. CEA is a prognostic marker for adenocarcinomas of the appendix, colon and rectum and is used to monitor response to treatment0-3, 7-9RS*RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorCEA (Carcinoembryonic Antigen) is a Registry Data Collection Variable for AJCC 8. CEA (Carcinoembryonic Antigen) Pretreatment Interpretation was previously collected as Colon and Rectum, CS SSF #1.A,C,I,MStage/Prognostic FactorsRSNAACCR182018
3820CEA Pretreatment Lab ValueceaPretreatmentLabValue6CEA (Carcinoembryonic Antigen) Pretreatment Lab Value records the CEA value prior to treatment. CEA is a nonspecific tumor marker that has prognostic significance for colon and rectum cancer.0.0, 0.1-9999.9, XXXX.1, XXXX.7, XXXX.8, XXXX.9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.text.TumorCEA (Carcinoembryonic Antigen) Pretreatment Lab Value is a Registry Data Collection Variable in AJCC. It was previously collected as Colon and Rectum, CS SSF# 3.A,C,I,MStage/Prognostic FactorsRSNAACCR182018
3821Chromosome 3 Statuschromosome3Status1Chromosome 3 Status refers to the partial or total loss of Chromosome 3, which is a prognostic factor for uveal melanoma.0-3, 7-9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorChromosome 3 Status is a Registry Data Collection Variable in AJCC. This data item was previously collected as Uveal Melanoma, CS SSF# 5.A,C,I,MRevised; 8/29/2025 SEER revised "RC" to "."RevisedStage/Prognostic Factors.NAACCR182018
3822Chromosome 8q Statuschromosome8qStatus1Chromosome 8q Status refers to gain in Chromosome 8q, which is a prognostic factor for uveal melanoma.0, 1, 7-9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.text.TumorChromosome 8q Status is a Registry Data Collection Variable in AJCC. This data item was previously collected as Uveal Melanoma, CS SSF# 7.A,C,I,MRevised; 8/29/2025 SEER revised "RC" to "."RevisedStage/Prognostic Factors.NAACCR182018
3823Circumferential Resection Margin (CRM)circumferentialResectionMargin4Circumferential or Radial Resection Margin, the distance in millimeters between the leading edge of the tumor and the surgically dissected margin as recorded on the pathology report, is a prognostic indicator for colon and rectal cancer. This may also be referred to as the Radial Resection Margin or surgical clearance.0.0, 0.1-99.9, XX.1, XX.2, XX.3, XX.4, XX.5, XX.6, XX.7, XX.8, XX.9RS*RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.text.TumorCircumferential or Radial Resection Margin is a Registry Data Collection Variable in AJCC. It was previously collected as Colon and Rectum CS SSF# 6.A,C,I,MStage/Prognostic FactorsRSNAACCR182018
3824Creatinine Pretreatment Lab ValuecreatininePretreatmentLabValue4Creatinine Pretreatment Lab Value, an indicator of kidney function is required to calculate the Model for End-Stage Liver Disease (MELD) score, which is used to assign priority for liver transplant.00, 0.1-99.9, XX.1, XX.7, XX.8, XX.9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.text.TumorCreatinine Pretreatment Lab Value is a Registry Data Collection Variable in AJCC. This data item was previously collected for Liver, CS SSF# 4.A,C,I,MStage/Prognostic FactorsRCNAACCR182018
3825Creatinine Pretreatment Unit of MeasurecreatininePretxUnitOfMeasure1Creatinine Pretreatment Unit of Measure identifies the unit of measure for the creatinine value measured in blood or serum prior to treatment. Creatinine is commonly measured in units of Milligrams/deciliter (mg/dL) in the United States and Micromoles/liter (umol/L) in Canada and Europe.1, 2, 7-9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorCreatinine Pretreatment is a Registry Data Collection Variable in AJCC. Creatinine Pretreatment Unit of Measure is needed to identify the unit in which creatinine is measured and was previously collected as Liver, CS SSF# 5.A,C,I,MStage/Prognostic FactorsRCNAACCR182018
3826Estrogen Receptor Percent Positive or Range estrogenReceptorPercntPosOrRange3Estrogen Receptor, Percent Positive Range is the percent of cells staining estrogen receptor positive by IHC.000-100, R10, R20, R30, R40, R50, R60, R70, R80, R90, R99, XX7, XX8, XX9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.text.TumorEstrogen Receptor, Percent Positive Range is a Registry Data Collection Variable in AJCC. It is a new data item for cases diagnosed 1/1/2018+.A,C,I,MStage/Prognostic FactorsRCNAACCR182018
3827Estrogen Receptor SummaryestrogenReceptorSummary1ER (Estrogen Receptor) Summary is a summary of results of the estrogen receptor (ER) assay.0, 1, 7, 9RS*RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digitsRSTumorThis data item is required for prognostic stage grouping in AJCC 8th edition, Chapter 48, *Breast*. It was previously collected as Breast CS SSF # 1.A,C,I,MStage/Prognostic FactorsRSNAACCR182018
3828Estrogen Receptor Total Allred ScoreestrogenReceptorTotalAllredScore2Estrogen Receptor, Total Allred Score is based on the percentage of cells that stain positive by IHC for estrogen receptor (ER) and the intensity of that staining.00-08, X8, X9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.text.TumorEstrogen Receptor, Total Allred Score is a Registry Data Collection Variable in AJCC. It is a new data item for cases diagnosed 1/1/2018+.A,C,I,MSEER revised from * to RHStage/Prognostic FactorsRHNAACCR182018
3829Esophagus and EGJ Tumor EpicenteresophagusAndEgjTumorEpicenter1Esophagus and Esophagogastric Junction (EGJ), Squamous Cell (including adenosquamous), Tumor Location refers to the position of the epicenter of the tumor in the esophagus.0-2, 9RS*RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digitsRSTumorThis data item is required for prognostic stage grouping for squamous and adenosquamous carcinoma in AJCC 8th edition, Chapter 16 *Esophagus and Esophagogastric Junction*. It is a new data item for cases diagnosed 1/1/2018+.A,C,I,MStage/Prognostic FactorsRSNAACCR182018
3830Extranodal Extension Clin (non-Head and Neck)extranodalExtensionClin1Extranodal Extension (ENE) Clinical is defined as "the extension of a nodal metastasis through the lymph node capsule into adjacent tissue" during the diagnostic workup. This data item defines clinical ENE for sites other than Head and Neck.0-2, 4, 7-9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorExtranodal Extension Clinical (non-Head and Neck) is a Registry Data Collection Variable for AJCC. This data item was previously collected for Penis, SSF# 17.A,C,I,MStage/Prognostic FactorsRCNAACCR182018
3831Extranodal Extension Head and Neck ClinicalextranodalExtensionHeadNeckClin1Extranodal extension (ENE) is defined as "the extension of a nodal metastasis through the lymph node capsule into adjacent tissue" and is a prognostic factor for most head and neck tumors. This data item pertains to clinical staging extension.0-2, 4, 7-9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorExtranodal Extension Head and Neck Clinical is a Registry Data Collection Variable in AJCC. It was previously collected as Head and Neck SSF# 8 (Common SSF).A,C,I,MStage/Prognostic FactorsRCNAACCR182018
3832Extranodal Extension Head and Neck PathologicalextranodalExtensionHeadNeckPath3Extranodal extension (ENE) is defined as "the extension of a nodal metastasis through the lymph node capsule into adjacent tissue" and is a prognostic factor for most head and neck tumors. This data item pertains to pathological staging extension.0.0, 0.1-9.9, X.1, X.2, X.3, X.4, X.7, X.8, X.9RS*RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.text.TumorExtranodal Extension Head and Neck Pathological is a Registry Data Collection Variable in AJCC. It was previously collected as Head and Neck SSF# 9 (Common SSF).A,C,I,MRevised; 9/02/2025 SEER revised "RS" to "RC"RevisedStage/Prognostic FactorsRCNAACCR182018
3833Extranodal Extension Path (non-Head and Neck)extranodalExtensionPath1Extranodal Extension Pathological is defined as "the extension of a nodal metastasis through the lymph node capsule into adjacent tissue" identified as part of the surgical resection. This data item defines pathological ENE for sites other than Head and Neck. 0, 1, 7-9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorExtranodal Extension Pathological (non-Head and Neck) is a Registry Data Collection Variable for AJCC. This data item was previously collected for Penis, SSF# 17.A,C,I,MStage/Prognostic FactorsRCNAACCR182018
3834Extravascular Matrix PatternsextravascularMatrixPatterns1Extravascular Matrix Patterns, the presence of loops and networks in extracellular matrix patterns, is a prognostic factor for uveal melanoma.0, 1, 8, 9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.Revised; 8/29/2025 SEER revised "RC" to "."Reviseddigits.TumorExtravascular Matrix Pattern is a Registry Data Collection Variable in AJCC 8. This data item was previously collected as Uveal Melanoma, CS SSF #11 and CS SSF# 12. These two data items were combined and simplified into one data for cases diagnosed 1/1/2018+.RevisedA,C,I,MRevisedRevisedStage/Prognostic Factors.NAACCR182018
3835Fibrosis ScorefibrosisScore1Fibrosis Score, the degree of fibrosis of the liver based on pathological examination, is a prognostic factor for liver cancer.0, 1, 7-9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digitsRSTumorFibrosis Score is a Registry Data Collection Variable in AJCC. This data item was previously collected for Liver, CS SSF# 2.A,C,I,MSEER; RevisedRevisedStage/Prognostic Factors.NAACCR182018
3836FIGO StagefigoStage5Federation Internationale de Gynecologie et d'Obstetrique (FIGO) is a staging system for female reproductive cancers.Valid alphanumeric codes for FIGO stages; 97-99.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.textLeft justified.TumorFIGO stage is a Registry Data Collection Variable in AJCC for the female genital cancers. This data item was previously collected for the female genital cancers as: Vulva SSF #10, Vagina SSF #1, Cervix SSF #1, Corpus Carcinoma SSF #1, Corpus Sarcoma SSF #1, Ovary SSF #2, Fallopian Tube SSF #1, Peritoneum Female Genital SSF #1, and Placenta SSF #2.A,C,I,MRevised; 8/29/2025 SEER revised "RS" to "RC"RevisedStage/Prognostic FactorsRCNAACCR182018
3837Gestational Trophoblastic Prognostic Scoring IndexgestationalTrophoblasticPxIndex2Gestational Trophoblastic Prognostic Scoring Index, a score based on the FIGO-modified World Health Organization (WHO) Prognostic Scoring Index, is used to stratify women with gestational trophoblastic neoplasia in addition to the anatomical stage group. The risk score is appended to the anatomic stage.00-25, X9RS*RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.text.TumorThis data item is required for prognostic stage grouping in AJCC 8th edition, Chapter 56 *Gestational Trophoblastic Neoplasms*. It was previously collected as Placenta, CS SSF # 1.A,C,I,MStage/Prognostic FactorsRSNAACCR182018
3838Gleason Patterns ClinicalgleasonPatternsClinical2Prostate cancers are graded using Gleason score or pattern. This data item represents the Gleason primary and secondary patterns from needle core biopsy or TURP.11-15, 19, 21-25, 29, 31-35, 39, 41-45, 49, 51-55, 59, X6, X7, X8, X9 RS*RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.textRSTumorGleason Patterns Clinical is a Registry Data Collection Variable for Clinical Stage for AJCC. This data item was previously collected as Prostate, CS SSF# 7.A,C,I,MStage/Prognostic FactorsRSNAACCR182018
3839Gleason Patterns PathologicalgleasonPatternsPathological2Prostate cancers are graded using Gleason score or pattern. This data item represents the Gleason primary and secondary patterns from a radical prostatectomy or autopsy.11-15, 19, 21-25, 29, 31-35, 39, 41-45, 49, 51-55, 59, X6, X7, X8, X9RS*RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.textRSTumorGleason Patterns Pathological is a Registry Data Collection Variable for AJCC. This data item was previously collected as Prostate, CS SSF# 9.A,C,I,MStage/Prognostic FactorsRSNAACCR182018
3840Gleason Score ClinicalgleasonScoreClinical2This data item records the Gleason score based on adding the values for primary and secondary patterns in Needle Core Biopsy or TURP.02-10, X7, X8, X9RS*RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.textRSTumorGleason Score Clinical is a Registry Data Collection Variable for AJCC. This data item was previously collected as Prostate, CS SSF# 8.A,C,I,MStage/Prognostic FactorsRSNAACCR182018
3841Gleason Score PathologicalgleasonScorePathological2This data item records the Gleason score based on adding the values for primary and secondary patterns from a radical prostatectomy or autopsy.02-10, X7, X8, X9RS*RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.textRSTumorGleason Score Pathological is a Registry Data Collection Variable for AJCC. This data item was previously collected as Prostate, CS SSF# 10.A,C,I,MStage/Prognostic FactorsRSNAACCR182018
3842Gleason Tertiary PatterngleasonTertiaryPattern2Prostate cancers are graded using Gleason score or pattern. This data item represents the tertiary pattern value from a radical prostatectomy or autopsy.10, 20, 30, 40, 50, X7, X8, X9RS*RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.textRS*TumorTertiary Gleason pattern on prostatectomy is a Registry Data Collection Variable for AJCC. This data item was previously collected as Prostate, CS SSF# 11.A,C,I,MRevised; 8/29/2025 SEER revised "RS" to "RC"RevisedStage/Prognostic FactorsRCNAACCR182018
3843Grade ClinicalgradeClinical1This data item records the grade of a solid primary tumor before any treatment (surgical resection or initiation of any treatment including neoadjuvant). For cases diagnosed January 1, 2018, and later, this data item, along with Grade Pathological and Grade Post-Neoadjuvant, replaces NAACCR Data Item Grade [440] as well as SSF’s for cancer sites with alternative grading systems (e.g., breast [Bloom-Richardson], prostate [Gleason]).1-5, 8, 9, A, B, C, D, E, L, H, M, SRREach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank. Leave blank for cases diagnosed prior to 2018.textRefer to the most recent version of the SSDI Manual for additional site-specific instructionsRTumorGrade is a measure of the aggressiveness of the tumor. Grade and cell type are important prognostic indicators for many cancers. For some sites, grade is required to assign the clinical stage group. For those cases that are eligible AJCC staging, the recommended grading system is specified in the AJCC Chapter. The AJCC Chapter-specific grading systems (codes 1-5) take priority over the generic grade definitions (codes A-E, L, H, 9). For those cases that are not eligible for AJCC staging, if the recommended grading system is not documented, the generic grade definitions would apply.A,C,I,MStage/Prognostic FactorsRNAACCR182018
3844Grade PathologicalgradePathological1This data item records the grade of a solid primary tumor that has been resected and for which no neoadjuvant therapy was administered. If AJCC staging is being assigned, the tumor must have met the surgical resection requirements in the AJCC manual. This may include the grade from the clinical workup. Record the highest grade documented from any microscopic specimen of the primary site whether from the clinical workup or the surgical resection. For cases diagnosed January 1, 2018, and later, this data item, along with Grade Clinical and Grade Post-Neoadjuvant, replaces NAACCR Data Item Grade [440] as well as SSF’s for cancer sites with alternative grading systems (e.g., breast [Bloom-Richardson], prostate [Gleason]).1-5, 8, 9, A, B, C, D, E, L, H, M, SRREach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank. Leave blank for cases diagnosed prior to 2018.textRefer to the most recent version of the SSDI Manual for additional site-specific instructionsRTumorGrade is a measure of the aggressiveness of the tumor. Grade and cell type are important prognostic indicators for many cancers. For some sites, grade is required to assign the pathological stage group. For those cases that are eligible AJCC staging, the recommended grading system is specified in the AJCC Chapter. The AJCC Chapter-specific grading systems (codes 1-5) take priority over the generic grade definitions (codes A-E, L, H, 9). For those cases that are not eligible for AJCC staging, if the recommended grading system is not documented, the generic grade definitions would apply.A,C,I,MStage/Prognostic FactorsRNAACCR182018
3845Grade Post Therapy Path (yp)gradePostTherapy1This data item records the grade of a solid primary tumor that has been resected following neoadjuvant therapy. If AJCC staging is being assigned, the tumor must have met the surgical resection requirements in the AJCC manual. Record the highest grade documented from the surgical treatment resection specimen of the primary site following neoadjuvant therapy. For cases diagnosed January 1, 2018, and later, this data item, along with Grade Clinical and Grade Pathological, replaces NAACCR Data Item Grade [440] as well as SSF’s for cancer sites with alternative grading systems (e.g., breast [Bloom-Richardson], prostate [Gleason]).1-5, 8, 9, A, B, C, D, E, L, H, M, S, BlankRREach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.textRefer to the most recent version of the SSDI Manual for additional site-specific instructionsR*TumorGrade is a measure of the aggressiveness of the tumor. Grade and cell type are important prognostic indicators for many cancers. For some sites, grade is required to assign the post-neoadjuvant stage group. For those cases that are eligible AJCC staging, the recommended grading system is specified in the AJCC Chapter. The AJCC Chapter-specific grading systems (codes 1-5) take priority over the generic grade definitions (codes A-E, L, H, 9). For those cases that are not eligible for AJCC staging, if the recommended grading system is not documented, the generic grade definitions would apply.A,C,I,MStage/Prognostic FactorsRSNAACCR182018
3846hCG Post-Orchiectomy Lab ValuehcgPostOrchiectomyLabValue7hCG (Human Chorionic Gonadotropin) Post-orchiectomy Lab Value refers to the lowest hCG value measured post-orchiectomy. hCG is a serum tumor marker that is often elevated in patients with nonseminomatous germ cell tumors of the testis. The Post-Orchiectomy lab value is used to monitor response to therapy.0.0, 0.1-99999.9, XXXXX.1, XXXXX.7, XXXXX.8, XXXXX.9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.text.TumorhCG (Human Chorionic Gonadotropin) Post-orchiectomy Lab Value is a Registry Data Collection Variable in AJCC. It was previously collected as Testis CS SSF# 14.A,C,I,MStage/Prognostic FactorsRCNAACCR182018
3847hCG Post-Orchiectomy RangehcgPostOrchiectomyRange1Human Chorionic Gonadotropin (hCG) Post-orchiectomy Range identifies the range category of the lowest hCG value measured post-orchiectomy. hCG is a serum tumor marker that is often elevated in patients with nonseminomatous germ cell tumors of the testis. The Post-Orchiectomy lab value is used to monitor response to therapy.0-5, 7-9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorhCG (Human Chorionic Gonadotropin) is a Registry Data Collection Variable in AJCC. hCG (Human Chorionic Gonadotropin) Post-orchiectomy Range is used to assign the S Category Pathological and was previously collected as Testis CS SSF# 15.A,C,I,MRevised; 8/29/2025 SEER revised "RS" to "RC"RevisedStage/Prognostic FactorsRCNAACCR182018
3848hCG Pre-Orchiectomy Lab ValuehcgPreOrchiectomyLabValue7hCG (Human Chorionic Gonadotropin) Pre-orchiectomy Lab Value refers to the hCG value measured prior to treatment. hCG is a serum tumor marker that is often elevated in patients with nonseminomatous germ cell tumors of the testis.0.0, 0.1-99999.9, XXXXX.1, XXXXX.8, XXXXX.9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.text.TumorhCG (Human Chorionic Gonadotropin) Pre-orchiectomy Lab Value is a Registry Data Collection Variable in AJCC. It was previously collected as Testis CS SSF# 8.A,C,I,MStage/Prognostic FactorsRCNAACCR182018
3849hCG Pre-Orchiectomy RangehcgPreOrchiectomyRange1Human Chorionic Gonadotropin (hCG) Pre-orchiectomy Range identifies the range category of the highest hCG value measured prior to treatment. hCG is a serum tumor marker that is often elevated in patients with nonseminomatous germ cell tumors of the testis.0-4, 7-9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorhCG (Human Chorionic Gonadotropin) is a Registry Data Collection Variable in AJCC. hCG (Human Chorionic Gonadotropin) Pre-orchiectomy Range is used to assign the S Category Clinical and was previously collected as Testis CS SSF# 9.A,C,I,MRevised; 8/29/2025 SEER revised "RS" to "RC"RevisedStage/Prognostic FactorsRCNAACCR182018
3850HER2 IHC Summary her2IhcSummary1HER2 IHC Summary is the summary score for HER2 testing by IHC.0-4, 7-9RH*.Each Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorHER2 IHC Summary is a Registry Data Collection Variable in AJCC. It is a new data item for cases diagnosed 1/1/2018+.A,C,I,MStage/Prognostic Factors.NAACCR182018
3851HER2 ISH Dual Probe Copy Numberher2IshDualProbeCopyNumber4HER2 in situ hybridization (ISH) Dual Probe Copy Number is the HER2 copy number based on a dual probe test.0.0-99.9, XX.1, XX.7, XX.8, XX.9..This data item may be left blank.   Each Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.text.TumorHER2 ISH Dual Probe Copy Number is a Registry Data Collection Variable in AJCC. It is a new data item for cases diagnosed 1/1/2018+.A,C,I,MStage/Prognostic Factors.NAACCR182018
3852HER2 ISH Dual Probe Ratioher2IshDualProbeRatio4HER2 in situ hybridization (ISH) Dual Probe Ratio is the summary score for HER2 testing using a dual probe. The test will report results for both HER2 and CEP17, the latter used as a control. The HER2/CEP17 ratio is reported.0.0-99.9, XX.2, XX.3, XX.7, XX.8, XX.9..Each Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.text.TumorHER2 ISH Dual Probe Ratio is a Registry Data Collection Variable in AJCC. It is a new data item for cases diagnosed 1/1/2018+.A,C,I,MStage/Prognostic Factors.NAACCR182018
3853HER2 ISH Single Probe Copy Numberher2IshSingleProbeCopyNumber4HER2 in situ hybridization (ISH) Single Probe Copy Number is the HER2 copy number based on a single probe test.0.0-99.9, XX.1, XX.7, XX.8, XX.9..Each Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.text.TumorHER2 ISH Single Probe Copy Number is a Registry Data Collection Variable in AJCC. It is a new data item for cases diagnosed 1/1/2018+.A,C,I,MStage/Prognostic Factors.NAACCR182018
3854HER2 ISH Summaryher2IshSummary1HER2 in situ hybridization (ISH) Summary is the summary score for results of testing for ERBB2 gene copy number by any ISH method. An immunohistochemistry (IHC) test identifies the protein expressed by the gene (ERBB2), and an ISH test identifies the number of copies of the gene (ERBB2) itself.0, 2, 3, 7-9RH*.Each Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorHER2 ISH Summary is a Registry Data Collection Variable in AJCC. It is a new data item for cases diagnosed 1/1/2018+.A,C,I,MStage/Prognostic Factors.NAACCR182018
3855HER2 Overall Summary her2OverallSummary1HER2 Overall Summary is a summary of results from HER2 testing.0, 1, 7, 8, 9RS*RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digitsRSTumorThis data item is required for prognostic stage grouping in AJCC 8th edition, Chapter 48, *Breast*. It was previously collected as Breast, CS SSF # 15.Experts recommend that every invasive breast cancer be tested for the presence of HER2 because anti-HER2 treatments are highly effective for these tumors.   HER2 overall summary will be collected for Esophagus and Esophagogastric Junction and Stomach for cases diagnosed 1/1/21+ because NCCN guidelines recommend HER2 testing at time of diagnosis if patients are documented or suspected of having metastatic disease. HER2 monoclonal antibodies may be added to chemotherapy for patients with HER2 positive disease.A,C,I,MStage/Prognostic FactorsRSNAACCR182018
3856Heritable TraitheritableTrait1Heritable trait pertains to evidence that a tumor is associated with a heritable mutation. In retinoblastoma, the heritable trait is a germline mutation in the RB1 gene, which is associated with bilateral disease, family history of retinoblastoma, presence of concomitant CNS midline embryonic tumor (commonly in pineal region), or retinoblastoma with an intracranial primitive neuroectodermal tumor (i.e., trilateral retinoblastoma). Children with any of these features may be assigned the H1 status without molecular testing. High quality molecular testing for RB1 mutation is required to determine the presence or absence of RB1 mutation for children without clinical features of a heritable mutation.0, 1, 7, 9RS*Heritable trait is required for prognostic stage grouping in AJCC 8th edition, Chapter 68 *Retinoblastoma*. It is a new data item for cases diagnosed 1/1/2018+.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorA,C,I,MStage/Prognostic FactorsRSNAACCR182018
3857High Risk CytogeneticshighRiskCytogenetics1High Risk Cytogenetics is defined as one or more of t(4;14), t(14;16), or del 17p identified from FISH test results and is part of the staging criteria for plasma cell myeloma.0, 1, 5, 7, 9RS*RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.text.TumorHigh Risk Cytogenetics is a prognostic factor required in AJCC 8th edition, Chapter 82 *Plasma Cell Myeloma and Plasma Cell Disorders*, for staging of plasma cell myeloma.A,C,I,MStage/Prognostic FactorsRSNAACCR182018
3858High Risk Histologic FeatureshighRiskHistologicFeatures1High Risk Histologic Features are defined in AJCC 8 Chapter 15 to include the terms "poor differentiation, desmoplasia, sarcomatoid differentiation, undifferentiated." High risk histologic features are a prognostic factor for cutaneous cell carcinomas of the head and neck.0-6, 8, 9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorHigh Risk Histologic Features is a Registry Data Collection Variable in AJCC. It was previously collected as Skin, CS SSF # 12.A,C,I,MRevised; 8/29/2025 SEER revised "RS" to "."RevisedStage/Prognostic Factors.NAACCR
3859HIV StatushivStatus1HIV status refers to infection with the Human Immunodeficiency Virus which causes Acquired Immune Deficiency Syndrome (AIDS). AIDS is associated with increased risk of developing some lymphomas.0, 1, 7-9..Each Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorHIV status may be collected by the surveillance community for neoplasms (e.g., Kaposi Sarcoma, Lymphomas) that are closely related to HIV/AIDS. Prior to 2018, Lymphoma SSF#1 and Kaposi Sarcoma SSF# 1, were used for HIV Status.A,C,I,MStage/Prognostic FactorsRSNAACCR182018
3860International Normalized Ratio Prothrombin TimeiNRProthrombinTime3International Normalized Ratio for Prothrombin Time (INR), an indicator of the liver’s ability to make clotting factors, is required to calculate the Model for End-Stage Liver Disease (MELD) score, which is used to assign priority for liver transplant.0.0-9.9, X.1, X.7, X.8, X.9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.text.TumorInternational Normalized Ratio for Prothrombin Time (INR) is a Registry Data Collection Variable in AJCC. This data item was previously collected for Liver, CS SSF# 8.A,C,I,MStage/Prognostic FactorsRCNAACCR182018
3861Ipsilateral Adrenal Gland InvolvementipsilateralAdrenalGlandInvolve1Ipsilateral adrenal gland involvement pertains to direct extension of the tumor into the ipsilateral adrenal gland (continuous) or ipsilateral adrenal gland involvement by a separate nodule (noncontiguous).0-4, 8, 9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorIpsilateral adrenal gland involvement for Kidney is a Registry Data Collection Variable in AJCC. It was previously collected as Kidney, CS SSF #3.A,C,I,MRevised; 9/02/2025 SEER revised "RS" to "RC"RevisedStage/Prognostic FactorsRCNAACCR182018
3862JAK2jak21Janus Kinase 2 (JAK2, JAK 2) is a gene mutation that increases susceptibility to several myeloproliferative neoplasms (MPNs). Testing for the JAK2 mutation is done on whole blood. Nearly all people with polycythemia vera, and about half of those with primary myelofibrosis and essential thrombocythemia, have the mutation. JAK2 analysis continues to increase in use for hematopoietic neoplasms.0-5, 7-9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorJAK2 can be collected by the surveillance community for myeloproliferative neoplasms. Prior to 2018, HemeRetic SSF#1 was used for JAK2.A,C,I,MStage/Prognostic FactorsRSNAACCR
3863Ki-67ki675Ki-67 (MIB-1) (Proliferative Index) is a marker of cell proliferation. A high value indicates a tumor that is proliferating more rapidly. Codes and coding instructions for this data item are site-specific.0.0-100.0, XXX.4, XXX.5, XXX.6, XXX.7, XXX.8, XXX.9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.text.TumorKi-67 (MIB-1) (Proliferative Index) is a Registry Data Collection Variable in AJCC. It was a new data item for breast cases diagnosed 1/1/2018+. It will apply to neuroendocrine tumors (NET) of the gastrointestinal tract (AJCC Chapters 29 – 34) for cases diagnosed 1/1/2021+. High Ki-67 is an adverse prognostic factor and Ki-67 is a component of grade for these tumors. NCCN guidelines recommend that tumor differentiation, mitotic rate and Ki-67 should be recorded in the pathology report for these tumors.A,C,I,MStage/Prognostic FactorsRCNAACCR182018
3864Invasion Beyond CapsuleinvasionBeyondCapsule1Invasion beyond capsule pertains to the pathologically confirmed invasion of the tumor beyond the fibrous capsule in which the kidney is enclosed.0-5, 8, 9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorInvasion beyond capsule into specific tissues for Kidney is a Registry Data Collection Variable in AJCC. It was previously collected as Kidney, CS SSF #1.A,C,I,MRevised; 9/02/2025 SEER revised "RS" to "RC"RevisedStage/Prognostic FactorsRCNAACCR182018
3865KIT Gene Immunohistochemistry kitGeneImmunohistochemistry1KIT Gene Immunohistochemistry (IHC) is the expression of the KIT gene in tumor tissue specimens based on immunohistochemical (IHC) stains. A positive test is a diagnostic and predictive marker for GIST tumors.0, 1, 7-9RS*RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorKIT Gene Immunohistochemistry (IHC) is a Registry Data Collection Variable in AJCC. This data item was previously collected for GIST schemas in CS (different SSF’s).A,C,I,MStage/Prognostic FactorsRCNAACCR182018
3866KRASkras1KRAS is an important signaling intermediate in the growth receptor pathway which controls cell proliferation and survival. KRAS is a protein with production controlled by the K-ras gene. When the K-ras gene is activated through mutation during colorectal carcinogenesis, production of KRAS continuously stimulates cell proliferation and prevents cell deaths. Activating mutations in KRAS are an adverse prognostic factor for colorectal carcinoma and predict a poor response to monoclonal anti-EGFR antibody therapy in advanced colorectal carcinoma.0-4, 7-9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorKRAS is a Registry Data Collection Variable in AJCC. It was previously collected as Colon and Rectum CS SSF# 9.A,C,I,MStage/Prognostic FactorsRSNAACCR182018
3867LDH Post-Orchiectomy RangeldhPostOrchiectomyRange1LDH (Lactate Dehydrogenase) Post-Orchiectomy Range identifies the range category of the lowest LDH value measured post-orchiectomy. LDH is a nonspecific marker for testicular cancer that is elevated in some germ cell tumors. The Post-Orchiectomy lab value is used to monitor response to therapy.0-5, 7-9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorLDH (Lactate Dehydrogenase) is a Registry Data Collection Variable in AJCC. LDH (Lactate Dehydrogenase) Post-Orchiectomy Range is used to assign the S Category Pathological and was previously collected as Testis CS SSF# 16.A,C,I,MRevised; 8/29/2025 SEER revised "RS" to "RC"RevisedStage/Prognostic FactorsRCNAACCR182018
3868LDH Pre-Orchiectomy RangeldhPreOrchiectomyRange1Lactate Dehydrogenase (LDH) Range identifies the range category of the highest LDH value measured prior to treatment. LDH is a nonspecific marker for testicular cancer that is elevated in some germ cell tumors. This data item refers to the Pre-Orchiectomy range.0-4, 7-9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorLDH (Lactate Dehydrogenase) is a Registry Data Collection Variable in AJCC. LDH (Lactate Dehydrogenase) Pre-Orchiectomy Range is used to assign the S Category Clinical and was previously collected as Testis CS SSF# 10.A,C,I,MRevised; 8/29/2025 SEER revised "RS" to "RC"RevisedStage/Prognostic FactorsRCNAACCR182018
3869LDH LevelldhPretreatmentLevel1LDH (Lactate Dehydrogenase) is an enzyme involved in conversion of sugars to energy and present in most cells in the body. Elevated pretreatment LDH is an adverse prognostic factor for plasma cell myeloma and melanoma of the skin.0, 1, 5, 7, 9RS*RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorLDH (Lactate Dehydrogenase) Level is a prognostic factor required in AJCC 8^th^ edition for Chapter 83 *Plasma Cell Myeloma and Plasma Cell Disorders* and Chapter 47 *Melanoma Skin*. For Plasma Cell Myeloma, LDH is part of the RISS Stage and is new for cases diagnosed 1/1/2018+. For Melanoma Skin, LDH is used to define the M subcategories and was previously collected as LDH Pretreatment Level and Melanoma Skin, SSF #4.A,C,I,MStage/Prognostic FactorsRSNAACCR
3870LDH Upper Limits of NormalldhUpperLimitsOfNormal3LDH (Lactate Dehydrogenase), an enzyme involved in converting sugars to energy in the body, is elevated in some malignancies. LDH level is a prognostic factor for patients with Stage IV melanoma. This data Item refers to the Upper Limit of Normal in the laboratory test used to interpret the Serum LDH result.001-999, XX8, XX9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.text.TumorLDH (Lactate Dehydrogenase) Upper Limits of Normal is a Registry Data Collection Variable in AJCC. It was previously collected as Melanoma Skin, CS SSF# 6.A,C,I,MStage/Prognostic FactorsRCNAACCR182018
3871LN Assessment Method Femoral-InguinallnAssessMethodFemoralInguinal1This data item describes the method used to assess involvement of femoral-inguinal lymph nodes associated with certain female genital cancers.0-2, 7-9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorMethod of assessment of regional nodal status is listed as a Registry Data Collection Variable in the AJCC GYN chapters. This data item was previously collected as Vulva, SSF# 15.A,C,I,MStage/Prognostic FactorsRCNAACCR182018
3872LN Assessment Method Para-AorticlnAssessMethodParaaortic1This data item describes the method used to assess involvement of para-aortic lymph nodes associated with certain female genital cancers.0-2, 7-9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorMethod of assessment of regional nodal status is listed as a Registry Data Collection Variable in the AJCC GYN chapters. This data item was previously collected as Vagina, CS SSF# 5.A,C,I,MStage/Prognostic FactorsRCNAACCR182018
3873LN Assessment Method PelviclnAssessMethodPelvic1This data item describes the method used to assess involvement of pelvic lymph nodes associated with certain female genital cancers.0-2, 7-9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorMethod of assessment of regional nodal status is listed as a Registry Data Collection Variable in the AJCC GYN chapters. This data item was previously collected as Vagina, CS SSF# 3.A,C,I,MStage/Prognostic FactorsRCNAACCR182018
3874LN Distant Assessment MethodlnDistantAssessMethod1This data item describes the method used to assess involvement of Distant (mediastinal, scalene) nodes associated with certain female genital cancers.0-2, 7-9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorMethod of assessment of distant nodal status is listed as a Registry Data Collection Variable in the AJCC GYN chapters. This data item was previously collected as Vagina, CS SSF# 7.A,C,I,MStage/Prognostic FactorsRCNAACCR182018
3875LN Distant: Mediastinal, ScalenelnDistantMediastinalScalene1This data item describes the status of Distant (mediastinal, scalene) nodes associated with certain female genital cancers.0-3, 8, 9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorSpecific distant lymph node involvement is listed as a Registry Data Collection Variable in the AJCC. This data was previously collected as Vagina, CS SSF# 6.A,C,I,MStage/Prognostic FactorsRCNAACCR182018
3876LN Head and Neck Levels I-IIIlnHeadAndNeckLevels1To31Lymph Nodes for Head and Neck, Levels I-III records the involvement of Levels I-III lymph nodes.0-9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorLevel of nodal involvement is a Registry Data Collection Variable in AJCC for several head and neck chapters. This data item was previously collected as Head and Neck SSF# 3 (common SSF).A,C,I,MRevised; 9/02/2025 SEER revised "RS" to "RC"RevisedStage/Prognostic FactorsRCNAACCR
3877LN Head and Neck Levels IV-VlnHeadAndNeckLevels4To51Lymph Nodes for Head and Neck, Levels IV-V records the involvement of Levels IV-V lymph nodes.0-3, 8, 9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorLevel of nodal involvement is a Registry Data Collection Variable in AJCC. This data item was previously collected as Head and Neck SSF# 4 (common SSF).A,C,I,MRevised; 9/02/2025 SEER revised "RS" to "RC"RevisedStage/Prognostic FactorsRCNAACCR182018
3878LN Head and Neck Levels VI-VIIlnHeadAndNeckLevels6To71Lymph Nodes for Head and Neck, Levels VI-VII records the involvement of Levels VI-VII lymph nodes.0-3, 8, 9.Level of nodal involvement is a Registry Data Collection Variable in AJCC. This data item was previously collected as Head and Neck SSF# 5 (common SSF).RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorLevel of nodal involvement is a Registry Data Collection Variable in AJCC. This data item was previously collected as Head and Neck SSF# 5 (common SSF).A,C,I,MRevised; 9/02/2025 SEER revised "RS" to "RC"RevisedStage/Prognostic FactorsRCNAACCR182018
3879LN Head and Neck OtherlnHeadAndNeckOther1Lymph Nodes for Head and Neck, Other records the involvement of lymph nodes other than Levels I-III, IV-V, and VI-VII.0-9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorLevel of nodal involvement is a Registry Data Collection Variable in AJCC. This data item was previously collected as Head and Neck SSF# 6 (common SSF).A,C,I,MRevised; 9/02/2025 SEER revised "RS" to "RC"RevisedStage/Prognostic FactorsRCNAACCR182018
3880LN Isolated Tumor Cells (ITC)lnIsolatedTumorCells1Lymph Nodes Isolated Tumor Cells (ITC), the presence of isolated tumor cells in regional lymph node(s) that may be detected by hematoxylin and eosin or by immunohistochemical staining, is a potential prognostic factor for Merkel Cell Carcinoma.0, 1, 8, 9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorRegional lymph nodes positive for ITCs (Tumor cell clusters not greater than 0.2 millimeter (mm))A,C,I,MRevised; 9/02/2025 SEER revised "RS" to "RC"RevisedStage/Prognostic FactorsRCNAACCR182018
3881LN LateralitylnLaterality1This data item describes whether positive regional lymph nodes are unilateral or bilateral.0-3, 8, 9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorLaterality of regional node metastasis is a Registry Data Collection Variable in AJCC. This data item was previously collected as Vulva, CS SSF# 11.A,C,I,MRevised; Revised; 8/29/2025 SEER revised "RS" to "."RevisedStage/Prognostic Factors.NAACCR182018
3882LN Positive Axillary Level I-IIlnPositiveAxillaryLevel1To22This data item pertains to the number of positive ipsilateral level I and II axillary lymph nodes and intramammary lymph nodes based on pathological information.00-99, X1, X5, X6, X8, X9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.text.TumorLymph Nodes Positive Axillary Level I-II can be collected by the surveillance community for breast cancers. Prior to 2018, Breast SSF#3 was used for Lymph Nodes Positive Axillary Level I-II.A,C,I,MStage/Prognostic FactorsRSNAACCR182018
3883LN SizelnSize4Lymph Nodes Size records diameter of the involved regional lymph node(s) with the largest diameter of any involved regional lymph node(s). Pathological measurement takes precedence over a clinical measurement for the same node.0.0, 0.1-99.9, XX.1, XX.2, XX.3, XX.4, XX.5, XX.6, XX.7, XX.8, XX.9RS*Lymph Nodes Size is a Registry Data Collection Variable in AJCC for several chapters. It was previously collected in the Head and Neck chapters as Size of Lymph Nodes, SSF# 1RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.text.TumorA,C,I,MRevised; 9/02/2025 SEER revised "RS" to "RC"RevisedStage/Prognostic FactorsRCNAACCR182018
3885Lymphocytosislymphocytosis1Lymphocytosis is defined by an excess of lymphocytes in the blood. In staging of Chronic Lymphocytic Leukemia/Small Lymphocytic Lymphoma (CLL/SLL), lymphocytosis is defined as an absolute lymphocyte count (ALC) greater than 5,000 cells/µL.0, 1, 5, 6, 7, 9RS*RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorLymphocytosis is a prognostic factor required for staging of Chronic Lymphocytic Leukemia/Small Lymphocytic Leukemia (CLL/SLL) in AJCC 8th edition, Chapter 79, *Hodgkin and Non-Hodgkin Lymphomas*.A,C,I,MStage/Prognostic FactorsRSNAACCR182018
3886Major Vein InvolvementmajorVeinInvolvement1Major vein involvement pertains to the invasion of the kidney tumor into major veins.0-4, 8, 9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorInvolvement of major veins for Kidney is a Registry Data Collection Variable in AJCC. It was previously collected as Kidney, CS SSF #2.A,C,I,MRevised; 9/02/2025 SEER revised "RS" to "RC"RevisedStage/Prognostic FactorsRCNAACCR182018
3887Measured Basal DiametermeasuredBasalDiameter4Measured Basal Diameter, the largest basal diameter of a uveal melanoma, is a prognostic indicator for this tumor.0.0-99.9, XX.0, XX.1, XX.2, XX.3, XX.4, XX.5, XX.6, XX.8, XX.9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.text.TumorMeasured Basal Diameter is listed as a Registry Data Collection Variable in AJCC. It was previously collected as Uveal Melanoma, CS SSF# 2.A,C,I,MStage/Prognostic FactorsRSNAACCR182018
3888Measured ThicknessmeasuredThickness4Measured Thickness, or height, of a uveal melanoma, is a prognostic indicator for this tumor.0.0-99.9, XX.0, XX.1, XX.2, XX.3, XX.4, XX.5, XX.6, XX.8, XX.9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.text.TumorMeasured Thickness is listed as a Registry Data Collection Variable in AJCC. It was previously collected as Uveal Melanoma, CS SSF# 3.A,C,I,MStage/Prognostic FactorsRSNAACCR182018
3889Methylation of O6-Methylguanine-MethyltransferasemethylationOfO6MGMT1O6-Methylguanine-Methyltransferase (MGMT) is an enzyme in cells that repairs DNA. Methylation of the MGMT gene reduces production of MGMT enzyme and the ability of tumor cells to repair damage caused by chemotherapy. Methylation of MGMT is a prognostic and predictive factor for high grade gliomas.0-3, 6-9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorMethylation of O6-Methylguanine-Methyltransferase (MGMT) is a Registry Data Collection Variable in AJCC. It was previously collected as Brain, CS SSF #4.A,C,I,MStage/Prognostic FactorsRSNAACCR
3890Microsatellite Instability (MSI)microsatelliteInstability1The microsatellite instability (MSI) test is a genetic test performed on tumor tissue to look for differences in length of certain non-functioning sections of DNA. The differences are caused by problems with the genes that encode proteins that normally repair certain types of DNA damage. Knowing whether cancer is microsatellite instability high may help plan the best treatment. Microsatellites are short, repeated, sequences of DNA. Cancer cells that have large numbers of microsatellites that may have defects in the ability to correct mistakes that occur when DNA is copied in the cell. Microsatellite instability is found most often in colorectal cancer, other types of gastrointestinal cancer, and endometrial cancer. It may also be found in cancers of the breast, prostate, bladder, and thyroid.0-2, 8, 9RS*RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.Revised Codes 0, 1, 2digitsRS*TumorMicrosatellite Instability (MSI) is a Registry Data Collection Variable in AJCC. It was previously collected as Colon and Rectum, CS SSF# 7.A,C,I,MStage/Prognostic FactorsRSNAACCR182018
3891Microvascular DensitymicrovascularDensity2Microvascular Density (MVD), a quantitative measure of tumor vascularity, is a prognostic factor for uveal melanoma.00-99, X1, X2, X3, X4, X5, X7, X8, X9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.RevisedRevisedtext.TumorMicrovascular Density (MVD), is a Registry Data Collection Variable in AJCC. This data item was previously collected as Uveal Melanoma, CS SSF# 13.RevisedA,C,I,MRevised; 8/29/2025 SEER revised "RC" to "."RevisedStage/Prognostic Factors.NAACCR182018
3892Mitotic Count Uveal MelanomamitoticCountUvealMelanoma4Mitotic Count Uveal Melanoma, the number of mitoses per 40 high-power fields (HPF) based on pathological evaluation, is a prognostic factor for uveal melanoma.0.0, 0.1-99.9, XX.1, XX.2, XX.3, XX.4, XX.7, XX.8, XX.9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.text.TumorMitotic Count Uveal Melanoma is listed as a Registry Data Collection Variable in AJCC. It was previously collected as Uveal Melanoma, CS SSF# 9.A,C,I,MStage/Prognostic FactorsRCNAACCR182018
3893Mitotic Rate MelanomamitoticRateMelanoma2Mitotic Rate Melanoma, the number of mitoses per square millimeter based on pathological evaluation, is a prognostic factor for melanoma of the skin.00-99, X1, X2, X3, X4, X7, X8, X9RS*RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.text.TumorMitotic Rate Melanoma is a Registry Data Collection Variable in AJCC. It was previously collected as Melanoma Skin, CS SSF# 7.A,C,I,MStage/Prognostic FactorsRSNAACCR182018
3894Multigene Signature MethodmultigeneSignatureMethod1Multigene signatures or classifiers are assays of a panel of genes from a tumor specimen, intended to provide a quantitative assessment of the likelihood of response to chemotherapy and to evaluate prognosis or the likelihood of future metastasis. This data item identifies the multigene signature method used. Oncotype Dx is coded elsewhere.1-9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorMultigene Signature Method is a Registry Data Collection Variable in AJCC. It was previously collected as Breast, CS SSF #22. See also Multigene Signature Results.A,C,I,MSEER; RevisedRevisedStage/Prognostic Factors.NAACCR
3895Multigene Signature ResultsmultigeneSignatureResults2Multigene signatures or classifiers are assays of a panel of genes from a tumor specimen, intended to provide a quantitative assessment of the likelihood of response to chemotherapy and to evaluate prognosis or the likelihood of future metastasis. This data item identified the multigene signature result. Oncotype Dx is coded elsewhere.00-99, X1, X2, X3, X4, X7, X8, X9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.text.TumorMultigene Signature Results is a Registry Data Collection Variable in AJCC. It was previously collected as Breast, CS SSF #23. See also Multigene Signature Method.A,C,I,MSEER; RevisedRevisedStage/Prognostic Factors.NAACCR182018
3896NCCN International Prognostic Index (IPI)nccnInternationalPrognosticIndex2The NCCN International Prognostic Index (IPI) (previously only "IPI") is used to define risk groups for specific lymphomas using a 0-8 score range, based on age, stage, number of extranodal sites of involvement, patient's performance status and pretreatment LDH level.00-08, X1, X2, X3, X4, X8, X9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.text.TumorNCCN International Prognostic Index (IPI) is a Registry Data Collection Variable in AJCC. It was previously collected for Lymphomas, SSF# 3.A,C,I,MRevised; 9/02/2025 SEER revised "RS" to "RC"RevisedStage/Prognostic FactorsRCNAACCR182018
3897Number of Cores ExaminednumberOfCoresExamined2This data item represents the number of cores examined as documented in the pathology report from needle biopsy of the prostate gland.01-99, X1, X6, X7, X8, X9RS*RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.text.TumorNumber of Cores Examined is a Registry Data Collection Variable for AJCC. This data item was previously collected as Prostate, CS SSF# 13.A,C,I,MRevised; 9/02/2025 SEER revised "RS" to "RC"RevisedStage/Prognostic FactorsRCNAACCR182018
3898Number of Cores PositivenumberOfCoresPositive2This data item represents the number of positive cores documented in the pathology report from needle biopsy of the prostate gland.00, 01-99, X1, X6, X7, X8, X9RS*RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.text.TumorNumber of Cores Positive is a Registry Data Collection Variable for AJCC. This data item was previously collected as Prostate, CS SSF# 12.A,C,I,MRevised; 9/02/2025 SEER revised "RS" to "RC"RevisedStage/Prognostic FactorsRCNAACCR182018
3899Number of Examined Para-Aortic NodesnumberOfExaminedParaAorticNodes2Number of examined para-aortic nodes is the number of nodes examined based on para-aortic nodal dissection.00, 01-99, X1, X2, X6, X8, X9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.text.TumorNumber of Examined Para-aortic Nodes is listed as a Registry Data Collection Variable in AJCC. This data item was previously collected as Corpus, CS SSF# 6.A,C,I,MStage/Prognostic FactorsRCNAACCR182018
3900Number of Examined Pelvic NodesnumberOfExaminedPelvicNodes2Number of examined pelvic nodes is the number of nodes examined based on pelvic nodal dissection.00, 01-99, X1, X2, X6, X8, X9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.text.TumorNumber of Examined Pelvic Nodes is listed as a Registry Data Collection Variable in AJCC. This data item was previously collected as Corpus, CS SSF# 4.A,C,I,MStage/Prognostic FactorsRCNAACCR182018
3901Number of Positive Para-Aortic NodesnumberOfPositiveParaAorticNodes2Number of Positive Para-Aortic Nodes is the number of positive nodes based on para-aortic nodal dissection00, 01-99, X1, X2, X6, X8, X9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.text.TumorNumber of Positive Para-aortic Nodes is listed as a Registry Data Collection Variable in AJCC. This data item was previously collected as Corpus, CS SSF# 5.A,C,I,MStage/Prognostic FactorsRCNAACCR182018
3902Number of Positive Pelvic NodesnumberOfPositivePelvicNodes2Number of Positive Pelvic Nodes is the number of positive nodes based on pelvic nodal dissection.00, 01-99, X1, X2, X6, X8, X9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.text.TumorNumber of Positive Pelvic Nodes is listed as a Registry Data Collection Variable in AJCC. This data item was previously collected as Corpus, CS SSF# 3.A,C,I,MStage/Prognostic FactorsRCNAACCR182018
3903Oncotype Dx Recurrence Score-DCISoncotypeDxRecurrenceScoreDcis3Oncotype Dx Recurrence Score-DCIS is a numeric score of a genomic test to predict the risk of local recurrence of breast cancer based on the assessment of 21 genes.0-100, XX6, XX7, XX8, XX9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.textRight justified, zero-filled.TumorOncotype Dx Recurrence Score-DCIS is a Registry Data Collection Variable in AJCC. It is a new data item for cases diagnosed 1/1/2018+.A,C,I,MRevised; 8/29/2025 SEER revised "RC" to "."RevisedStage/Prognostic Factors.NAACCR182018
3904Oncotype Dx Recurrence Score-InvasiveoncotypeDxRecurrenceScoreInvasiv3Oncotype Dx Recurrence Score-Invasive is a numeric score of a genomic test to predict the likelihood of distant recurrence of invasive breast cancer based on the assessment of 21 genes.0-100, XX4, XX5, XX6, XX7, XX9RS*RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.textRight justified, zero-filled.TumorOncotype Dx Recurrence Score-Invasive is a Registry Data Collection Variable in AJCC. It is a new data item for cases diagnosed 1/1/2018+.A,C,I,MStage/Prognostic FactorsRSNAACCR182018
3905Oncotype Dx Risk Level-DCISoncotypeDxRiskLevelDcis1Oncotype Dx Risk Level-DCIS stratifies Oncotype Dx recurrence scores into low, intermediate, and high risk of local recurrence.0-2, 6-9..Each Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorOncotype Dx Risk Level-DCIS is a Registry Data Collection Variable in AJCC. It is a new data item for cases diagnosed 1/1/2018+.A,C,I,MSEER: Revised; CoC Revised 7 Aug 2025;RevisedStage/Prognostic Factors.NAACCR182018
3906Oncotype Dx Risk Level-InvasiveoncotypeDxRiskLevelInvasive1Oncotype Dx Risk Level-Invasive stratifies Oncotype Dx recurrence scores into low, intermediate, and high risk of distant recurrence.0-2, 6-9..Each Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorOncotype Dx Risk Level-Invasive is a Registry Data Collection Variable in AJCC. It is a new data item for cases diagnosed 1/1/2018+.A,C,I,MSEER: Revised; CoC Revised 7 Aug 2025;RevisedStage/Prognostic Factors.NAACCR182018
3907Organomegalyorganomegaly1Organomegaly is defined as presence of enlarged liver and/or spleen on physical examination and is part of the staging criteria for Chronic Lymphocytic Leukemia/Small Lymphocytic Lymphoma (CLL/SLL).0, 1, 5, 9RS*RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorOrganomegaly is a prognostic factor required for staging of CLL/SLL in AJCC 8th edition, Chapter 79 *Hodgkin and Non-Hodgkin Lymphomas*.A,C,I,MStage/Prognostic FactorsRSNAACCR182018
3908Percent Necrosis Post NeoadjuvantpercentNecrosisPostNeoadjuvant5Percent Necrosis Post Neoadjuvant is a prognostic factor for bone sarcomas.0.0, 0.1-100.0, XXX.2, XXX.8, XXX.9RH*.Each Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.text.TumorPercent Necrosis Post Neoadjuvant is a Registry Data Collection Variable for AJCC. It was previously collected as Bone, CS SSF# 3.A,C,I,MSEER Revised; CCCR Revised; CoC Revised 7 Aug 2025;RevisedStage/Prognostic Factors.NAACCR182018
3909Perineural InvasionperineuralInvasion1Perineural Invasion, within or adjacent to the primary tumor, is a negative prognostic factor for cutaneous squamous cell carcinomas of the head and neck and carcinomas of the colon and rectum, eyelid and lacrimal gland.0, 1, 8, 9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorPerineural Invasion is a Registry Data Collection Variable in AJCC. It was previously collected as Colon and Rectum CS SSF# 8 and Lacrimal Gland CS SSF# 4.A,C,I,MStage/Prognostic FactorsRSNAACCR182018
3910Peripheral Blood InvolvementperipheralBloodInvolvement1Peripheral blood involvement, summarized in "B category", refers to the percentage of peripheral blood lymphocytes that are atypical (Sezary) cells and whether they are "Clone negative" or "Clone positive".0-7, 9RS*RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorPeripheral blood involvement is a prognostic factor required in AJCC 8th edition, Chapter 81 *Primary Cutaneous Lymphomas*, for staging of Mycosis Fungoides and Sezary Syndrome. It was previously collected as Mycosis Fungoides, CS SSF #1.A,C,I,MStage/Prognostic FactorsRSNAACCR182018
3911Peritoneal CytologyperitonealCytology1Peritoneal cytology pertains to the results of cytologic examination for malignant cells performed on fluid that is obtained from the peritoneal cavity.0-3, 7-9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorPeritoneal Cytology is listed as a Registry Data Collection Variable in AJCC. This data item was previously collected as Corpus, CS SSF# 2.A,C,I,MStage/Prognostic FactorsRSNAACCR182018
3913Pleural EffusionpleuralEffusion1Pleural effusion is the accumulation of fluid between the parietal pleura (the pleura covering the chest wall and diaphragm) and the visceral pleura (the pleura covering the lungs).0-4, 8, 9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorPleural Effusion is collected by the surveillance community for pleura cancers. Prior to 2018, Pleura SSF #1 was used for Pleural Effusion.A,C,I,MRevised; 9/02/2025 SEER revised "RS" to "RC"RevisedStage/Prognostic FactorsRCNAACCR
3914Progesterone Receptor Percent Positive or RangeprogesteroneRecepPrcntPosOrRange3Progesterone Receptor, Percent Positive or Range is the percent of cells staining progesterone receptor positive measured by IHC.000, 001-100, R10, R20, R30, R40, R50, R60, R70, R80, R90, R99, XX7, XX8, XX9.RS*Note*: * Physician statement of PR (Progesterone Receptor) Percent Positive or Range can be used to code this data item. * Code this data item using the same report used to record PR Summary. * If PR negative, or percentage less than 1%, code 000. * The actual PR (1-100%) percent takes priority over the range codes. * If PR positive but percentage unknown, code XX9. Each Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank. text.TumorProgesterone Receptor, Percent Positive or Range is a Registry Data Collection Variable in AJCC. It is a new data item for cases diagnosed 1/1/2018+.A,C,I,MStage/Prognostic FactorsRCNAACCR182018
3915Progesterone Receptor SummaryprogesteroneRecepSummary1PR (Progesterone Receptor) Summary is a summary of results from the progesterone receptor (PR) assay.0, 1, 7, 9RS*RSNote 1: Physician statement of PR (Progesterone Receptor) Summary status can be used to code this data item when no other information is available. Note 2: The result of the PR test performed on the primary breast tissue is to be recorded in this data item. Note 3: Results from nodal or metastatic tissue may be used ONLY when there is no evidence of primary tumor. Note 4: In cases where PR is reported on more than one breast tumor specimen, record the highest value. If any sample is positive, record as positive. •    Exception: If PR is positive on an in situ specimen and PR is negative on all tested invasive specimens, code PR as negative (code 0). Note 5: If neoadjuvant therapy is given, record the assay from tumor specimens prior to neoadjuvant therapy.   • If neoadjuvant therapy is given and there are no PR results from pre-treatment specimens, report the findings from post-treatment specimens. Note 6: If the patient is PR positive and node negative, a multigene test such as Oncotype Dx may be performed, in which case another PR test will be performed. Do not record the results of that test in this field.   • Record only the results of the test which made the patient eligible to be given the multigene test.   Each Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digitsRSTumorThis data item is required for prognostic stage grouping in AJCC 8th edition, Chapter 48, _Breast_. It was previously collected as Breast CS SSF # 2.A,C,I,MStage/Prognostic FactorsRSNAACCR182018
3916Progesterone Receptor Total Allred ScoreprogesteroneRecepTotalAllredScor2Progesterone Receptor, Total Allred Score is based on the percentage of cells that stain by IHC for progesterone receptor (PR) and the intensity of that staining.00-08, X8, X9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.text.TumorProgesterone Receptor, Total Allred Score is a Registry Data Collection Variable in AJCC. It is a new data item for cases diagnosed 1/1/2018+.A,C,I,MRevised; SEER revised from * to RH on 8/7/2023,Stage/Prognostic FactorsRHNAACCR182018
3917Primary Sclerosing Cholangitis primarySclerosingCholangitis1Primary sclerosing cholangitis denotes a chronic autoimmune inflammation of the bile ducts that leads to scar formation and narrowing of the ducts over time. It is a prognostic factor for intrahepatic bile duct cancer.0, 1, 8, 9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorPrimary Sclerosing Cholangitis is a Registry Data Collection Variable in AJCC. This data item was previously collected for Intrahepatic Bile Duct, SSF# 11.A,C,I,MStage/Prognostic Factors.NAACCR182018
3918Profound Immune SuppressionprofoundImmuneSuppression1Profound Immune Suppression, suppressed immune status that may be associated with HIV/AIDs, solid organ transplant, chronic lymphocytic leukemia, non-Hodgkin lymphoma, multiple conditions or other conditions, increases the risk of developing Merkel Cell Carcinoma and is an adverse prognostic factor.0-6, 8, 9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorProfound Immune Suppression is a Registry Data Collection Variable in AJCC. It was previously collected as Merkel Cell Penis, SSF #22, Merkel Cell Scrotum SSF #22, Merkel Cell Skin, SSF# 22, and Merkel Cell Vulva, SSF# 22.A,C,I,MRevised; 9/02/2025 SEER revised "RS" to "RC"RevisedStage/Prognostic FactorsRCNAACCR182018
3919EOD Prostate Pathologic ExtensionprostatePathologicalExtension3 EOD Prostate Pathologic Extension is used to assign pT category for prostate cancer based on radical prostatectomy specimens.000-999Prostate Pathological Extension, Prostate, CS SSF# 3..textSee the most current version of EOD (Prostate) (<https://staging.seer.cancer.gov/>) for rules and site-specific codes and coding structures..Tumor EOD Prostate Pathologic Extension is used in EOD. It was previously collected as Prostate Pathological Extension, and Prostate, CS SSF# 3.A,C,I,MStage/Prognostic FactorsRSSEER182018
3920PSA (Prostatic Specific Antigen) Lab ValuepsaLabValue5PSA (Prostatic Specific Antigen) is a protein produced by cells of the prostate gland and is elevated in patients with prostate cancer. This data item pertains to PSA lab value.0.1, 0.2-999.9, XXX.1, XXX.2, XXX.3, XXX.7, XXX.9RS*RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.textRSTumorThis data item is required for prognostic stage grouping in AJCC 8th edition, Chapter 58, _Prostate_. It was previously collected as Prostate, CS SSF# 1.A,C,I,MStage/Prognostic FactorsRSNAACCR182018
3921Residual Tumor Volume Post CytoreductionresidualTumVolPostCytoreduction2Gross residual tumor after primary cytoreductive surgery is a prognostic factor for ovarian cancer and residual tumor volume after cytoreductive surgery is a prognostic factor for late stage ovarian cancers.00, 50, 60, 70, 80, 97-99.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.Revised; 9/02/2025 SEER revised "RS" to "RC"Reviseddigits.TumorResidual Tumor Volume Post Cytoreduction is a Registry Data Collection Variable listed in AJCC. It was previously collected as Ovary, CS SSF # 3.RevisedA,C,I,MRevisedRevisedStage/Prognostic FactorsRCNAACCR182018
3922Response to Neoadjuvant TherapyresponseToNeoadjuvantTherapy1This data item records the physician's statement of response to neoadjuvant chemotherapy.0-4, 8, 9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorResponse to Neoadjuvant Therapy is a Registry Data Collection Variable in AJCC. It was previously collected as Breast, CS SSF #21.A,C,I,MStage/Prognostic FactorsRCNAACCR182018
3923S Category ClinicalsCategoryClinical1S Category Clinical combines the results of pre-orchiectomy Alpha Fetoprotein (AFP), Human Chorionic Gonadotropin (hCG) and Lactate Dehydrogenase (LDH) into a summary S value.0-3, 9RS*RS\*N indicates the upper limit of normal for the LDH assay.   Each Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank. digits.TumorS Category Clinical is required for prognostic stage grouping in AJCC 8th edition, Chapter 59 *Testis*. It is a new data item for cases diagnosed 1/1/2018+.A,C,I,MStage/Prognostic FactorsRSNAACCR182018
3924S Category PathologicalsCategoryPathological1S Category Pathological combines the results of post-orchiectomy Alpha Fetoprotein (AFP), Human Chorionic Gonadotropin (hCG) and Lactate Dehydrogenase (LDH) into a summary S value.0-3, 5, 9RS*RS\*N indicates the upper limit of normal for the LDH assay.   Each Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank. digits.TumorS Category Pathological is required for prognostic stage grouping in AJCC 8th edition, Chapter 59, *Testis*. It is a new data item for cases diagnosed 1/1/2018+.A,C,I,MStage/Prognostic FactorsRSNAACCR182018
3925Sarcomatoid FeaturessarcomatoidFeatures3Sarcomatoid features: present or absent and percentage refers to the observation of sheets and fascicles of malignant spindle cells in a kidney tumor which can occur across all histologic subtypes. The percentage of sarcomatoid component has been shown to correlate with cancer-specific mortality.000, 001-100, R01, R02, R03, R04, R05, XX5, XX6, XX7, XX8, XX9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.text.TumorSarcomatoid features for Kidney is a Registry Data Collection Variable in AJCC. It was previously collected as Kidney, CS SSF #4.A,C,I,MStage/Prognostic FactorsRSNAACCR182018
3926Schema Discriminator 1schemaDiscriminator11Captures additional information needed to generate AJCC ID [995] and Schema ID [3800] for some anatomic sites. Discriminators can be based on sub site, histology or other features which affect prognosis.RS*RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.textThe information recorded in Schema Discriminator differs for each anatomic site. See the SSDI manual for most current version of the site-specific codes and coding structures.RSTumorA schema discriminator is used to assign AJCC ID [995] when site and histology alone are insufficient to identify the applicable AJCC staging method and to assign Schema ID [3800], which links each case to the appropriate SSDIs, Summary Stage and EOD data collection system.A,C,I,MStage/Prognostic FactorsRSNAACCR182018
3927Schema Discriminator 2schemaDiscriminator21Captures additional information needed to generate AJCC ID [995] and Schema ID [3800] for some anatomic sites. Discriminators can be based on sub site, histology or other features which affect prognosis.RS*RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.textThe information recorded in Schema Discriminator differs for each anatomic site. See the SSDI manual for most current version of the site-specific codes and coding structures.RSTumorA schema discriminator is used to assign AJCC ID [995] when site and histology alone are insufficient to identify the applicable AJCC staging method and to assign Schema ID [3800], which links each case to the appropriate SSDIs, Summary Stage and EOD data collection system.A,C,I,MStage/Prognostic FactorsRSNAACCR182018
3928Schema Discriminator 3schemaDiscriminator31Captures additional information needed to generate AJCC ID [95] and Schema ID [3800] for some anatomic sites. Discriminators can be based on sub site, histology or other features which affect prognosis.RS*RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.textThe information recorded in Schema Discriminator differs for each anatomic site. See the SSDI manual for most current version of the site-specific codes and coding structures..TumorA schema discriminator is used to assign AJCC ID [995] when site and histology alone are insufficient to identify the applicable AJCC staging method and to assign Schema ID [3800], which links each case to the appropriate SSDIs, Summary Stage and EOD data collection system.A,C,I,MStage/Prognostic FactorsRSNAACCR182018
3929Separate Tumor NodulesseparateTumorNodules1"Separate tumor nodules" refers to what is conceptually a single tumor with intrapulmonary metastasis in the ipsilateral (same) lung. Their presence in the same or different lobes of lung from the primary tumor affects the T and M categories.0-4, 7-9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorThis data item was previously collected for Lung, SSF# 1 and at least one standard setter is continuing to collect it.A,C,I,MRevised; 9/02/2025 SEER revised "RS" to "RC"RevisedStage/Prognostic FactorsRCNAACCR182018
3930Serum Albumin Pretreatment LevelserumAlbuminPretreatmentLevel1Albumin is the most abundant protein in human blood plasma. Serum albumin pretreatment level is a prognostic factor for plasma cell myeloma.0, 1, 5, 7, 9RS*RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorSerum albumin pretreatment level is a prognostic factor required in AJCC 8th edition, Chapter 82 *Plasma Cell Myeloma and Plasma Cell Disorders*, for the Revised International Staging System (RISS).A,C,I,MStage/Prognostic FactorsRSNAACCR182018
3931Serum Beta-2 Microglobulin Pretreatment LevelserumBeta2MicroglobulinPretxLvl1Serum Beta-2 Microglobulin is a protein that is found on the surface of many cells and plentiful on the surface of white blood cells. Increased production or destruction of these cells causes Serum β2 (beta-2) Microglobulin level to increase. Elevated Serum β2 (beta-2) Microglobulin level is a prognostic factor for plasma cell myeloma.0-2, 5, 7, 9RS*RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorSerum Beta-2 Microglobulin Pretreatment Level is a prognostic factor required in AJCC 8th edition, Chapter 82 _Plasma Cell Myeloma and Plasma Cell Disorders_, for staging of plasma cell myeloma.A,C,I,MStage/Prognostic FactorsRSNAACCR182018
3932LDH Lab ValueldhPretreatmentLabValue7LDH (Lactate Dehydrogenase) Lab Value, measured in serum, is a predictor of treatment response, progression-free survival and overall survival for patients with Stage IV melanoma of the skin.0.0, 0.1-99999.9, XXXXX.1, XXXXX.7, XXXXX.8, XXXXX.9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.textRSTumorLDH (Lactate Dehydrogenase) Lab Value is a Registry Data Collection Variable in AJCC. It was previously collected as LDH Pretreatment Lab Value and Melanoma Skin, CS SSF# 5.A,C,I,MRevised; 9/02/2025 SEER revised "RS" to "RC"RevisedStage/Prognostic FactorsRCNAACCR182018
3933Thrombocytopeniathrombocytopenia1Thrombocytopenia is defined by a deficiency of platelets in the blood. In staging of Chronic Lymphocytic Leukemia/Small Lymphocytic Lymphoma (CLL/SLL), thrombocytopenia is defined as Platelets (Plt) less than 100,000/μL.0, 1, 5, 6, 7, 9RS*RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorThrombocytopenia is a prognostic factor required for staging of Chronic Lymphocytic Leukemia/Small Lymphocytic Lymphoma (CLL/SLL) in AJCC 8th edition, Chapter 79 _Hodgkin and Non-Hodgkin Lymphomas_.A,C,I,MStage/Prognostic FactorsRSNAACCR182018
3934Tumor DepositstumorDeposits2A tumor deposit is defined as a discrete nodule of cancer in pericolic/perirectal fat or in adjacent mesentery (mesocolic or rectal fat) within the lymph drainage area of the primary carcinoma, without identifiable lymph node tissue or identifiable vascular structure.00, 01-99, X1, X2, X8, X9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.text.TumorThe presence of tumor deposits is a Registry Data Collection Variable in AJCC. It was previously collected as Colon and Rectum CS SSF# 4.A,C,I,MRevised; 9/02/2025 SEER revised "RS" to "RC"RevisedStage/Prognostic FactorsRCNAACCR182018
3935Tumor Growth PatterntumorGrowthPattern1Tumor Growth Pattern refers to the growth pattern of intrahepatic cholangiocarcinoma.1-3, 8, 9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorTumor Growth Pattern is a Registry Data Collection Variable in AJCC. This data item was previously collected for Intrahepatic Bile Duct, SSF# 10.A,C,I,MStage/Prognostic Factors.NAACCR182018
3936Ulcerationulceration1Ulceration, the absence of an intact epidermis overlying the primary melanoma based upon histopathological examination, is a prognostic factor for melanoma of the skin.0, 1, 8, 9RS*RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorUlceration is a Registry Data Collection Variable in AJCC. It was previously collected as Melanoma Skin, CS SSF# 2.A,C,I,MStage/Prognostic FactorsRSNAACCR182018
3937Visceral and Parietal Pleural InvasionvisceralParietalPleuralInvasion1Visceral and Parietal Pleural Invasion is defined as invasion beyond the elastic layer or to the surface of the visceral pleura.0, 4-6, 8, 9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.digits.TumorVisceral and Parietal Pleural Invasion (previously called "pleural/elastic layer invasion (PL)") is a Registry Data Collection Variable for AJCC. This data item was previously collected for Lung, SSF# 2.A,C,I,MRevised; 9/02/2025 SEER revised "RS" to "RC"RevisedStage/Prognostic FactorsRCNAACCR182018
3938ALK RearrangementalkRearrangement1Testing for ALK rearrangement is performed for patients with advanced non-small cell lung cancer (NSCLC) to identify tumors which are sensitive to small-molecule ALK kinase inhibitors.0-2, 4, 7-9, Blank.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.text.TumorALK rearrangement is recommended by treatment guidelines for patients with advanced lung cancer as a prognostic marker and factor in determining appropriate therapy. It is a new data item for cases diagnosed 01/01/2021+.A,C,I,MStage/Prognostic FactorsRNAACCR212021
3939EGFR Mutational AnalysisegfrMutationalAnalysis1Epidermal growth factor receptor (EGFR) mutational analysis is performed for patients with advanced non-small cell lung cancer (NSCLC) to identify patients with certain activating mutations in the EGFR gene which are sensitive to tyrosine kinase inhibitors.0-2, 4, 7-9, Blank.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.text.TumorEGFR mutational analysis is recommended by treatment guidelines for patients with advanced lung cancer as a prognostic marker and factor in determining appropriate therapy. It is a new data item for cases diagnosed 01/01/2021+.A,C,I,MStage/Prognostic FactorsRNAACCR212021
3940BRAF Mutational AnalysisbrafMutationalAnalysis1The BRAF oncoprotein is involved in transmitting cell growth and proliferation signals from KRAS and NRAS. The BRAF V600E mutation is associated with poorer prognosis and predicts lack of response to anti-EGFR therapies.0-4, 7-9, Blank.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.text.TumorBRAF mutational analysis is recommended in clinical guidelines for patients with advanced colorectal cancer as a prognostic marker and factor in determining appropriate therapy.  It is a new data item for cases diagnosed 1/1/2021+.A,C,I,MStage/Prognostic FactorsRNAACCR212021
3941NRAS Mutational AnalysisnrasMutationalAnalysis1NRAS is a signaling intermediate in the growth receptor pathway. Certain NRAS mutations predict poor response to anti-EGFR therapy in patients with metastatic colorectal cancer.0-2, 4, 7-9.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.text.TumorNRAS mutational analysis is recommended in clinical guidelines for patients with metastatic colon cancer who are being considered for anti-EGFR therapy. It is a new data item for cases diagnosed 01/01/2021+.A,C,I,MStage/Prognostic FactorsRNAACCR212021
3942CA 19-9 PreTX Lab Valueca199PretxLabValue6Carbohydrate Antigen (CA) 19-9 Pretreatment Lab Value records the CA 19-9 value prior to treatment. CA 19-9 is a tumor marker that has prognostic significance for pancreatic cancer.0.0, 0.1-999.9, XXXX.1, XXXX.2, XXXX.3, XXXX.7, XXXX.8, XXXX.9, BlankCarbohydrate Antigen 19-9 Pretreatment Lab Value.RSEach Site-Specific Data Item (SSDI) applies only to selected primary sites, histologies, and years of diagnosis. Depending on applicability and standard-setter requirements, SSDIs may be left blank.text.TumorCA 19-9 Pretreatment Lab Value is a strong predictor of resectability in the absence of metastatic disease. It is a new data item for cases diagnosed 01/01/2021+.A,C,I,MStage/Prognostic FactorsRNAACCR212021
3943NCDB--SARSCoV2--TestncdbSarsCov2Test1Data item is designed to track whether patient received a SARS-CoV-2 test or not. Collection based on diagnosis years 2020 and 2021.0, 1, 9.RH*Note*: This item may be left blank.digitsnumeric.PatientTo evaluate the impact of COVID-19 diagnosis on cancer patients.A,C,I,MSpecial UseRH*CoC212021
3944NCDB--SARSCoV2--PosncdbSarsCov2Pos1 Data item is designed to track whether patient received a POSITIVE SARS-CoV-2 test or not. Collection based on diagnosis years 2020 and 2021.0, 1, 9.RH*Note*: This item may be left blank.digitsnumeric.PatientTo evaluate the impact of COVID-19 diagnosis on cancer patients.A,C,I,MSpecial UseRH*CoC212021
3945NCDB--SARSCoV2--Pos DatencdbSarsCov2PosDate8What was the date of the first positive test? Collection based on diagnosis years 2020 and 2021.Valid dates, Blank.RHdateYYYYMMDD.PatientTo evaluate the impact of COVID-19 diagnosis on cancer patients.A,C,I,MSpecial UseRH*CoC212021
3946NCDB--COVID19--Tx ImpactncdbCovid19TxImpact1Was the first course of treatment (diagnosis, staging, treatment or other cancer management events) impacted by hospital availability (limited access to facilities or postponement of non-essential procedures) due to COVID-19 pandemic? (No; First Course Delayed; First Course Altered; First Course Cancelled). Collection based on diagnosis years 2020 and 2021.1-5, 9.RH*Note*: This item may be left blank.digitsnumeric.TumorTo evaluate the impact of COVID-19 pandemic on cancer patients.A,C,I,MSpecial UseRH*CoC212021
3950Macroscopic Evaluation of MesorectummacroscopicEvalOfTheMesorectum2This data item records the results of a macroscopic evaluation of the mesorectum from a total mesorectal excision (TME)00, 10, 20, 30, 40, 99, Blank .Rtext.TumorNumerous studies have demonstrated the total mesorectal excision (TME) improves local recurrence rates and the corresponding survival by as much as 20%. Macroscopic pathologic assessment of the completeness of the mesorectum, scored as complete, partially complete, or incomplete, accurately predicts both local recurrence and distant metastasis.A,C,I,MStage/Prognostic FactorsRCCoC222022
3955Derived Rai StagederivedRaiStage1This data item stores the Derived Rai stage value derived from the values coded in the following SSDIs for the Lymphoma-CLL/SLL schema (9823/3). * Lymphocytosis [3885] * Adenopathy [3804] * Organomegaly [3907] * Anemia [3811] * Thrombocytopenia [3933] The Rai stage is only applicable for Chronic Lymphocytic Leukemia/Small Lymphocytic Lymphoma (CLL/SLL) (9823/3) cases where the primary site is bone marrow (C421). For cases with a primary site other than bone marrow (C421), the derived Rai stage will be 8 and all the SSDIs will be coded to 5. Derivation will be run on all cases diagnosed 1/1/2018 and forward.0-4, 8, 9..This field should be left blank for all cases diagnosed prior to 2018, for schemas other than 00795, and when not required by standard setter.text .TumorThe Derived Rai stage can be used to evaluate disease spread at diagnosis, treatment patterns and outcomes over time.A,C,I,MStage/Prognostic FactorsDNAACCR222022
3956p16p161The p16 biomarker is over-expressed (produced) in response to HPV. It is therefore a surrogate marker for HPV disease.0, 1, 8, 9, blankRS*RSNote: See the [SSDI Manual](https://apps.naaccr.org/ssdi/list/?_gl=1*111s1ff*_ga*NTAyNDk1MDUwLjE1OTI5Mzk3MDY.*_ga_ZGX07SVHJF*MTY1NDU0NDUzMy40LjEuMTY1NDU0NDcwNi4w&_ga=2.89925727.598791132.1654524231-502495050.1592939706) for coding instructions. Anus schema added/ Please note for CCCR p16 for Cervix changed from "." to RS\* retroactive to 2021textp16 is a tumor suppressor protein also known as cyclin-dependent kinase inhibitor 2A. The p16 biomarker is over-expressed (produced) in response to HPV. It is therefore a surrogate marker for HPV disease.RSTumorPatients with HPV have a different survival or outcome so it is important to be able to distinguish this by documenting the p16 results. Testing is performed by immunohistochemistry (IHC) which is inexpensive and has near universal availability. It has an easily standardized interpretation. HPV testing is usually performed through DNA testing which is more expensive and less widely available. HPV testing also has technically more variability with the interpretation.A,C,I,MStage/Prognostic FactorsRSSEER222022
3957LN Status PelviclnStatusPelvic1This data item describes the status of pelvic lymph nodes associated with certain female genital cancers.0, 1, 8, 9Lymph Node Status: PelvicRS*RStext.TumorSpecific regional lymph node involvement is listed as a Registry Data Collection Variable in AJCC. This information was previously collected as Cervix SSF #2.A,C,I,MStage/Prognostic FactorsRCSEER222022
3958LN Status Para-AorticlnStatusParaAortic1This data item describes the status of para-aortic lymph nodes associated with certain female genital cancers.0, 1, 8, 9Lymph Node Status: Para-aorticRS*RStext.TumorSpecific regional lymph node involvement is listed as a Registry Data Collection Variable in AJCC. This information was previously collected as Vagina SSF #4. See Lymph Node Assessment Methods and Status for Regional and Distant Lymph Nodes in GYN sites for additional information.A,C,I,MStage/Prognostic FactorsRCSEER222022
3959LN Status Femoral-InguinallnStatusFemoralInguinal1This data item describes the status of femoral-inguinal lymph nodes associated with certain female genital cancers.0, 1, 8, 9Lymph Node Status: Femoral-InguinalRS*RStext.TumorSpecific regional lymph node involvement is listed as a Registry Data Collection Variable in AJCC. See Lymph Node Assessment Methods and Status for Regional and Distant Lymph Nodes in GYN sites for additional information.A,C,I,MStage/Prognostic FactorsRCSEER222022
3960Histologic SubtypehistologicSubtype1Histology code for appendiceal tumors (8480) is defined as “Mucinous Adenocarcinoma (in situ or invasive).” In the AJCC 8th chapter for Appendix-Carcinoma, there are also low-grade appendiceal mucinous neoplasm (LAMN) and high-grade appendiceal mucinous neoplasm (HAMN) diagnoses that are assigned the same histology. Due to the different natures of these histologies, there is interest in tracking these different types of tumors. With the current histology codes, a distinction cannot be made. A histology subtype data item is needed. 0, 1, 2, 3, 4RS*RSdigitsNumericRS*TumorA,C,I,MStage/Prognostic FactorsRSSEER232023
3961Clinical Margin WidthclinicalMarginWidth4Clinical Margin Width describes the margins from a wide excision for a melanoma primary. The margin width is measured by the surgeon prior to the procedure. The measurement is taken, in centimeters, from the edge of the lesion or the prior excision scar to the peripheral margin of the specimen.0.1, 0.2-9.9, XX.1, XX.8.RStext.TumorClinical margin width for wide local excision of a melanoma is based on the original Breslow thickness of the primary tumor, as indicated on the initial biopsy pathology report.A,C,I,MRevised; 9/02/2025 SEER revised "RS" to "RC"RevisedStage/Prognostic FactorsRCCoC20232023
3964Brain Primary Tumor LocationbrainPrimaryTumorLocation1The Pons and other subsites of the Brain Stem have the same ICD-O topography code (C717), which is for subsites of the Brain Stem. Clinically, information regarding the Pons is very important, especially for pediatric cases. A schema discriminator is necessary to distinguish between the pons and other subsites of the brain stem.1, 2, 8, 9, BlankRS*R**Note 1:** This SSDI is effective for diagnosis years 2024+ * For cases diagnosed 2018-2023, leave this SSDI blanknumericRSTumorThe pons site is the third most common site for pediatric brain tumors and there is currently no way to identify tumors that occur in this site. Surgery is too dangerous for these types of tumors. Needle biopsies are also dangerous and extremely rare. Without pathology specimens, accurate histology is elusive making accurate incidence not possible. A cascade of implications results without accurate incidence including support for drug development.A,C,I,MRevised; SEER updated 07/18/2023Stage/Prognostic FactorsRSSEER242024
7010Path Reporting Fac ID 1pathReportingFacId125An identifying code (for example, a CLIA number) that uniquely identifies the pathology facility sending the first report of the case. This data item accommodates information for only one path report. If additional path reports were prepared, enter the identifying code of pathology facility sending the report in Path Reporting Fac ID 2 through Path Reporting Fac ID 5 [7011-7014]. Information in this data item should refer to the path report described in data items 7100, 7090, 7190, 7320, and 7480.BHS-4 Batch Sending Facility #0084, MSH-4 Sending Facility (Name) #00004 (HL7)..textLeft justified, alphanumeric.TumorClinical Laboratory Improvement Act Identification Numbers (CLIAs) are used for laboratory reporting.   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>A,MPathology.HL7122010
7011Path Reporting Fac ID 2pathReportingFacId225An identifying code (for example, a CLIA number) that uniquely identifies the pathology facility sending the second report of the case. This data item accommodates information for only one path report. If additional path reports were prepared, enter the identifying code of pathology facility sending the report in Path Reporting Fac ID 3 through Path Reporting Fac ID 5 [7012-7014]. Information in this data item should refer to the path report described in data items 7101, 7091, 7191, 7321, and 7481.BHS-4 Batch Sending Facility #0084, MSH-4 Sending Facility (Name) #00004 (HL7)..textLeft justified, alphanumeric.TumorClinical Laboratory Improvement Act Identification Numbers (CLIAs) are used for laboratory reporting. 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>A,MPathology.HL7
7012Path Reporting Fac ID 3pathReportingFacId325An identifying code (for example, a CLIA number) that uniquely identifies the pathology facility sending the third report of the case. This data item accommodates information for only one path report. If additional path reports were prepared, enter the identifying code of pathology facility sending the report in Path Reporting Fac ID 4 through Path Reporting Fac ID 5 [7013-7014]. Information in this data item should refer to the path report described in data items 7102, 7092, 7192, 7322, and 7482.BHS-4 Batch Sending Facility #0084, MSH-4 Sending Facility (Name) #00004 (HL7)..textLeft justified, alphanumeric.TumorClinical Laboratory Improvement Act Identification Numbers (CLIAs) are used for laboratory reporting. 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>A,MPathology.HL7122010
7013Path Reporting Fac ID 4pathReportingFacId425An identifying code (for example, a CLIA number) that uniquely identifies the pathology facility sending the fourth report of the case. This data item accommodates information for only one path report. If an additional path report was prepared, enter the identifying code of pathology facility sending the report in Path Reporting Fac ID 5 [7014]. Information in this data item should refer to the path report described in data items 7103, 7093, 7193, 7323, and 7483.BHS-4 Batch Sending Facility #0084, MSH-4 Sending Facility (Name) #00004 (HL7)..textLeft justified, alphanumeric.TumorClinical Laboratory Improvement Act Identification Numbers (CLIAs) are used for laboratory reporting. 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>A,MPathology.HL7122010
7014Path Reporting Fac ID 5pathReportingFacId525An identifying code (for example, a CLIA number) that uniquely identifies the pathology facility sending the fifth report of the case. Information in this data item should refer to the path report described in data items 7104, 7094, 7194, 7324, and 7484.BHS-4 Batch Sending Facility #0084, MSH-4 Sending Facility (Name) #00004 (HL7)..textLeft justified, alphanumeric.TumorClinical Laboratory Improvement Act Identification Numbers (CLIAs) are used for laboratory reporting. 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>A,MPathology.HL7122010
7090Path Report Number 1pathReportNumber120Unique sequential number assigned by a laboratory to the first report for this case. This item accommodates only one path report. When information is available for more than one path report, enter the path report number(s) in Path Report No 2 through Path Report No 5 [7091-7094]. Information in this data item should refer to the path report described in data items 7010, 7100, 7190, 7320, and 7480.   Note: In some cases the HL7 field length as sent by the laboratory may be longer than 20.OBR-3 Filler Order Number #00217 (HL7), Path Report Number..textLeft justified, alphanumeric.TumorThe pathology report number provides a cross reference that identifies the specimen at the pathology facility. It may be useful for follow back with the pathology facility.   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>A,MPathology.HL7122010
7091Path Report Number 2pathReportNumber220Unique sequential number assigned by a laboratory to the second report for this case. This item accommodates only one path report. When information is available for more than two path reports, enter the path report number(s) in Path Report No 3 through Path Report No 5 [7092-7094]. Information in this data item should refer to the path report described in data items 7011, 7101, 7191, 7321, and 7481.   Note: In some cases the HL7 field length as sent by the laboratory may be longer than 20.OBR-3 Filler Order Number #00217 (HL7), Path Report Number..textLeft justified, alphanumeric.TumorThe pathology report number provides a cross reference that identifies the specimen at the pathology facility. It may be useful for follow back with the pathology facility. 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>A,MPathology.HL7122010
7092Path Report Number 3pathReportNumber320Unique sequential number assigned by a laboratory to the third report for this case. This item accommodates only one path report. When information is available for more than three path reports, enter the path report number(s) in Path Report No 4 through Path Report No 5 [7093-7094]. Information in this data item should refer to the path report described in data items 7012, 7102, 7192, 7322, and 7482.   Note: In some cases the HL7 field length as sent by the laboratory may be longer than 20.OBR-3 Filler Order Number #00217 (HL7), Path Report Number..textLeft justified, alphanumeric.TumorThe pathology report number provides a cross reference that identifies the specimen at the pathology facility. It may be useful for follow back with the pathology facility. 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>A,MPathology.HL7122010
7093Path Report Number 4pathReportNumber420Unique sequential number assigned by a laboratory to the fourth report for this case. This item accommodates only one path report. When information is available for more than four path reports, enter the path report number in Path Report No 5 [7094]. Information in this data item should refer to the path report described in data items 7013, 7103, 7193, 7323, and 7483.   Note: In some cases the HL7 field length as sent by the laboratory may be longer than 20.OBR-3 Filler Order Number #00217 (HL7), Path Report Number..textLeft justified, alphanumeric.TumorThe pathology report number provides a cross reference that identifies the specimen at the pathology facility. It may be useful for follow back with the pathology facility. 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>A,MPathology.HL7122010
7094Path Report Number 5pathReportNumber520Unique sequential number assigned by a laboratory to the fifth report for this case. This item accommodates only one path report. Information in this data item should refer to the path report described in data items 7014, 7104, 7194, 7324, and 7484.   Note: In some cases the HL7 field length as sent by the laboratory may be longer than 20.OBR-3 Filler Order Number #00217 (HL7), Path Report Number..textLeft justified, alphanumeric.TumorThe pathology report number provides a cross reference that identifies the specimen at the pathology facility. It may be useful for follow back with the pathology facility. 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>A,MPathology.HL7122010
7100Path Order Phys Lic No 1pathOrderPhysLicNo120License 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.OBR-16 Ordering Provider (License Number) #00226, Path Ordering Client/Phys--Lic No...textLeft justified, alphanumeric, no embedded blanks.TumorCancer 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>A,MPathology.HL7122010
7101Path Order Phys Lic No 2pathOrderPhysLicNo220License 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.OBR-16 Ordering Provider (License Number) #00226, Path Ordering Client/Phys--Lic No...textLeft justified, alphanumeric, no embedded blanks.TumorCancer 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>A,MPathology.HL7122010
7102Path Order Phys Lic No 3pathOrderPhysLicNo320License 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.OBR-16 Ordering Provider (License Number) #00226, Path Ordering Client/Phys--Lic No...textLeft justified, alphanumeric, no embedded blanks.TumorCancer 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>A,MPathology.HL7122010
7103Path Order Phys Lic No 4pathOrderPhysLicNo420License 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.OBR-16 Ordering Provider (License Number) #00226, Path Ordering Client/Phys--Lic No...textleft justified, alphanumeric, no embedded blanks.TumorCancer 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>A,MPathology.HL7122010
7104Path Order Phys Lic No 5pathOrderPhysLicNo520License 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...textleft justified, alphanumeric, no embedded blanks.TumorCancer 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>A,MPathology.HL7122010
7190Path Ordering Fac No 1pathOrderingFacNo125Facility 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.blankORC-21 Ordering Facility Name #01311 (HL7), Path Ordering Facility Number (AHA Number)..textLeft justified, alphanumeric.TumorThe 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> A,MPathology.HL7122010
7191Path Ordering Fac No 2pathOrderingFacNo225Facility 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.blankORC-21 Ordering Facility Name #01311 (HL7), Path Ordering Facility Number (AHA Number)..textLeft justified, alphanumeric.TumorThe 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>A,MPathology.HL7122010
7192Path Ordering Fac No 3pathOrderingFacNo325Facility 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.blankORC-21 Ordering Facility Name #01311 (HL7), Path Ordering Facility Number (AHA Number)..textLeft justified, alphanumeric.TumorThe 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>A,MPathology.HL7122010
7193Path Ordering Fac No 4pathOrderingFacNo425Facility 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.blankORC-21 Ordering Facility Name #01311 (HL7), Path Ordering Facility Number (AHA Number)..textLeft justified, alphanumeric.TumorThe 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>A,MPathology.HL7122010
7194Path Ordering Fac No 5pathOrderingFacNo525Facility 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 standard-setting organization such as the American College of Surgeons (ACoS) or Clinical Laboratory Improvement Amendments (CLIA). This item accommodates only one path report. Information in this data item should refer to the path report described in data items 7014, 7094, 7104, 7324, and 7484.blankORC-21 Ordering Facility Name #01311 (HL7), Path Ordering Facility Number (AHA Number)..textLeft justified, alphanumeric.TumorThe 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>A,MPathology.HL7122010
7320Path Date Spec Collect 1pathDateSpecCollect125Records 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 and time (YYYY-MM-DDThh:mm:ss+zz:zz). Partial dates are allowed (e.g. year + month).”   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.Valid dateTimeOBR-7 Observation Date/Time #00241 (HL7), Path--Date Spec Collection..dateTimeYYYY-MM-DDThh:mm:ss+zz:zz.TumorCancer 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\>A,MPathology.HL7122010
7321Path Date Spec Collect 2pathDateSpecCollect225Records 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 and time (YYYY-MM-DDThh:mm:ss+zz:zz). Partial dates are allowed (e.g. year + month).”Valid dateTimesOBR-7 Observation Date/Time #00241 (HL7), Path--Date Spec Collection..dateTimeYYYY-MM-DDThh:mm:ss+zz:zz.TumorCancer 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\>A,MPathology.HL7122010
7322Path Date Spec Collect 3pathDateSpecCollect325Records 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 and time (YYYY-MM-DDThh:mm:ss+zz:zz). Partial dates are allowed (e.g. year + month). 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.Valid dateTimesOBR-7 Observation Date/Time #00241 (HL7), Path--Date Spec Collection..dateTimeYYYY-MM-DDThh:mm:ss+zz:zz.TumorCancer 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\>A,MPathology.HL7122010
7323Path Date Spec Collect 4pathDateSpecCollect425Records 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 and time (YYYY-MM-DDThh:mm:ss+zz:zz). Partial dates are allowed (e.g. year + month).   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.Valid dateTimesOBR-7 Observation Date/Time #00241 (HL7), Path--Date Spec Collection..dateTimeYYYY-MM-DDThh:mm:ss+zz:zz.TumorCancer 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\>A,MPathology.HL7122010
7324Path Date Spec Collect 5pathDateSpecCollect525Records 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 and time (YYYY-MM-DDThh:mm:ss+zz:zz). Partial dates are allowed (e.g. year + month). 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.Valid dateTimesOBR-7 Observation Date/Time #00241 (HL7), Path--Date Spec Collection..mixedYYYY-MM-DDThh:mm:ss+zz:zz.TumorCancer 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\>A,MPathology.HL7122010
7480Path Report Type 1pathReportType12This field reflects the type of report transmitted to the cancer registry and may need to be classified at the central cancer registry. This data item accommodates information for only one path report. If additional path reports were prepared, enter the path report type(s) in Path Report Type 2 through Path Report Type 5 [7481-7484]. Information in this data item should refer to the path report described in data items 7010, 7100, 7090, 7190, and 7320.01-11, 98, 99OBR-4 Universal Service ID #00238 (HL7), Path--Report Type..digitsRight justified, zero filled.TumorThis variable is primarily used for administrative purposes at the cancer registry.   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>A,MPathology.HL7122010
7481Path Report Type 2pathReportType22This field reflects the type of report transmitted to the cancer registry and may need to be classified at the central cancer registry. This data item accommodates information for only one path report. If additional path reports were prepared, enter the path report type(s) in Path Report Type 3 through Path Report Type 5 [7482-7484]. Information in this data item should refer to the path report described in data items 7011, 7101, 7091, 7191, and 7321.01-11, 98, 99OBR-4 Universal Service ID #00238 (HL7), Path--Report Type..digitsRight justified, zero filled.TumorThis variable is primarily used for administrative purposes at the cancer registry. 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>A,MPathology.HL7122010
7482Path Report Type 3pathReportType32This field reflects the type of report transmitted to the cancer registry and may need to be classified at the central cancer registry. This data item accommodates information for only one path report. If additional path reports were prepared, enter the path report type(s) in Path Report Type 4 through Path Report Type 5 [7433-7484]. Information in this data item should refer to the path report described in data items 7012, 7102, 7092, 7192, and 7322.01-11, 98, 99OBR-4 Universal Service ID #00238 (HL7), Path--Report Type..digitsRight justified, zero filled.TumorThis variable is primarily used for administrative purposes at the cancer registry. 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>A,MPathology.HL7122010
7483Path Report Type 4pathReportType42This field reflects the type of report transmitted to the cancer registry and may need to be classified at the central cancer registry. This data item accommodates information for only one path report. If an additional path report was prepared, enter the path report type in Path Report Path Report Type 5 [7484]. Information in this data item should refer to the path report described in data items 7013, 7103, 7093, 7193, and 7323.01-11, 98, 99OBR-4 Universal Service ID #00238 (HL7), Path--Report Type..digitsRight justified, zero filled.TumorThis variable is primarily used for administrative purposes at the cancer registry. 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>A,MPathology.HL7122010
7484Path Report Type 5pathReportType52This field reflects the type of report transmitted to the cancer registry and may need to be classified at the central cancer registry. This data item accommodates information for only one path report. Information in this data item should refer to the path report described in data items 7014, 7104, 7094, 7194, and 7324.01-11, 98, 99OBR-4 Universal Service ID #00238 (HL7), Path--Report Type..digitsRight justified, zero filled.TumorThis variable is primarily used for administrative purposes at the cancer registry. 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>A,MPathology.HL7122010