* indicates required field
The NAACCR Standards Implementation Timeline provides deadlines to facilitate successful implementation of revisions to NAACCR Standards for Cancer Registries, Data Standards and Data Dictionary. Revisions to the standards include, but are not limited to, changes to existing data items and proposing new data items for implementation.
| Activity | Deadline is Year Prior to Implementation Unless Stated Otherwise |
|---|---|
| Change request for new data items requiring field testing due to the Mid-Level Tactical Group (MLTG). Requests for new data items must be sponsored by a standard setting organization. |
July 1 (18 Months Prior to Implementation) |
| Change request for data items due to MLTG.* |
October 1 (15 Months Prior to Implementation) |
| Other planned changes (e.g., Staging, ICD-O3.2, Solid Tumor Rules, etc.) due to MLTG. |
October 1 (15 Months Prior to Implementation) |
| Field testing initiated. |
October 1 (15 Months Prior to Implementation) |
| MLTG informs the High-Level Strategic Group (HLSG) of all proposed changes. |
December 31 (13 Months Prior to Implementation) |
| Conversions reported to MLTG. | January 1 |
| Field test results reported to MLTG. | February 1 |
| MLTG approval and recommendation submitted to HLSG. | March 1 |
| HLSG reviews and votes on proposed changes. | March 15 |
| MLTG transmits approved changes to the Uniform Data Standards Work Group (UDS WG). | April 1 |
| NAACCR sends required status table and reportability table to standard setters for review. | April 15 |
| Standard setters submit updates to the required status table and reportability table to NAACCR. | April 30 |
| UDS WG review and approval of the Data Standards and Data Dictionary. | June 1 |
| NAACCR Data Standards and Data Dictionary released. | July 1 |
*Changes to existing data items that result from experience in collecting the data, questions received from registrars or reliability studies generally will not require field testing. However, changes to codes made for other reasons may require field testing to ensure that the new codes and coding instructions can be accurately applied in registry settings. Change requests made in October that the MLTG determine need to be field tested may postpone the implementation year.
Print the Implementation Timeline