TNM v1.0

TNM v1.0 is now available.

The TNM staging algorithm contains the data items and descriptions necessary to collect T, N and M stage components, as well as other data items required to calculate Clinical and Pathologic Stage Groups. In addition, this algorithm calculates a combined stage group. It also contains the data item definitions for the associated Predictive and Prognostic Factors on a schema specific basis. Staging information is collected for site and histology combinations that are not defined in TNM in order to support SEER Summary Stage calculations (these calculations will not be implemented for diagnosis year 2016).

The initial release includes Union for International Cancer Control (UICC) TNM Classification of Malignant Tumor 7th edition.

Bugfix release

This release fixes a parsing error for table fields that end in a "-". When parsing cells, values are considered ranges if the length of the data one the left and right of the dash are the same. However the code was not handling values with a dash as the last character. This did not affect the CS algorithm but did affect the upcoming TNM algorithm

Bugfix release

This release fixes a minor issue with table parsing. Cell values with a trailing empty value were not being processing correctly. Values that looked like ,1,2,3 were parsing properly in 4 distinct values, while 1,2,3, was incorrectly parsing into only 3 values. The parsing was fixed to properly handle both cases.

Java 7

This is the first release which requires Java 7.

• There was an exception being thrown in getInvolvedTables when a table had no rows. There was no reason for this and now it is handled properly.

Change how missing context keys are matched

The behavior of missing context keys and how they match tables INPUTs was changed. For a complete description, see #12.

Bugfix for schema lookup staging outputs

While the stage API correctly dealt with the outputs defined on the schema level, the lookupSchema were not.

There were 2 issues corrected in this release:

1. Values calculated in staging but not in the output list were being listed as outputs in lookupSchema. They do not get returned in stage.
2. Outputs that have defaults values (like schema_number in CS) were not being included in the list of outputs returned by lookupSchema.

Minor bugfix

There was an problem with the calculation of inputs to individual table paths when the library was run under Java 8. There were additional inputs listed that should have been ignored. The releases fixes the issues and updates the CS 02.05.50 schema files to incorporate the fix.

Validation change

This is a minor release which changes how validation is done for staging calls. This change affects 2 cases when an input definition has a validation table defined:

• an input is not supplied and that input has no default defined
• an input is supplied as blank

In prior releases, blank inputs were validated against the defined table. In this release, the blank inputs are not validated. Some inputs were not being used for staging so it was perfectly valid to not supply them and the errors were extra noise. If the input is used in the staging calculations there could possible be error produced later in the staging process which is the correct behavior.

Input calculation fix

This is a minor release that fixed a rare case where calculated inputs on a table path were incorrect.

CS input and output descriptions

Input and output descriptions were added to the CS algorithm.