Version 02.03


 About this Release

Timeline for Implementation

CSv2 version 02.03.02 must be used to code all cases diagnosed on or after January 1, 2011. Once version 02.03.02 is implemented in a registry, it should be used to code all newly abstracted cases diagnosed from 2004 forward. (2004 was the first year for which Collaborative Stage was collected.) Therefore, the item CS Version Input Original [NAACCR item number 2935] must be 020302 or greater for cases diagnosed in 2011 or abstracted using version 02.03.02. Once version 02.03.02 is implemented in a registry, and existing CS data have been converted according to specifications provided, all cases with CS data coded in prior versions should have all output stage fields re-derived using the algorithm of the new version 02.03.02. Therefore, all cases with CS data will be expected to have CS Version Derived [NAACCR item number 2936] of 020302 after implementation and conversion.



Implementing Version 02.03.02

If you have not yet implemented CS version 02.00.01 (released in January 2010), 02.01.00 (released in February 2010), or 02.02.00 (released in April 2010), you must do so before implementing this new release. All conversion specifications and implementation instructions published for the initial version 2 releases must be followed prior to conversion to version 02.03.02.

CDC has provided Northcon12 and a DLL that will perform the conversions and derivations from CS version 02.0x to CS version 02.03. See the section Program to Convert from Collaborative Stage Version 02.02 to Version 02.03 on the Conversion tab.



Contents of Release

Collaborative Stage Data Collection System version 02.03.02 includes updates to the schemas resulting from the table proofreading and validation project. The last two digits of the version number are 02 because numbers 00 and 01 have been designated to mark cases undergoing conversion to version 02.03.02. Instructions for applying the version numbers 020300 and 020301 are provided in the conversion documentation portion of the release materials.

This release contains the following changes:

Myeloma Plasma Cell Disorder:

A new schema for Multiple Myeloma and Plasma Cell Disorders has been added to the CS schemas. These cases were formerly part of the HemeRetic schema. 

Updates to Schemas:
The CSv2 schemas have undergone an extensive proofreading and validation process. This has resulted in a number of changes throughout the system. These changes have provided a more consistent and standardized methodology of presenting the schema tables. The scope of work for this validation process included:
  • Validation of the original tables approved by the CSv2 Mapping Team to the AJCC 7th Edition
  • Standardization of the tables utilizing general templates for consistency in how the information is presented
  • Correction of grammar and style utilized in the table headers and footnotes
  • Modifications based on questions and issues submitted by registrars and trainers related to prior releases of CSv2
Site-Specific Factors:
Site-specific factors have been added or modified for the following schemas:
  • Bile Duct Intrahepatic
  • Kaposi Sarcoma
  • Testis
Schema Discriminator (SSF 25):

When a schema discriminator is required to identify the proper schema, the DLL will require a valid SSF25 value. For those schemas that have a defined schema discriminator (SSF 25), any blanks which were allowed in CSv0202 have been changed to 981 or 982. SSF 25 describes when it is needed to arrive at the correct schema. For schemas where SSF 25 is defined, if site and histology can already determine the correct schema, the DLL ignores what is in SSF 25 and selects the correct schema. The DLL will only return an error message if the code is an invalid value for SSF 25. Any edits based on invalid codes will also return an error if blanks (or other invalid codes) are in SSF 25. Other edits may be written to prevent valid values other than 981 and 982 from being used when the schema can be determined based on site/histology.

Schema Discriminator (SSF 25) and EDITS:

If site and histology define the schema, the DLL does not check the value of SSF 25 for consistency, such as checking SSF 25 versus the site code. Only if the SSF 25 code is invalid will the DLL report it as an error for SSF 25. There will be an edit provided within EDITS to check for the consistency of SSF 25 with site and histology.


The contents of the zip file include the following in separate folders:
  • Documentation (API Documentation)
  • CSAPI (DLL, LIB, and H files – CSv2 Staging Library)
    • cstage.dll -- For the build/version number, either right-click on the file in Windows Explorer and check the version properties tab or call the API function CStage_get_version()
    • Include files: csapi.h and collab.h
    • Cstage.lib
  • VB CSAPI (Wrapper DLLs used for VB.Net)
  • VB Source (VB source code)
  • Source Code (API Source Code)
  • (HTML tables formatted for the web)
  • (XML tables used in the build)
  • CStageSamples (API sample programs)
    • CSamples (C & C++ sample programs)
    • CSharpSamples (C# sample programs)
    • JavaSamples (Java sample programs)
    • VBSample (Visual Basic .NET programs)
  • (Test-o-Matic standalone interface for the API)
  • Version Change Log



The conversion specifications, document with release notes and rules-based conversions, and spreadsheets with schema/code-specific instructions, comprise the guide for release 02.03.02. No other implementation guides are provided for this release.

Changes noted in the May 12, 2011 specifications: Clarifications have been added to emphasize that the schema names utilized in the document and associated spreadsheet are based on definitions and schema names for CSv02.03. Also, the specifications which refer to the fifth spreadsheet tab (Obsolete Reviewed) were enhanced.

Program to Convert from Collaborative Stage Version 02.02 to 02.03

CDC provides a conversion program and function library to convert data from NAACCR 12.0 to NAACCR 12.1. The conversion of Collaborative Stage (CS) data field-by-field from version 0202xx to 0203xx is embedded in the program. The program, Northcon121.exe, uses a new Windows Dynamic Link Library function library (DLL), nconv121.dll, to do its work., Instructions for using the DLL are included in the setup package. Download from the CDC-NPCR Web page,


 Additional Support Files

CS Defaults version 02.03.02 Dated 2011-02-18 
An Excel spreadsheet which provides the default values for the CSv0203 data fields for Death Certificate Only (DCO) cases originally coded under CSv020302. The spreadsheet is organized by schema and is for cases which have a behavior code of 3. Instructions are included. The previous version was for v0202 and not v02.03.

CSv2 Valid Invalid & Obsolete Codes Tables 2010-12-06 
Valid, Invalid, and Obsolete Codes Tables: Excel Spreadsheets are provided which show schema-specific valid and invalid values for each field for CS version 02.03.02. An Excel spreadsheet is also included which contains the obsolete codes for version 02.03.02. Please note that the obsolete spreadsheet has a table for each obsolete code type and one of all obsolete codes combined. These three spreadsheets are not mutually exclusive since the obsolete codes are also contained in the valid code list.
NAACCR v.12 Valid Invalid v.02.03.02 2010-12-06
Test Cases for the Algorithm: Vendors have expressed an interest in obtaining test records which have a known behavior when the CS algorithm is run on them. Two sets of random test cases, one for valid CS codes ( and one set with one and only one CS invalid code ( in each record were generated from the XML files. These input files (.in.) are in NAACCR v12 format (LRECL = 3339) and only contain the CS input fields and other fields necessary for the DLL to successfully run. On the input file, the record is un-staged, i.e., all derived CS fields are blank. These files can be used as input to the corresponding version of the CS algorithm (v020302). The output files (.out.) contain the staging results generated by the CSv2 algorithm. When staging the Valid “in” file, no errors should be generated by the algorithm. When staging the Invalid “in” file, one specific error message should be generated per data record. Please note that each record of the invalid “out” file contains the first 200 characters of the error message generated by the CSv2 algorithm. The error message has been written to column 1236 (Reserved 05).


Testing the CS Algorithm
Tools to ensure that your software program calculates stage correctly.
Test-O-Matic – is an interactive Windows program that is useful for exploring Collaborative Staging tables and deriving stage. For more detailed information, please refer to CSv1 Test-o-Matic description.