TNM Path cN0 2016 (CoC)

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #6026
    AnonymousRuth Li
    Spectator

    We are reviewing the 16E edits to create state-specific edit set and noticed that with the changes to allow for clinical N categories in the pathologic N category, several edits were made more “lenient”. The edit “TNM Path cN0 2016 (CoC)” seems like the edit that would counteract that by checking for mis-use of clinical N in the pN category by passing only the exceptions of in situ, GIST, bone, soft tissue, skin melanoma (T1A only), and corpus uteri.

    But this edit is not listed in any of the edit sets. Is there a reason it was left out? Related to this, I have attached a filtered 16E edit set spreadsheet of those edits that have “COC” in the name of the edit but not included in the COC edit sets. Some of them, such as “Vital Status, Cause of Death (COC)” has an administrative note indicating that CoC no longer supports the edit, but others do not have a similar note.

    Back to the “TNM Path cN0 2016 (CoC)” edit, when I tested the edit in EditWriter4, it passed when it shouldn’t for cutaneous melanoma where pT is NOT pT1A (screenshot attached). In EditWriter 5 it also passed for the same scenario (screenshot attached).

    Thank you for your time!

    Attachments:
    You must be logged in to view attached files.
    #6293
    AnonymousRuth Li
    Spectator

    Responses from NAACCR:

    To the question “this edit is not listed in any of the edit sets. Is there a reason it was left out?”:

    That was an oversight. We skipped the process of polling the standard setters to see if they wanted the edit in their edit set.

    CoC, NPCR, and SEER are all on the Edits WG and they approved the edit. NPCR modified their .dll to accommodate these changes as well.

    To the question ““TNM Path cN0 2016 (CoC)” edit, when I tested… it passed when it shouldn’t for cutaneous melanoma where pT is NOT pT1A”:

    It does look like we have a problem with the logic. It is letting any pT value pass with a cN0. We will look into and should have a fix for v18. If you like we can send you the logic to correct the edit on your end. [Update] Error can be corrected by removing 31 from the following logic statement in the edit:

    if (INLIST(#S”TNM Path N”, “0”, “cxbb”, 2,3))
    if (INLIST(#S”TNM Path T”, “A”, “pxbb”, 2,3) or
    INLIST(#S”TNM Path T”, “IS”, “pxxb”, 2,3) or
    INLIST(#S”TNM Path T”, “ISU, ISD”, “pxxx”, 2,3) or
    INLIST(Sitegrp, “16A,16B,027,028,31,36A”))
    return PASS;

Viewing 2 posts - 1 through 2 (of 2 total)
  • The forum ‘Vendor and Central Registry Metafile Administrators’ is closed to new topics and replies.

Copyright © 2018 NAACCR, Inc. All Rights Reserved | naaccr-swoosh-only See NAACCR Partners and Sponsors