Report | Question ID | Question | Discussion | Answer | Year |
---|---|---|---|---|---|
|
20041088 | CS Extension/EOD Extension--Renal Pelvis: Primary site is renal pelvis with direct extension to the rt adrenal gland. What is the correct extension code? | This answer was provided in the context of CSv1 coding guidelines. The response may not be used after your registry database has been converted to CSv2. Assign CS Extension code 67 [Adrenal gland from renal pelvis] for adrenal extension from renal pelvis -- T4 and regional direct extension. |
2004 | |
|
20051075 | CS Extension--Breast: How is this field coded when path describes dermal lymphatic invasion of the nipple? See Discussion. | Example Multicentric infiltrating lobular carcinoma of left breast treated with MRM. Microscopic summary: Blood/lymphatic Vessel Invasion: present. Path final diagnosis: Angiolymphatic invasion present, including dermal lymphatic invasion in nipple. Micro: There is angiolymphatic invasion, including dermal capillary invasion identified in sections of the nipple. The path report describes multiple breast tumors, none of which is located adjacent to the nipple. |
This answer was provided in the context of CSv1 coding guidelines. The response may not be used after your registry database has been converted to CSv2. Assign CS Extension code 20 [Invasion of subcutaneous tissue...] based on the final diagnosis on the path report. There is "dermal lymphatic invasion in nipple." In this case, the stage will be determined by the tumor size. |
2005 |
|
20051101 | CS Extension--Cervix: How are "positive pelvic washings" coded for a cervical primary? | This answer was provided in the context of CSv1 coding guidelines. The response may not be used after your registry database has been converted to CSv2. According to the CS Steering Committee, positive pelvic washings for primary cervical cancer are not part of the staging criteria in the collaborative staging system (nor in TNM and FIGO). Document positive pelvic washings in a text field. The CS steering committee will add a statement to CS extension to clarify this for cervix uteri. |
2005 | |
|
20061063 | CS Extension--Lung: Do notes 6A and 6B in the 2004 SEER manual offer conflicting instruction for determining the significance of pleural effusion for this primary site? See Discussion. | 1. Is note B to be used to modify or change what note A states? Does note B state -- If a pleural fluid bx(s) is negative; but the fluid is bloody and/or is an exudate, and clinical judgment indicates the effusion is related to tumor -- use code 72? If a pleural effusion is biopsied should the pathology report state the color of the pleural fluid or is an exudate? (Training issue)
2. Do the following clinical findings impact the clinical evaluation of involvement for a pleural effusion? If yes, why? (Training issue(s)) a. Heart problems? b. The location of the pleural effusion? i. Bilateral pleural effusion is noted; tumor in Rt or Lt lung only? ii. Bilateral pleural effusion is noted; tumor in both lungs? iii. Pleural effusion is noted on the opposite side from the tumor? iv. Pleural effusion is on same side as the tumor?
SUPPORTING CS MANUAL DOCUMENTATION Note 6: Pleural Effusion. A. Note from SEER manual: Ignore pleural effusion that is negative for tumor. Assume that a pleural effusion is negative if a resection is done. B. Note from AJCC manual: Most pleural effusions associated with lung cancers are due to tumor. However, there are a few patients in whom multiple cytopathologic examinations of pleural fluid are negative for tumor. In these cases, fluid is non-bloody and is not an exudate. When these elements and clinical judgment dictate that the effusion is not related to the tumor, the effusion should be excluded as a staging element and the patient should be staged T1, or T2, or T3. |
This answer was provided in the context of CSv1 coding guidelines. The response may not be used after your registry database has been converted to CSv2. 1. Note B does not modify or change note A. Note B is explaining when an effusion should not be used to determine the stage. Pleural effusions are evaluated by cytology, not biopsy. 2. If relevant, the clinician should document the fact in the medical record. Heart problems can cause non-malignant pleural effusions (that are disregarded for staging). Pleural effusion will almost always be around the lower lobes due to gravity, but may envelop an entire lung. Pleural effusions can be unilateral or bilateral regardless of the location of the tumor, but are usually on the side where the tumor is. |
2006 |
|
20071037 | CS Extension--Breast: Is the term "erosion" the same as "ulceration"? | This answer was provided in the context of CSv1 coding guidelines. The response may not be used after your registry database has been converted to CSv2. "Erosion" is not synonymous with "ulceration" when coding CS extension for breast. |
2007 | |
|
20091124 | CS Eval--Lung: How is the CS Reg Nodes Eval field to be coded when the FNA of a paratracheal lymph node is positive for adenocarcinoma and the patient subsequently undergoes neoadjuvant chemoradiation therapy followed by an excision of multiple lymph node fragments that show adenocarcinoma? See Discussion. | The CSv1 scheme for lung shows that code 1 under CS Reg Nodes Eval is a path staging basis. However, the definition for code 1 also states that no regional lymph nodes were removed for examination. Would we use code 1 because the case represents path staging basis? If we select code 5 because regional lymph nodes were dissected, the staging basis would be clinical. If we select code 6, the staging basis would be y. | This answer was provided in the context of CSv1 coding guidelines. The response may not be used after your registry database has been converted to CSv2.
Use code "6" for the CS LN evaluation field. As explained on page 113 in the 2007 SEER Manual, when post-operative disease is more extensive despite neoadjuvant therapy, this can be coded in the evaluation field. In this case, only an FNA was done on lymph nodes pre-operatively, but actual lymph nodes were removed and documented in the post-neoadjuvant excision of the lymph nodes which documented that they are histologically positive -- proving that the neoadjuvant therapy did not work. |
2009 |
|
20041031 | CS Extension--Bladder: How should this field be coded when the pathology states "papillary transitional cell carcinoma with no invasion into the submucosa or deep muscularis" but there is "focal extension of tumor into bladder diverticula"? | This answer was provided in the context of CSv1 coding guidelines. The response may not be used after your registry database has been converted to CSv2. Code the CS Extension field to 01 [Papillary transitional cell carcinoma stated to be noninvasive]. Extension into bladder diverticula does not change the code. Diverticula are pouches in the mucosa (mucous membrane). |
2004 | |
|
20020059 | Grade, Differentiation: Can a FIGO grade be coded in this field or is the FIGO grading system to be used only for EOD/Stage coding? |
This answer pertains to cases prior to 2014. For cases diagnosed 2014 and forward, see http://seer.cancer.gov/tools/grade/
Do not use FIGO grade to code differentiation.
FIGO grade is something completely different from FIGO stage. FIGO stage is used to code EOD. FIGO grade is based on the percentage of non-squamous (i.e., solid) portions of the tumor and corresponds roughly to a three grade differentiation system: grade I, well differentiated (=<5% solid component); grade II, moderately differentiated (>5 - 50% solid); and grade III, poorly differentiated (> 50% solid). SEER is evaluating whether the ICD-O-3 6th digit differentiation codes (four grade categories) accurately represent the FIGO grade. For the time being, do not code FIGO grade.
For a diagnosis that includes commonly used differentiation term with a FIGO grade, such as "Moderately differentiated, FIGO grade II," disregard the FIGO grade and code the Grade, Differentiation field according to the term "Moderately differentiated." |
2002 | |
|
20160068 | Reportability--Brain and CNS: Are sphenoid wing meningiomas reportable? See discussion. |
It's my understanding that true intraosseous meningiomas are very rare. It's also my understanding that cranial meninges DO cover the sphenoid wing, so I'm wondering if it's possible to have a meningioma of the sphenoid wing on imaging that arises from the meninges NOT the bone. Is that the deciding factor on reportability? It's been suggested to me that meninges cells do lie within the bone, but again if a meningioma is described as being located at the sphenoid wing on imaging, without bone involvement - and no surgery is performed - I do not understand why it is specifically excluded as non-reportable. |
This answer pertains to cases diagnosed prior to 2018. For 2018 and later cases, refer to the Non-Malignant CNS Solid Tumor Rules. Note: This answer updates previous answers which have been removed from the SEER Inquiry System. Intraosseous meningiomas are not reportable. You are correct, these are rare meningiomas originating in bone. The term "sphenoid wing meningioma" is sometimes used for an intraosseous meningioma of the sphenoid bone. Yes, it's possible to have a meningioma of the sphenoid wing on imaging that arises from the meninges NOT the bone. Read the available information carefully. When the site of origin is described as "along the sphenoid wing" or "overlying the sphenoid wing" report the meningioma. These descriptions indicate that the meningioma originates from the meninges covering bone rather than the bone itself. Meningioma arising in bone is rare enough, that when present, we would expect it to be clearly stated as such. In the absence of a statement indicating origin in bone, the meningioma is most likely arising from meninges covering the bone. |
2016 |
|
20130033 | Histology--Heme & Lymphoid Neoplasms: How is the histology coded for a low grade B-cell lymphoma with plasmacytic differentiation? |
This answer has been corrected. Previous answer is shown below under "History." Assign 9591/3 for this case. See also SINQ 20190070. |
2013 |