|
Release history of Collaborative Stage version 2
02.00.00 Reserved for cases processed by CSv2 conversion utility
02.00.01 Initial release – January 2010
02.01.00 February 2010
02.02.00 April 2010 (current)
The third production version of CSv2 was released on 04/29/2010 (Build/Version Number: 02.02.00). This is the version that should be used for current software installations to calculate Collaborative Stage V2. The documentation and sample programs have been revised to account for some minor updates to the API and schema mapping. A change log is also included in the download to account for changes from build 02.01.00 to 02.02.00.
Please Note:
This release of CSv2 is a production version. However, schemas validation reviews and field use feedback will require an additional release in fall 2010. Registries and vendors are encouraged to implement the current release as soon as practical. E-mail notifications will be provided when a new production version is released. These releases will be posted on this Web page.
The first production version of CSv2 was released on 01/13/2010 (Build/Version Number: 02.00.01) in conjunction with the second Vendor CSv2 NAACCR Town hall meeting. This presentation was specifically given to help vendors implement the production version of CSv2 in their software products. The presentations given on 11/04/2009 and 01/13/2010 should be used in conjunction with the software to develop a full understanding of CSv2.
The MS PowerPoint slides (converted to PDFs) should be reviewed before downloading the ZIP file with the software. Links to the Town Hall MS PowerPoint slides and the CSv2 production version of the software are included below:
CSv2_Vendor Meeting_2009_11_04.pdf - Converted to a PDF from the MS PowerPoint slides
CSv2_Vendor Meeting_2010_01_13.pdf - Converted to a PDF from the MS PowerPoint slides
Collaborative Stage Version 02.02.00 Release Announcement with Implementation Instructions
Contents of Release
The new version includes corrections to the software and corresponding API documentation. Two new components have been added: VB source code and HTML documentation for schema selection. The function cstage_get_version was added to the EDITS interface. A blank in the field Lymph-Vascular Invasion will now be considered valid when the year of diagnosis is 2009 or earlier and CS Version Input Original is less than 020000. See the “Release Notes” and the file “Changes for CSv2.2.doc” for more details.
The release also contains changes to the following schemas.
Breast: CS Extension code 715 was made OBSOLETE DATA RETAINED. The meaning of code 715 overlapped with the meaning of codes 600 and 725, and the code had been left in the table in error. No review of cases is warranted.
Testis: A stage table was corrected. Also, the calculation of the S value was adjusted to use the data in the obsolete Site-Specific Factors 1-3 for cases diagnosed in 2009 and earlier. The calculation of S value was also adjusted to accommodate cases diagnosed in 2010 that were originally coded in CSv1. No case review is needed, but the stage outputs must be re-derived to correct the data.
LymphomaOcularAdnexa: The documentation of the algorithm was synchronized with the behavior of the staging algorithm. No case review is needed.
Implementing Version 02.02.00
If you have not yet implemented CS version 02.00.01 (released in 01/10), or 02.01.00 (released in 2/10), you can implement this new release instead. Note that all conversion specifications and implementation instructions published for the initial version 2 release must still be followed.
If you have implemented CS version 2 and converted your old data, but have not yet collected any new cases under CSv2, you can just replace the DLL with the new one and re-derive all stage data with the new version, setting the CS Version Derived to ‘020200’.
If you have implemented CSv2, converted old data, and collected any new data under CSv2, you may also need to review some cases for which the schema selection algorithm may have returned an incorrect result. This new release includes a change in the handling of blanks in schema discriminator, Site-Specific Factor 25 (SSF25). The schema selection algorithm will no longer resolve to a schema when a discriminator is needed but is blank. Any cases matching the following sites and histologies and having a blank string in SSF25 should be reviewed. The blank string should be replaced with an appropriate non-blank code and all of the CS fields should be reviewed and recoded if necessary.
| Schemas Involved |
Primary Site Codes |
Histology Codes |
Nasopharyns/PharyngealTonsil |
C111 |
8000-8713, 8800-9136, 9141-9582, 9700-9701 |
EsophagusGEJunction/Stomach |
C161, C162 |
8000-8152, 8154-8231, 8243-8245, 8247-8248, 8250-8934, 8940-9136, 9141-9582, 9700-9701 |
Peritoneum/PeritoneumFemaleGen |
C481-C482, C488 |
8000-8576, 8590-8671, 8930-8934, 8940-9110 |
CSv2_Production_Release_2010_04_29.zip 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.zip (HTML tables formatted for the web)
- XML.zip (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)
- Testomatic.zip (Test-o-Matic standalone interface for the API)
- Version Change Log
Conversion Specifications
Resources
- Schema ID Names/Sites/Histology Groups (190 XLS) - updated July 8, 2010 - This listing identifies the AJCC 6th and 7th Edition chapters and the corresponding CSv2 schema. It also includes ICD-O-3 primary site codes and histology codes. The last column indicates the primary site and histology codes that generate stage.
Program to Convert from Collaborative Stage Version 1 to Version 2
CDC has released Northcon12, a freestanding Windows-based utility program that converts a file of cancer registry records in NAACCR11 record layout format to the NAACCR 12 record layout. Conversion of Collaborative Stage (CS) data from version 1 to version 2 is embedded in this program. The CS conversion is based on the published specifications and has been extensively tested. When the conversion is run, the user has the option to derive the Collaborative Stage version 2 stage outputs on appropriate records. For more information or to download the program, see the CDC-NPCR Web page at:
http://www.cdc.gov/cancer/npcr/tools/registryplus/up_download.htm
Instructions for accessing the program’s underlying dynamic link libraries (DLLs) are also available on this Web page. These can be used by anyone who wishes to perform the conversions using another program.
Support Files and Test Files
CSv2_Valid_Invalid_&_Obsolete_Codes_Tables_2010_04_29.zip (130K ZIP) 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.02.00. An Excel spreadsheet is also included which contains the obsolete codes for version 02.02.00. 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.
NAACCRv12_Valid_Invalid_v020100_2010_04_29.zip (2095K ZIP) 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 (valid.NAACCRv12.in.v020200.txt) and one set with one and only one CS invalid code (invalid.NAACCRv12.in.v020200.txt) 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 (v020200). 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).
For Questions:
As the CSv2 algorithm is implemented and employed with real case scenarios, questions regarding the CS site-specific schemas should be sent to csv2@facs.org.
For questions and comments on CSv2 production version software, please e-mail Joseph Rogers at JRogers@cdc.gov.
Software Archives
Software Products for Collaborative Staging
Version 1 (CSv1)
Revised July 9, 2010
Collaborative Staging Home Page
|