SEER Inquiry System - Search

For cases diagnosed 2010 and forward, access the Hematopoietic Database at http://seer.cancer.gov/seertools/hemelymph.

This case should be accessioned as two primaries: follicular lymphoma [9690/3] diagnosed 02/17/2012 and diffuse large B-cell lymphoma [9680/3] diagnosed 10/16/2012 per Rule M10. This patient was diagnosed with a chronic neoplasm (follicular lymphoma) followed greater than 21 days later by an acute neoplasm (DLBCL).

The follicular lymphoma was initially diagnosed on 02/17/2012. The cervical node biopsies were "highly suspicious for B-cell lymphoma" [9591/3]. While "suspicious" is a reportable ambiguous term used to accession cases, suspicious cytologies are not SEER reportable and, therefore, the diagnosis date cannot be 01/27/2012. The histology of the first primary would be updated to 9690/3 [follicular lymphoma] based on the Medical Oncology note on 04/18/2012 that confirmed the histology was follicular lymphoma and the patient was being treated for such.

The diagnosis of DLBCL was made 8 months later. Rule M4 cannot apply to this case because the follicular lymphoma and DLBCL were not diagnosed simultaneously. Rule M4 only applies when the two non-Hodgkin lymphomas are diagnosed simultaneously AND in the same location.

SEER*Educate provides training on how to use the Heme Manual and DB. If you are unsure how to arrive at the answer in this SINQ question, refer to SEER*Educate to practice coding hematopoietic and lymphoid neoplasms. Review the step-by-step instructions provided for each case scenario to learn how to use the application and manual to arrive at the answer provided. https://educate.fhcrc.org/LandingPage.aspx.

Vascular tumors of the CNS are reportable when they arise in the dura or parenchyma of the CNS and should be coded accordingly. The instructions in the CDC book regarding primary site coding are not the most current instructions.SEER assumed responsibility for brain and CNS reporting instructions in 2007.

The tumor in SINQ 20120034 is not reportable because it arises in a blood vessel. The cavernous hemangioma in SINQ 20081113 is reportable because the primary site is the white matter of the cerebral cortex.

For cases diagnosed 2010 and forward, access the Hematopoietic Database at http://seer.cancer.gov/seertools/hemelymph.

Code diagnostic confirmation to 3 [positive histology AND positive immunophenotyping studies (9590/3 - 9992/3)].

Immunoglobulin heavy and light chain genes rearranged is listed under Genetics Data in the Heme DB for 9699/3 [extranodal marginal zone lymphoma]. Given the documentation of this positive genetic finding and the positive bone marrow, code diagnostic confirmation to 3.

SEER*Educate provides training on how to use the Heme Manual and DB. If you are unsure how to arrive at the answer in this SINQ question, refer to SEER*Educate to practice coding hematopoietic and lymphoid neoplasms. Review the step-by-step instructions provided for each case scenario to learn how to use the application and manual to arrive at the answer provided. https://educate.fhcrc.org/LandingPage.aspx.

For cases diagnosed 2010 and forward, access the Hematopoietic Database at http://seer.cancer.gov/seertools/hemelymph.

Per Rule PH24, code primary site to orbit. According to Rule PH24, one is to code the primary site to the organ when lymphoma is present only in an organ. Note 2 under this rule also instructs one to capture the secondary involvement of distant lymph nodes and/or bone marrow in CS extension fields.

If the physician had not confirmed the primary site as orbit, you would have used Rule PH22 when the primary site is not indicated.

SEER*Educate provides training on how to use the Heme Manual and DB. If you are unsure how to arrive at the answer in this SINQ question, refer to SEER*Educate to practice coding hematopoietic and lymphoid neoplasms. Review the step-by-step instructions provided for each case scenario to learn how to use the application and manual to arrive at the answer provided. https://educate.fhcrc.org/LandingPage.aspx.

For cases diagnosed 2010 and forward, access the Hematopoietic Database at http://seer.cancer.gov/seertools/hemelymph.

Polycythemia Vera (PV) [9950/3] is reportable. The Abstractor Notes section in the Hematopoietic Database for PV indicates there are three phases of PV. The third phase is referred to as the "spent" or "post-polycythemic myelofibrosis phase". This patient appears to be in the third phase of PV. This would not be reported as a new primary if PV has already been reported.

SEER*Educate provides training on how to use the Heme Manual and DB. If you are unsure how to arrive at the answer in this SINQ question, refer to SEER*Educate to practice coding hematopoietic and lymphoid neoplasms. Review the step-by-step instructions provided for each case scenario to learn how to use the application and manual to arrive at the answer provided. https://educate.fhcrc.org/LandingPage.aspx.

For cases diagnosed 2010 and forward, access the Hematopoietic Database at http://seer.cancer.gov/seertools/hemelymph.

Polycythemia, NOS is not reportable. Polycythemia, NOS is not a synonym for polycythemia vera and, therefore, is not reportable. To be reportable the diagnosis must be polycythemia vera, or one of the other terms listed in the Alternate Names section of the Heme DB.

Polycythemia (also known as erythrocytosis) is a disease state in which the proportion of blood volume that is occupied by red blood cells increases. Blood volume proportions can be measured as a hematocrit level. It can be due to an increase in the mass of red blood cells ("absolute polycythemia"); or to a decrease in the volume of plasma ("relative polycythemia").

SEER*Educate provides training on how to use the Heme Manual and DB. If you are unsure how to arrive at the answer in this SINQ question, refer to SEER*Educate to practice coding hematopoietic and lymphoid neoplasms. Review the step-by-step instructions provided for each case scenario to learn how to use the application and manual to arrive at the answer provided. https://educate.fhcrc.org/LandingPage.aspx.

For cases diagnosed 2010 and forward, access the Hematopoietic Database at http://seer.cancer.gov/seertools/hemelymph.

This case should be accessioned as a single primary, diffuse large B-cell lymphoma diagnosed in 2011 per Rule M7. Note 4 for Rule M7 states to change the histology code on the original abstract to the more specific histology, diffuse large B-cell lymphoma in this case. There is no time restriction for rule M7. Apply rule PH11 and code the histology as 9680/3 [DLBCL] when both DLBCL and follicular lymphoma are present in the same lymph node(s).

Ambiguous terminology is not used to code a more specific histologic type per the Heme Manual. The information submitted states only that this low grade B-cell lymphoma was "most consistent with follicular lymphoma." The term "consistent with" is an ambiguous term per SEER and cannot be used to code the histology of the 2011 neoplasm as follicular lymphoma. There was no subsequent clinical statement that this patient was diagnosed with follicular lymphoma in 2011.

SEER*Educate provides training on how to use the Heme Manual and DB. If you are unsure how to arrive at the answer in this SINQ question, refer to SEER*Educate to practice coding hematopoietic and lymphoid neoplasms. Review the step-by-step instructions provided for each case scenario to learn how to use the application and manual to arrive at the answer provided. https://educate.fhcrc.org/LandingPage.aspx.

Although the ambiguous terminology on the pathology report is not used to code the histology to follicular lymphoma, had there been a subsequent clinical statement that this patient had follicular lymphoma, the histology would be coded to follicular lymphoma [9690/3]. A diagnosis of follicular lymphoma followed by a diagnosis of DLBCL more than 21 days later is a new primary per rule M12.

For cases diagnosed 2010 and forward, access the Hematopoietic Database at http://seer.cancer.gov/seertools/hemelymph.

Without further information as to the type of acute myeloid leukemia, code the histology to 9861/3 [acute myeloid leukemia, NOS]. If further information on the specific acute myeloid leukemia becomes available, update the histology code.

Document that the pathology report states the acute myeloid leukemia is a "non-M3 type" in a text field. This documentation will help explain the choice of 9861/3 for this case. M3 refers to one of the eight FAB subtypes described by a group of French, American, and British leukemia experts in the 1970's who divided acute myeloid leukemias into subtypes, M0 through M7. They classified the disease based on the type of cell from which the leukemia developed and how mature the cells were. This was based largely on how the leukemia cells looked under the microscope after routine staining.

In this case, all we know is that the histology does not pathologically represent the M3 (acute promyelocytic leukemia (APL)) form of acute myeloid leukemia. We do not know which type of acute myeloid leukemia it does represent.

SEER*Educate provides training on how to use the Heme Manual and DB. If you are unsure how to arrive at the answer in this SINQ question, refer to SEER*Educate to practice coding hematopoietic and lymphoid neoplasms. Review the step-by-step instructions provided for each case scenario to learn how to use the application and manual to arrive at the answer provided. https://educate.fhcrc.org/LandingPage.aspx.

For cases diagnosed 2010 and forward, access the Hematopoietic Database at http://seer.cancer.gov/seertools/hemelymph.

Per Rule M2, this is a single primary. According to Rule M2, the single histology is always the single primary.

SEER*Educate provides training on how to use the Heme Manual and DB. If you are unsure how to arrive at the answer in this SINQ question, refer to SEER*Educate to practice coding hematopoietic and lymphoid neoplasms. Review the step-by-step instructions provided for each case scenario to learn how to use the application and manual to arrive at the answer provided. https://educate.fhcrc.org/LandingPage.aspx.