NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

June 7, 2021:  R8 Final CTEP Standard Forms

These CTEP standard forms have been created as part of the NCI CTEP CDISC Implementation.  This is a collaborative effort between NCI CBIIT and NCI CTEP; the NCI CDISC aligned content has been leveraged as appropriate in consideration of NCI CTEP CDISC implementation.  The CTEP standard forms include:


  1. CDSIC aligned question text, prompt, CDISC published CT, CDASH variables and the corresponding caDSR Form PIDs and CDE PIDs.
  2. The variables within the CTEP standard forms have a two letter domain prefix specified where appropriate as per our NCI CTEP CDISC implementation decision.
  3. The NCTN/ETCTN curation style guide requirements have been applied to the content in the CTEP standard forms. 

We are actively working on R6 and R7.  An update will be provided as available.  If you have any questions, please send an email to ncicdiscsupport@nih.gov.

March 29th, 2021:  CTEP Standard Form Release for R5

R5 Final CTEP Standard Forms

  1. CTEP CDISC Diagnosis Intervention v1.0
  2. CTEP CDISC Equipment v1.0
  3. CTEP CDISC Imaging Administration v1.0
  4. CTEP CDISC Consent Metastasis v1.0
  5. CTEP CDISC PET-Imaging Agent v1.0
  6. CTEP CDISC PET-Patient-Prep v1.0
  7. CTEP CDISC Progression v1.0
  8. CTEP CDISC Protocol Deviations v1.0

These CTEP standard forms have been created as part of the NCI CTEP CDISC Implementation.  This is a collaborative effort between NCI CBIIT and NCI CTEP; the NCI CDISC aligned content has been leveraged as appropriate in consideration of NCI CTEP CDISC implementation.  The CTEP standard forms include:


  1. CDSIC aligned question text, prompt, CDISC published CT, CDASH variables and the corresponding caDSR Form PIDs and CDE PIDs.
  2. The variables within the CTEP standard forms have a two letter domain prefix specified where appropriate as per our NCI CTEP CDISC implementation decision.
  3. The NCTN/ETCTN curation style guide requirements have been applied to the content in the CTEP standard forms. 


We are actively working on R6.  An update will be provided as available.  If you have any questions, please send an email to ncicdiscsupport@nih.gov.


A thank you to CBIIT for their collaboration and support efforts on this project.  A thank you to all of our LPOs for all your engagement to make this implementation a success.

January 27th, 2021:  CTEP Standard Form Release for R4

R4 Final CTEP Standard Forms

  1. CTEP CDISC CTEP CDISC AE SAE CTCAEv4.0 v1.0
  2. CTEP CDISC AE SAE CTCAEv5.0 v1.0
  3. CTEP CDISC Consent v1.0
  4. CTEP CDISC Consent Withdrawal v1.0
  5. CTEP CDISC Consent Withdrawal QOL Study v1.0
  6. CTEP CDISC Consent Withdrawal Specimen v1.0
  7. CTEP CDISC Diagnosis Administrative v1.0
  8. CTEP CDISC Diagnosis Gross Pathology v1.0
  9. CTEP CDISC Enrollment v1.0
  10. CTEP CDISC Lab Test Results v1.0
  11. CTEP CDISC Prior Therapies v1.0
  12. CTEP CDISC Registration v1.0
  13. CTEP CDISC Staging AJCC Edition 8 Lung v1.0


These CTEP standard forms have been created as part of the NCI CTEP CDISC Implementation.  This is a collaborative effort between NCI CBIIT and NCI CTEP; the NCI CDISC aligned content has been leveraged as appropriate in consideration of NCI CTEP CDISC implementation.  The CTEP standard forms include:


  1. CDSIC aligned question text, prompt, CDISC published CT, CDASH variables and the corresponding caDSR Form PIDs and CDE PIDs.
  2. The variables within the CTEP standard forms have a two letter domain prefix specified where appropriate as per our NCI CTEP CDISC implementation decision.
  3. The NCTN/ETCTN curation style guide requirements have been applied to the content in the CTEP standard forms. 


We are actively working on R5.  An update will be provided as available.  If you have any questions, please send an email to ncicdiscsupport@nih.gov.

November 2nd, 2020

Based on feedback from the LPOs and the CDISC project team, we have determined that the TRIAD forms in R2 are administrative.  We do not have an active use case to align any of the content.  Using the same rule we have for all forms, if there is a use case identified we will revisit the roadmap and align the needed content. 

...