TNM 1.7

The TNM version was updated from 1.6 to 1.7. #47

• Colon and Rectum, Combined T table: When one of Clinical T or Path T is missing, the Combined T table for Colon and Rectum was not handling T4. T4 has been added.
• General: if Clin and Path T, N, M and Stage Group are all set to 88, then the Derived Combined T, N, M and Stage Group will be set to 88. This happened without error for most schemas, but Prostate was incorrectly returning an error messages.

BUG FIX: An internal context value was being returned on staging calls. #43

Bugfix release

The sex discriminator was not included in the EodSchemaLookup entity. It is required for certain schemas. A unit test was also added to verify that all discriminators are now included. #40

EOD

Added support for EOD 1.0 (see #39)

Extent of Disease (EOD) is a set of three data items that describe how far a cancer has spread at the time of diagnosis. EOD 2018 is effective for cases diagnosed in 2018 and later.

In each EOD schema, valid values, definitions, and registrar notes are provided for

• EOD Primary Tumor
• EOD Lymph Nodes
• EOD Mets
• Summary Stage 2018
• Site-Specific Data Items (SSDIs), including grade, pertinent to the schema

For cancer cases diagnosed January 1, 2018 and later, the NCI SEER program will collect Extent of Disease (EOD) revised for 2018 and Summary Stage 2018. The schemas have been developed to be compatible with the AJCC 8th Edition chapter definitions.

All of the standard setting organizations will collect the predictive and prognostic factors through Site Specific Data Items (SSDIs). Unlike the SSFs, these data items have formats and code structures specific to the data item.

Numeric range bugfix

The support for numeric ranges in the prior release had a bug in how it built the ranges. It was corrected in #37.

Support numeric range comparison

Prior to this change, the ranges supported by the algorithms has the requirement that each side was the same length. That is because we were using String comparisons. With upcoming algorithms there is a requirement to support numeric ranges. For example,

"0.1-99999.9"

The solution is that for numeric ranges we will compare as float values (even if integer):

• If the low and high values ranges are different and are both "numeric", then the value will be compared after converting to a Float (which will work for the Integer type fields as well).
• Otherwise it will be compared as a String but the strings must be the same length otherwise consider different

Note that as part of this change StagingStringRange was renamed to StagingRange to be more accurate.

For details see #36

TNM 1.6

TNM 1.6 was added to the library, and TNM 1.5 was removed.

TNM changes include:

• There was a bug in the calculation of Combined N for the Colon schema. This manifested only in the C++ library and resulted in errors being returned when the calculation of Combined N was attempted. It has been corrected.
• The Year of Diagnosis validation table was limited to 2016 and 2017.
• Messages were added to returned errors to aid in the identification of the conflict.
• SEER Primary Tumor, SEER Regional Nodes, SEER Mets and Summary Stage 2017 were removed (they were never defined for 2016-2017). While the fields and template calculation steps were included in the API, they were suppressed in production. These data items and calculation steps have been removed to streamline the API. There should be no impact on the validation tables or calculations being performed. The input tags seer_primary_tumor, seer_nodes and seer_mets are no longer valid and should not be passed into the algorithm.

Change to schema selection

This change was handled in #31.

This is the current way schema selection is handled:

• match on all selection tables using ONLY site/hist; completely ignores any other INPUT columns
  • if there is a single match, return it
  • else loop over all the matched tables
    • match table using ALL input columns.

The upcoming EOD algorithm will support multiple discriminators. I am simplifying the process to look like this:

• match on all selection tables using only the keys that were supplied in the lookup.

This change will allow lookups returning multiple results when only some of the discriminators are supplied.

This should have no affect on CS or TNM algorithms.

Dependency updates

Minor release to update various dependencies.

TNM 1.5

This release updates TNM to 1.5. The are as follows:

TNM v1.5 changes:

All schemas where Tis is valid: For Combined N, when neoadjuvant treatment was given (Surgery sequence = 2 or 4) and no nodes were examined (Regional LN Positive = 98), values other than blank (or pX) for Path N resulted in the error message “RN Pos = 98, Path N should be blank”. When Path T = pIS, edits require Path N to be c0. The Combined N logic has been changed to accept Path N = c0 for schemas where Tis is valid.

Support external algorithms and versions

This release adds the ability to use external algorithms and versions. This is accomplished using the ExternalStagingFileDataProvider. This change did not affect the internal algorithms (CS and TNM) and they are still accessed the same way.