Report | Question ID | Question | Discussion | Answer | Year |
---|---|---|---|---|---|
|
20081073 | CS Extension/Ambiguous terminology--Pancreas: Should an exception be made for "abuts" or "encased/encasing" regarding CS pancreas extension? See Discussion. |
According to the CS Manual regarding ambiguous terminology, we do not accept "abuts" or "encased/encasing" as involvement. According to the March/April 2008 issue of "CA, A Cancer Journal for Clinicians", vol 58, number 2, an article concerning Pancreas staging by M.D. Anderson researchers/clinicians recommends defining unresectable involvement of the celiac axis/mesenteric artery with the terms "abutment" as involvement of 180 degrees or less of the circumference of the vessel, and "encasement" as more than 180 degree involvement. A large comprehensive cancer center in our area has already adopted these guidelines. |
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.Follow the current CS instructions regarding ambiguous terminology. "Abuts" and "encased/encasing" are not involvement. The American College of Surgeons Commission on Cancer provided the following in response to this question: This concept can be considered for CS version 2, but it would need to be made in conjunction with acceptance of that same theory in AJCC 7th Edition so that the stage can be derived. Many times what can be defined and accepted in a closed environment of a single institution research project cannot be duplicated and accepted across the nation and in every community facility. Would pathologists specify the > or < 180 degree involvement in every pathology report? It would also have to be reviewed to see if this idea has been accepted by the larger oncology community, or just the idea of a single institution. |
2008 |
|
20051143 | CS Extension--Prostate: Can the EOD Manual clarifications regarding apparent and inapparent tumors be used to determine CS clinical extension for prostate primaries? | 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.Do not use the EOD information to determine apparent and inapparent when coding Collaborative Stage for tumors diagnosed 1/1/2004 or later.
The August 2007 CoC Flash stated that "After consultation with the AJCC curators for genitourinary disease, the CS Steering Committee has determined that the SEER list of terms for apparent and inapparent in the SEER Extent of Disease Manual is NOT to be used for interpreting reports for Collaborative Staging. While it was a convenient tool for registrars, the curators are of the opinion that the use of the list will lead to misinterpretation of reports. Rather, the curators recommend that registrars rely on a direct physician statement of apparent or inapparent disease for Collaborative Staging."
August 2007 CoC Flash: http://www.facs.org/cancer/cocflash/august07.pdf, Coding Prostate Cancer: A Message from the Collaborative Staging Steering Committee. |
2005 | |
|
20091073 | Grade: Can FIGO grade be used to code Grade/Differentiation? See Discussion. | SINQ 20020059 says not to use FIGO grade to code differentiation. It also says SEER is evaluating whether the ICD-O-3 sixth digit differentiation codes accurately represent the FIGO grade. For the time being, do not code FIGO grade. What is the result of the evaluation? Any new information regarding FIGO grade? | 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.Do not code FIGO grade in the grade field. The conversion from a three-grade system to a four-grade system does not work for FIGO grade three. Since FIGO G3 includes both Poorly differentiated and undifferentiated, it cannot be converted. FIGO grade may be captured in a CS site specific factor in the future. |
2009 |
|
20081001 | CS Tumor Size: Can an 'ulcerated mass' be used to code CS tumor size? See Discussion.
|
The CS Manual (p. 26, 4.a.) states do not code the size of the polyp, ulcer or cyst. However it states that a 'cystic mass' can be used to code TS if it is the only size given. Scopes Text: 'ulcerated' mass based at anal verge & ext 3-4 cm up into rectum. | 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.Do not code CS Tumor size using the size of an ulcerated mass.
Answer from:
|
2008 |
|
20081116 | CS Extension--Brain and CNS: How is this field coded for a malignant brain tumor that presents as a lesion with significant pressure on the left frontal ventricle and dilation of the right ventricles? See Discussion. | CS Extension code 30 includes tumor that invades or encroaches upon the ventricular system. Does significant pressure mean the same thing as encroach? | 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.Do not assign extension code 30 in this case unless there is evidence elsewhere of ventricular system involvement. "Significant pressure" is not synonymous with encroachment or involvement. See the list of ambiguous terms for CS staging on page 121 of the 2007 SEER manual. |
2008 |
|
20091039 | CS Tumor Size--Lung:. Does code 997 (diffuse, entire lobe) for lung and main stem bronchus take precedence over a stated tumor size? See Discussion. | Per SPCSM 2007 'Coding Instructions for CS Staging Data Items-CS Tumor Size' item 5c states that code 998 (diffuse, entire lung) for lung and main stem bronchus takes precedence over any mention of size. Does this apply to code 997 as well? | 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 stated tumor size rather than 997. Code 997 does not take precedence over tumor size at this time. According to CoC, the instructions in the CS Manual, Part I-27, rule 5c are to alert the user to special circumstances. Code 997 is not included because it is not diffuse for all of the sites listed. The site-specific rules and codes in the schema always take precedence. Further instructions and clarifications will be added to the lung schema, CS Manual Part II-317 in the next version of CS. |
2009 |
|
20071062 | Primary Site: For malignant gastrointestinal tumors (GISTs), how should the primary site be coded and which Collaborative Stage and TNM staging schemes should be used for disease found in the stomach, small intestine or other locations? | 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 primary site to the location where the GIST originated. If the primary site cannot be determined, assign code C809 [Unknown primary site].
GIST of gastrointestinal hollow viscera cannot be staged in TNM. In Collaborative Staging, use the stomach scheme for GIST of the stomach. Use the small intestine scheme for GIST of the small intestine. For GIST of other primary sites, use the CS scheme for the specific site. |
2007 | |
|
20051072 | Primary Site/CS Extension--Lymphoma: Should CS Extension be coded to 22 [Involvement of spleen PLUS lymph node(s) BELOW the diaphragm] or 32 [Involvement of spleen PLUS lymph node(s) on both sides of the diaphragm] for the biopsy proven lymphoma in a retroperitoneal mass and a CT of the chest with nodes described as "indeterminate" or "calcified"? See Discussion. | It was diagnosed on CT-guided biopsy of retroperitoneal mass: obtained access to the posterior aspect of the lesion adjacent to the left side of the spinal column at approx the level of the kidney. CT Abdomen/Pelvis: Large low attenuation & smooth walled regions in hilum of the spleen & into the splenic parenchyma w/assoc smaller lesions in the spleen. Associated adenopathy on left side of aorta between the superior mesenteric artery & renal vein. Body of report: Soft tissue mass 4.4 x 4.8 x 7cm adjacent to the left side of the aorta & spanning the distance betw superior mesenteric vein inferiorly to level of left renal vein, appears to be matted adenopathy. CT Chest: indeterminate nodes in pretracheal region w/calcified nodes in infracarinal region, right perihilar region & calcifications in pulmonary parenchyma of right lung. Calcified nodes & other structures suggest healed granulomatous process. However, with the infarct/mass lesion in the spleen & left periaortic adenopathy, extension of this process to the mediastinum can't be excluded. |
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 primary site C772 [Intra-abdominal lymph nodes]. Assign CS extension code 22 [Involvement of spleen plus lymph nodes below diaphragm]. The description from the chest CT is not sufficient to code lymph node involvement above the diaphragm. |
2005 |
|
20081060 | CS Tumor Size--Lung: If a 5/11/07 CT showed a 6.5 cm LLL mass and a 7/24/07 CT showed 8.4 cm LLL mass, do we code the larger tumor size identified within four months of diagnosis or do we code the first size documented at the time of diagnosis? | 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 larger tumor size. |
2008 | |
|
20041040 | CS Tumor Size--Unknown & ill-defined site: For an unknown primary site, should this field be coded to 000 [No mass/tumor found] or 999 [Unknown; size not stated; not stated in patient record]? | 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 Tumor Size field to 999 [Unknown; size not stated; not stated in patient record] when the primary site is unknown.
There is a discrepancy in Part I of the CS Manual on page 27, rule 5g, which says that primary site C80.9 should be coded as 888 not applicable. The CS Steering Committee has decided that the last line about unknown and ill-defined sites should be deleted from rule 5g. This issue will be addressed in a CS errata to be distributed in July 2004. |
2004 |