System Guide
Back to Search Results

Search Results

Display Options
Display Options
Select Fields
Export Results to CSV Create Report 0
+ Add all results to report

Report Produced: 01/14/2026 12:48 PM

Report Question ID Question Discussion Answer Year
20091046 CS Lymph Nodes/CS Site Specific Factor--Melanoma: When CS Lymph Nodes is coded 13, 14 or 15 (codes used when satellite nodule(s) or in-transit metastases are present), why must CS SSF 3 be coded 000 (No lymph node metastasis)? See Discussion.

3/11/05 Consult - PE: huge exophytic lesion right lower leg (mushroom-type lesion), 6cm. Below that lesion is another ulcerative lesion 2cm. Right upper arm lesion w/ satellite nodule. Note from physician states malignant melanoma on right lower leg metastatic to the left arm/shoulder. No scans done so there is no assessment of the lymph nodes.

We coded CS LNS to 13, which captures the satellite nodule, CS SSF3 = 999 and CS Reg Nodes Eval = 0. SEER Edit 216 requires the SSF3 to be 000. SSF 3 is coded 999 as there is no information about the clinical status of lymph nodes.

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.When CS lymph nodes is coded 13-15, SSF 3 must be coded 000. Follow the instruction in the SSF 3 Note: Use code 000, No lymph node metastases, if ... there are satellite nodules or in-transit metastases, but no regional lymph node metastases, i.e., CS Lymph Nodes is coded 13-15.

For this case, assign CS lymph node code 15 [Satellite nodule(s) or in-transit metastases greater than 2cm from primary tumor WITHOUT regional lymph node involvement or involvement of regional nodes not stated]. The arm lesion is more than 2cm from the leg lesion.

 2009
20081103 CS Lymph Nodes--Breast: What code should be used for the the following? There is no mention of LNS clinically; the patient has neoadjuvant therapy; and the LNS are matted pathologically.

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 the information from the pathologic evaluation to code CS Lymph nodes.

In the nodes evaluation field, assign code 6 [Regional lymph nodes removed for examination with pre-surgical systemic treatment or radiation and lymph node evaluation based on pathologic evidence]. See CS Lymph Nodes note 4.

 2008
20051112 Collaborative Staging--Hematopoietic, NOS: Which Collaborative Staging schema is used for a connective, subcutaneous and soft tissue primary of the pelvis [C495] with the morphology of Langerhans cell sarcoma [9756/39]? See Discussion. On page C-411 of the SEER manual for the connective, subcutaneous, and other soft tissues schema it lists exceptions for certain morphologies and the above is not listed as an exception. On the Hematopoietic scheme it lists the above morphology.

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 the hematopoietic schema on page C-709 of the 2004 SEER manual. The histologically defined schemas have priority over the site schemas when both apply. See page 115 of the 2004 SEER manual.

The morphology codes listed on page C-411 pertain to the SEER Site Specific Guidelines.

 2005
20081080 CS Lymph Nodes/CS Site Specific Factor--Head and Neck: How should these fields be coded when the information is from an out of state data exchange and the record provides no supporting text, all the required fields are not coded and the codes that are provided are in conflict? See Discussion. A parotid case with CS LN coded to 10 [single positive ipsilateral regional node]; Regional LNs Positive coded to 68 and Regional LNs Examined coded to 74. No SSFs were coded. Based on the number of nodes coded as positive, the CS LN code was incorrect. Because the only information available to the central registry was that multiple regional LNs NOS were positive, we coded CS LN to 80 [lymph nodes NOS] and coded all SSFs to 999. Upon running the SEER edits, this case popped up on edits yielding a CS Site-Specific Factor codes, CS Lymph Nodes and Head/Neck Schemas conflict. Provide some guidance as how to properly code CS LNs & SSFs 1-6 for this case given the very limited information provided to us?

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.This is an unusual situation with conflicting information. If possible, request the pathology report and/or audit the case.

If you cannot obtain any further information or clarification, there are two choices:

  • Code CS LN's 80; code SSF 1 & 2 999, code SSF 3-6 000.

  • Code CS LN's 99; code SSF 1-6 999.

    		•  2008
    		20091035 CS Extension--Ovary: What code is used to capture omental caking?

    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.The term "omental caking" refers to a thickened omentum. In the case of ovarian cancer, omental caking is always indicative of involvement of the omentum. The omentum is an abdominal structure for the purposes of CS extension. Assign the appropriate code between 70-73.

    When the size of implants is not stated, but operative report and scans state omental caking, code 71 would be best. When there are no size measurements on the operative report or scan or elsewhere, there is not enough information to assign 72. The choice of code between 70 and 73 will depend on the details of the specific case.

    		 2009
    		20051074 CS Extension/CS Lymph Nodes--Colon: What codes are used when large vessel invasion (V2 grossly evident) is stated to be present on a pathology report? See Discussion.

    Example

    Cecum, right hemicolectomy: poorly differentiated invasive adenocarcinoma of the cecum. Large vessel invasion (V2-grossly evident) is present. Microscopic description: The grossly described matted lymph node tissue shows an irregular nuclear contour and is classified as V2, grossly evident venous invasion based on staging criteria of the AJCC Cancer Staging Manual, 6th Edition.

    Per note 2 in the coding scheme for CS-Extension, a nodule with irregular contour in the pericolic adipose tissue should be coded in CS-Extension to code 45. Is the large vessel invasion described in the path report the same process as a tumor nodule in pericolic fat? Should note 2 be used and CS-Extension coded to 45?

    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.The description of large vessel invasion and irregular nuclear contour from the example above describes grossly matted LYMPH NODE tissue. Do not code this in the CS Extension field. Code the CS Lymph Nodes field appropriately based on the rest of the information for this case.

    When large vessel invasion and irregular nuclear contour is used to describe a "tumor nodule," rather than a recognizable lymph node, code it in the CS extension field.

    		 2005
    		20091038 CS Tumor Size--Breast: Do the tumor size instructions in the CS Manual take priority over those in the SEER manual? See Discussion. In regards to priority order of sources to be used in coding size for breast and lung, we are instructed to use the site-specific instructions in the 2004 SEER Manual over the general instructions in the CS Manual (see SINQ 20061109). Thus, physical exam size would be used over an imaging size. I&R question 2389 instructs registrars to use an imaging size over a physical exam size. This inconsistency creates confusion for them. Do the answers given in I&R not take into account the information in the SEER Manual? As a SEER Registry, which rules do we tell our hospitals to use? Are ACoS accredited hospitals required to use I&R over SINQ?

    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.The current SEER instructions and the CS instructions for source of tumor size information are the same. The tumor size priority source instruction in the 2004 SEER manual is not included in the 2007 SEER manual. SINQ 20061109 has been updated for clarification. There is no conflict between SEER instructions and I&R instructions at this time. SEER and the CoC collaborate, endeavoring to provide consistent instructions and to resolve inconsistencies.

    		 2009
    		20061001 2004 SEER Manual Errata/CS Lymph Nodes--Head & Neck: On page C-353, in the supraglottic larynx schema, there is no mention of Level IV nodes in the CS Lymph Node codes.

    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.The CS Steering Committee is aware of this issue and is working to resolve it.

    		 2006
    		20081007 CS Extension--Lung: How is "subpleural extension" coded?

    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.Subpleural extension means that the tumor extends to the subpleural space, but the pleura itself is not involved. Assign the appropriate extension code based on the other facts for the case. Do not code pleural involvement.

    		 2008
    		20061019

    CS Site Specific Factor 6--Breast: If the tumor size for the breast is unknown, and it is unknown whether the tumor is mixed in situ and invasive or "pure", how is SSF6 to be coded? See Discussion.

    The definition for SSF6 for breast changed from "Unknown if invasive and in situ components present, unknown if tumor size represents mixed tumor or a pure tumor" to an added clarification of "Clinical tumor size coded." Since the clinical tumor size is NOT coded, this does not fit.

    The definition for 060 is "Invasive and in situ components present, unknown size of tumor (CS Tumor Size coded 999). Since it is unknown if the tumor is mixed, this definition does not fit either.

    It seems that the revised (April 2005) definition for 888 has left a situation that cannot be coded.

    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.SSF 6 should be coded 888 in this case. SEER will make the CS task force aware of this situation.

    		 2006