diff --git a/web/src/main/javascript/docs/faq.md b/web/src/main/javascript/docs/faq.md new file mode 100644 index 0000000..4ec49b6 --- /dev/null +++ b/web/src/main/javascript/docs/faq.md @@ -0,0 +1,39 @@ +# Frequently Asked Questions (FAQ) + +## 1. Why do you distinguish between “detailed tumor types” and “main tumor types,” and why are the main tumor types not entered into the OncoTree with separate nodes? + +OncoTree distinguishes between **detailed tumor types** and **main tumor types** to maintain a structured hierarchy of cancer classifications. The **detailed tumor types** provide specific subcategories within each **main tumor type**, allowing for more precise annotation and analysis. The **main tumor types** act as broader categories that group together related detailed tumor types. + +The reason main tumor types are not assigned separate nodes in OncoTree is that the classification is designed to focus on specific, well-defined tumor subtypes rather than broad categories. This ensures that OncoTree remains granular and clinically relevant for precision medicine applications. + +## 2. Do you have codes for the main tumor types, just like for the detailed tumor types? Or are you planning on assigning them in the future? + +Currently, OncoTree provides unique codes primarily for **detailed tumor types** to facilitate precise classification. While main tumor types do not have distinct codes assigned in the same way, efforts to develop mappings or codes for these broad categories may be considered in the future to improve interoperability with other classification systems. + +## 3. Why do you include so many main tumor types with the extension “, NOS”? These types are not included in the drop-down menu for the tumor types on the OncoKB website. Would it make a difference to the results when using these NOS terms as input to the web API? + +The extension **"NOS" (Not Otherwise Specified)** is used to indicate tumor types that do not have a more specific classification. These are included to ensure compatibility with clinical terminology and pathology reports, which often use NOS when further molecular or histopathological details are unavailable. + +Since OncoKB is optimized for precision oncology, the **NOS terms** may not appear in the drop-down menu because they are considered less specific. However, using NOS terms as input to the **OncoKB web API** could still yield results, depending on whether the system can map them to a more specific classification. + +## 4. Do you have a mapping of the main tumor types onto NCI or UMLS as for the detailed tumor types? + +Yes, OncoTree provides **detailed tumor type mappings** to external ontologies such as: + +- **NCI Thesaurus (NCIt)** +- **Unified Medical Language System (UMLS)** + +However, mappings for **main tumor types** may not be explicitly provided. Users may need to rely on hierarchical relationships within OncoTree or external classification resources to infer these mappings. + +## 5. Do you have a mapping for the tumor types onto the common SNOMED or ICD-10 codes? Or do you have a suggestion on how to perform this mapping? + +OncoTree does not currently provide **direct mappings to SNOMED CT or ICD-10**. However, mappings can be established using: + +- **NCI Thesaurus (NCIt)**, which provides cross-references to SNOMED and ICD-10. +- **UMLS Metathesaurus**, which links medical terms across multiple ontologies, including SNOMED and ICD-10. + +To perform this mapping, you can: + +1. Use **NCIt codes** from OncoTree and find their corresponding entries in SNOMED or ICD-10. +2. Use the **UMLS Metathesaurus API** to look up terms and find equivalent SNOMED/ICD-10 codes. +3. Leverage tools like the **National Library of Medicine (NLM) mappings** to find equivalent ICD-10 codes. diff --git a/web/src/main/javascript/public/404.html b/web/src/main/javascript/public/404.html index 67b4e39..74b836b 100644 --- a/web/src/main/javascript/public/404.html +++ b/web/src/main/javascript/public/404.html @@ -15,7 +15,7 @@
- + \ No newline at end of file diff --git a/web/src/main/javascript/public/about.html b/web/src/main/javascript/public/about.html index bf44f67..f5c5607 100644 --- a/web/src/main/javascript/public/about.html +++ b/web/src/main/javascript/public/about.html @@ -18,7 +18,7 @@

Appearance

About ​

About OncoTree ​

OncoTree is a comprehensive, community-led cancer classification system that adapts to the evolving demands of precision oncology. Designed to classify cancers by both histological and molecular traits, it provides a structured framework to complement the clinical decision-making processes. The platform, which is open-source and publicly accessible, is governed by a diverse committee of oncologists, pathologists, and scientists. This multidisciplinary oversight ensures OncoTree remains relevant, incorporating new cancer types and research advancements in real time to support clinical decision-making and research applications.

Curation Process Overview ​

Overview of the curation process in OncoTree

- + \ No newline at end of file diff --git a/web/src/main/javascript/public/assets/faq.md.DLit2BmC.js b/web/src/main/javascript/public/assets/faq.md.DLit2BmC.js new file mode 100644 index 0000000..92bff1c --- /dev/null +++ b/web/src/main/javascript/public/assets/faq.md.DLit2BmC.js @@ -0,0 +1 @@ +import{_ as e,c as t,o,a3 as n}from"./chunks/framework.CyEiTwkJ.js";const y=JSON.parse('{"title":"Frequently Asked Questions (FAQ)","description":"","frontmatter":{},"headers":[],"relativePath":"faq.md","filePath":"faq.md"}'),s={name:"faq.md"},i=n('

Frequently Asked Questions (FAQ) ​

1. Why do you distinguish between “detailed tumor types” and “main tumor types,” and why are the main tumor types not entered into the OncoTree with separate nodes? ​

OncoTree distinguishes between detailed tumor types and main tumor types to maintain a structured hierarchy of cancer classifications. The detailed tumor types provide specific subcategories within each main tumor type, allowing for more precise annotation and analysis. The main tumor types act as broader categories that group together related detailed tumor types.

The reason main tumor types are not assigned separate nodes in OncoTree is that the classification is designed to focus on specific, well-defined tumor subtypes rather than broad categories. This ensures that OncoTree remains granular and clinically relevant for precision medicine applications.

2. Do you have codes for the main tumor types, just like for the detailed tumor types? Or are you planning on assigning them in the future? ​

Currently, OncoTree provides unique codes primarily for detailed tumor types to facilitate precise classification. While main tumor types do not have distinct codes assigned in the same way, efforts to develop mappings or codes for these broad categories may be considered in the future to improve interoperability with other classification systems.

3. Why do you include so many main tumor types with the extension “, NOS”? These types are not included in the drop-down menu for the tumor types on the OncoKB website. Would it make a difference to the results when using these NOS terms as input to the web API? ​

The extension "NOS" (Not Otherwise Specified) is used to indicate tumor types that do not have a more specific classification. These are included to ensure compatibility with clinical terminology and pathology reports, which often use NOS when further molecular or histopathological details are unavailable.

Since OncoKB is optimized for precision oncology, the NOS terms may not appear in the drop-down menu because they are considered less specific. However, using NOS terms as input to the OncoKB web API could still yield results, depending on whether the system can map them to a more specific classification.

4. Do you have a mapping of the main tumor types onto NCI or UMLS as for the detailed tumor types? ​

Yes, OncoTree provides detailed tumor type mappings to external ontologies such as:

However, mappings for main tumor types may not be explicitly provided. Users may need to rely on hierarchical relationships within OncoTree or external classification resources to infer these mappings.

5. Do you have a mapping for the tumor types onto the common SNOMED or ICD-10 codes? Or do you have a suggestion on how to perform this mapping? ​

OncoTree does not currently provide direct mappings to SNOMED CT or ICD-10. However, mappings can be established using:

To perform this mapping, you can:

  1. Use NCIt codes from OncoTree and find their corresponding entries in SNOMED or ICD-10.
  2. Use the UMLS Metathesaurus API to look up terms and find equivalent SNOMED/ICD-10 codes.
  3. Leverage tools like the National Library of Medicine (NLM) mappings to find equivalent ICD-10 codes.
',18),a=[i];function r(h,d,u,p,m,l){return o(),t("div",null,a)}const g=e(s,[["render",r]]);export{y as __pageData,g as default}; diff --git a/web/src/main/javascript/public/assets/faq.md.DLit2BmC.lean.js b/web/src/main/javascript/public/assets/faq.md.DLit2BmC.lean.js new file mode 100644 index 0000000..3ea65a2 --- /dev/null +++ b/web/src/main/javascript/public/assets/faq.md.DLit2BmC.lean.js @@ -0,0 +1 @@ +import{_ as e,c as t,o,a3 as n}from"./chunks/framework.CyEiTwkJ.js";const y=JSON.parse('{"title":"Frequently Asked Questions (FAQ)","description":"","frontmatter":{},"headers":[],"relativePath":"faq.md","filePath":"faq.md"}'),s={name:"faq.md"},i=n("",18),a=[i];function r(h,d,u,p,m,l){return o(),t("div",null,a)}const g=e(s,[["render",r]]);export{y as __pageData,g as default}; diff --git a/web/src/main/javascript/public/faq.html b/web/src/main/javascript/public/faq.html new file mode 100644 index 0000000..2eef673 --- /dev/null +++ b/web/src/main/javascript/public/faq.html @@ -0,0 +1,24 @@ + + + + + + Frequently Asked Questions (FAQ) | OncoTree + + + + + + + + + + + + + +

Appearance

Frequently Asked Questions (FAQ) ​

1. Why do you distinguish between “detailed tumor types” and “main tumor types,” and why are the main tumor types not entered into the OncoTree with separate nodes? ​

OncoTree distinguishes between detailed tumor types and main tumor types to maintain a structured hierarchy of cancer classifications. The detailed tumor types provide specific subcategories within each main tumor type, allowing for more precise annotation and analysis. The main tumor types act as broader categories that group together related detailed tumor types.

The reason main tumor types are not assigned separate nodes in OncoTree is that the classification is designed to focus on specific, well-defined tumor subtypes rather than broad categories. This ensures that OncoTree remains granular and clinically relevant for precision medicine applications.

2. Do you have codes for the main tumor types, just like for the detailed tumor types? Or are you planning on assigning them in the future? ​

Currently, OncoTree provides unique codes primarily for detailed tumor types to facilitate precise classification. While main tumor types do not have distinct codes assigned in the same way, efforts to develop mappings or codes for these broad categories may be considered in the future to improve interoperability with other classification systems.

3. Why do you include so many main tumor types with the extension “, NOS”? These types are not included in the drop-down menu for the tumor types on the OncoKB website. Would it make a difference to the results when using these NOS terms as input to the web API? ​

The extension "NOS" (Not Otherwise Specified) is used to indicate tumor types that do not have a more specific classification. These are included to ensure compatibility with clinical terminology and pathology reports, which often use NOS when further molecular or histopathological details are unavailable.

Since OncoKB is optimized for precision oncology, the NOS terms may not appear in the drop-down menu because they are considered less specific. However, using NOS terms as input to the OncoKB web API could still yield results, depending on whether the system can map them to a more specific classification.

4. Do you have a mapping of the main tumor types onto NCI or UMLS as for the detailed tumor types? ​

Yes, OncoTree provides detailed tumor type mappings to external ontologies such as:

  • NCI Thesaurus (NCIt)
  • Unified Medical Language System (UMLS)

However, mappings for main tumor types may not be explicitly provided. Users may need to rely on hierarchical relationships within OncoTree or external classification resources to infer these mappings.

5. Do you have a mapping for the tumor types onto the common SNOMED or ICD-10 codes? Or do you have a suggestion on how to perform this mapping? ​

OncoTree does not currently provide direct mappings to SNOMED CT or ICD-10. However, mappings can be established using:

  • NCI Thesaurus (NCIt), which provides cross-references to SNOMED and ICD-10.
  • UMLS Metathesaurus, which links medical terms across multiple ontologies, including SNOMED and ICD-10.

To perform this mapping, you can:

  1. Use NCIt codes from OncoTree and find their corresponding entries in SNOMED or ICD-10.
  2. Use the UMLS Metathesaurus API to look up terms and find equivalent SNOMED/ICD-10 codes.
  3. Leverage tools like the National Library of Medicine (NLM) mappings to find equivalent ICD-10 codes.
+ + + + \ No newline at end of file diff --git a/web/src/main/javascript/public/hashmap.json b/web/src/main/javascript/public/hashmap.json index 1e03739..d94dec3 100644 --- a/web/src/main/javascript/public/hashmap.json +++ b/web/src/main/javascript/public/hashmap.json @@ -1 +1 @@ -{"about.md":"BceXjb0R","mapping.md":"CdddfsKe","news.md":"ZGge0dYE"} +{"about.md":"BceXjb0R","faq.md":"DLit2BmC","mapping.md":"CdddfsKe","news.md":"ZGge0dYE"} diff --git a/web/src/main/javascript/public/mapping.html b/web/src/main/javascript/public/mapping.html index c39a4f7..2ccbb92 100644 --- a/web/src/main/javascript/public/mapping.html +++ b/web/src/main/javascript/public/mapping.html @@ -19,7 +19,7 @@

Appearance

Contents ​

OncoTree to OncoTree Mapping Tool ​

The OncoTree Mapping tool was developed to facilitate the mapping of OncoTree codes between different OncoTree release versions. Below you can find basic instructions in the "Running the tool" section, and a detailed walkthrough in the "Tutorial" section.

Setting up and downloading the tool ​

As of January 2020, the sun has set on Python 2.X. If you are still using Python 2.X, we encourage you to use Python 3.6 and above, but here is the last version of the code to work with Python 2.X. In the future, only Python 3.X versions of this tool will be supported.

Click here to download the script: oncotree_to_oncotree.py

Running the tool ​

The OncoTree Mapping tool can be run with the following command:

python3 <path/to/scripts/oncotree_to_oncotree.py> --source-file <path/to/source/file> --target-file <path/to/target/file> --source-version <source_oncotree_version> --target-version <target_oncotree_version>

Options

  • -i | --source-file: This is the source clinical file path. It must contain ONCOTREE_CODE in the file header and it must contain OncoTree codes corresponding to the <source_oncotree_version>. Read more about the cBioPortal clinical file format here.
  • -o | --target-file: This is the path to the target clinical file that will be generated. It will contain mapped OncoTree codes from <source_oncotree_version>-to-<target_oncotree_version>.
  • -s | --source-version: This is the source OncoTree version. The OncoTree codes in the source file must correspond to this version.
  • -t | --target-version: This is the target OncoTree version that the script will attempt to map the source file OncoTree codes to.

The list of OncoTree versions available are viewable here or on the dropdown menu of the OncoTree home page.

Note: the source file should not contain embedded line breaks within any single cell in the table, such as those created by using the keyboard combinations Alt-Enter or Command-Option-Enter while editing a cell in Microsoft Excel.

For a detailed walkthrough of running the tool, see the "Tutorial" section below.

Output ​

The OncoTree Mapper Tool will automatically replace the value in the ONCOTREE_CODE column with the mapped code if available. The tool will also add a new column called ONCOTREE_CODE_OPTIONS containing suggestions for OncoTree codes if one or more nodes could not be directly mapped. The ONCOTREE_CODE_OPTIONS column formats its suggestions differently depending on the mapping results. Possible suggestion formats and corresponding examples are shown below.

1. Unambiguous Direct Mappings ​

Unambiguous direct mappings occur when an OncoTree code maps directly to a single code in the target version. In this case, the ONCOTREE_CODE_OPTIONS column will be left blank, and the mapped code will be automatically placed in the ONCOTREE_CODE column. Unambiguous direct mappings are checked for addition of more granular nodes; to see how this may affect the ONCOTREE_CODE_OPTIONS column formatting, please refer to the subsection below "4. More Granular Nodes Introduced".

2. Ambiguous Direct Mappings ​

Ambiguous direct mappings occur when an OncoTree code maps to multiple codes in the target version. The ONCOTREE_CODE_OPTIONS column formats the output as follows:

'Source Code' -> {'Code 1', 'Code 2', 'Code 3', }   e.g. ALL -> {TLL, BLL}

Example: Schema describing the revocation of OncoTree node ALL is mapped to multiple nodes.

In oncotree_2018_05_01, ALL had two children: TALL and BALL. On release oncotree_2018_06_01, the ALL node was discontinued and the TALL node was renamed TLL and the BALL node was renamed BLL.

The ONCOTREE_CODE_OPTIONS column would be shown as follows:

ALL -> {TLL, BLL}

Ambiguous direct mappings are also checked for addition of more granular nodes; to see how this may affect the ONCOTREE_CODE_OPTIONS column formatting, please refer to the subsection below "4. More Granular Nodes Introduced".

3. No Direct Mappings ​

No direct mappings occur when the source OncoTree code is unrelated to any OncoTree code in the target version. One such possibility is mapping a newly introduced OncoTree code backwards in time. In this case, the tool finds the closest set of neighbors (e.g parents and children) which are mappable in the target version. The ONCOTREE_CODE_OPTIONS column returns the set with the keyword Neighbors as follows:

'Source Code' -> Neighbors {'Code 1', 'Code 2', 'Code 3', }   e.g. UPA -> Neighbors {BLADDER}

Example: Schema describing a case where new OncoTree node UPA cannot be directly mapped backwards to a node.

In oncotree_2019_03_01, UPA was added to the OncoTree as a child node of BLADDER. Because UPA did not exist in previous version oncotree_2018_05_01 and did not replace any existing node, the tool uses the surrounding nodes when mapping backwards. In this case, the parent node BLADDER is returned as the closest match.

The ONCOTREE_CODE_OPTIONS column would be shown as follows:

UPA -> Neighbors {BLADDER}

4. More Granular Nodes Introduced ​

In certain cases, the target version can also introduce nodes with more specific descriptions. When this occurs, the tool will add the string more granular choices introduced to the existing text in the ONCOTREE_CODE_OPTIONS column as follows:

'Source Code' -> {'Code 1', }, more granular choices introduced e.g. TALL -> {TLL}, more granular choices introduced

Example: Schema describing a case where OncoTree node TALL is mapped to a node with more granular children

In oncotree_2019_03_01, TALL was a leaf node with no children. In release oncotree_2019_06_01, TLL was introduced as a replacement for TALL with additional children ETPLL and NKCLL.

The ONCOTREE_CODE_OPTIONS column would be shown as follows:

TALL -> {TLL}, more granular choices introduced

5. Invalid Source OncoTree Code ​

An invalid source OncoTree Code means the provided code cannot be found in the source version. In such a case, mapping cannot be attempted and the ONCOTREE_CODE_OPTIONS column displays the following:

'Source Code' -> ???, OncoTree code not in source OncoTree version

Tutorial ​

The following tutorial will guide the user through using the oncotree_to_oncotree.py tool. The tutorial will go through the expected output to highlight specific mapping cases. Additionally, the tutorial will cross-reference the output with the generated mapping summary to demonstrate how it can be used to aid in manual selection of unresolved nodes.

Step 1 ​

Download the sample input file (data_clinical_sample.txt) from here .

Step 2 ​

Download oncotree_to_oncotree.py from here .

Step 3 ​

Run the following command from the command line:

python oncotree_to_oncotree.py -i data_clinical_sample.txt -o data_clinical_sample_remapped.txt -s oncotree_2018_03_01 -t oncotree_2019_03_01

The tool will output two files: data_clinical_sample_remapped.txt and data_clinical_sample_remapped_summary.html. For your reference, you can see the expected output files - here and here

Step 4 ​

Examine data_clinical_sample_remapped.txt; the first five columns of the file should look as follows:

PATIENT_IDSAMPLE_IDAGE_AT_SEQ_REPORTONCOTREE_CODEONCOTREE_CODE_OPTIONS
P1S141ALL -> {BLL,TLL}, more granular choices introduced
P2S260BALL -> {BLL}, more granular choices introduced
P3S3<18TALL -> {TLL}, more granular choices introduced
P4S471PTCL
P5S564PTCL
P6S636CHL -> {CHL}, more granular choices introduced
P7S763SpCC -> ???, OncoTree code not in source OncoTree version
P8S863MCL -> {MCL}, more granular choices introduced
P9S973HGNEE -> ???, OncoTree code not in source OncoTree version
P10S1052ONCOTREE_CODE column blank : use a valid OncoTree code or "NA"
P11S1177NA
P12S1287TNKL -> {MTNN}, more granular choices introduced
P13S1379HIST -> {HDCN}, more granular choices introduced
P14S1453CLLSLL
P15S1569CLLSLL
P16S1665LEUK -> {MNM}, more granular choices introduced
P17S1766MYCF
P18S1866RBL

Step 5 ​

Using values in the ONCOTREE_CODE_OPTIONS as a guide, manually select and place an OncoTree Code in the ONCOTREE_CODE column. For additional information, refer to the summary file data_clinical_sample_remapped_summary.html. Repeat for all rows in the output file. Several examples are shown below.

Sample 1 ​
SAMPLE_IDONCOTREE_CODEONCOTREE_CODE_OPTIONS
S1ALL -> {BLL,TLL}, more granular choices introduced

Source OncoTree code ALL maps directly to codes BLL and TLL. Users should place either BLL or TLL in the ONCOTREE_CODE column. The ONCOTREE_CODE_OPTIONS column also notes that more granular choices were introduced; as such, users can use the summary file for additional guidance.

Searching by source code, the following information can be found in the summary file:

The summary file provides a link to the closest shared parent node LNM; users can choose more granular nodes by referencing the provided tree:

Sample 2 ​
SAMPLE_IDONCOTREE_CODEONCOTREE_CODE_OPTIONS
S2BALL -> {BLL}, more granular choices introduced

Source OncoTree code BALL maps directly to BLL. Users should place BLL in the ONCOTREE_CODE column. However, similar to sample 1, the ONCOTREE_CODE_OPTIONS indicates there are more granular choices available. Users can follow the same steps as above and use the summary file to select a more granular node.

Sample 4 ​
SAMPLE_IDONCOTREE_CODEONCOTREE_CODE_OPTIONS
S4PTCL

No additional resolution is needed; the previous OncoTree code was already automatically mapped to PTCL and placed in the ONCOTREE_CODE column. ONCOTREE_CODE_OPTIONS is empty because no manual selections were necessary.

Sample 9 ​
SAMPLE_IDONCOTREE_CODEONCOTREE_CODE_OPTIONS
S4HGNEE -> ???, OncoTree code not in source OncoTree version

Source OncoTree code HGNEE was not found in the source OncoTree version and therefore could not be mapped. Users can either reassign a new source OncoTree code (and rerun the script) or remove the sample.

Step 6 ​

After filling in the ONCOTREE_CODE column with an OncoTree code for each sample, use an editor (e.g. Microsoft Excel, vim, etc.) to trim off the ONCOTREE_CODE_OPTIONS column. The resulting file will be a new data_clinical_sample.txt file with all codes mapped to the target version. The first four columns of the final result is shown below:

PATIENT_IDSAMPLE_IDAGE_AT_SEQ_REPORTONCOTREE_CODE
P1S141BLL
P2S260BLL
P3S3<18TLL
P4S471PTCL
P5S564PTCL
P6S636CHL
P7S763SPCC
P8S863MCL
P10S1052NA
P11S1177NA
P12S1287MTNN
P13S1379HDCN
P14S1453CLLSLL
P15S1569CLLSLL
P16S1665MNM
P17S1766MYCF
P18S1866RBL

Ontology to Ontology Mapping Tool ​

The Ontology Mapping tool was developed to facilitate the mapping between different cancer classification systems. We currently support mapping between OncoTree, ICD-O, NCIt, UMLS and HemeOnc systems. The tool and the mapping file (the mapping file does not need to be downloaded to run the tool) can be found here

Prerequisites ​

The Ontology Mapping tool runs on python 3 and requires pandas and requests libraries. These libraries can be installed using

pip3 install pandas
 pip3 install requests

Running the tool ​

The Ontology Mapping tool can be run with the following command:

python <path/to/scripts/ontology_to_ontology_mapping_tool.py> --source-file <path/to/source/file> --target-file <path/to/target/file> --source-code <source_ontology_code> --target-code <target_ontology_code>

Options

  • i | --source-file: This is the source file path. The source file must contain one of the ONCOTREE_CODE, NCIT_CODE, UMLS_CODE, ICDO_TOPOGRAPHY_CODE, ICDO_MORPHOLOGY_CODE or HEMEONC_CODE in the file header and it must contain codes corresponding to the Ontology System.
  • o | --target-file: This is the path to the target file that will be generated. It will contain ontologies mapped from source code in <source-file> to <target-code>.
  • s | --source-code: This is the source ontology code in <source-file>. It must be one of the ONCOTREE_CODE, NCIT_CODE, UMLS_CODE, ICDO_TOPOGRAPHY_CODE, ICDO_MORPHOLOGY_CODE or HEMEONC_CODE.
  • t | --target-code: This is the target ontology code that the script will attempt to map the source file ontology code to. It must be one of the ONCOTREE_CODE, NCIT_CODE, UMLS_CODE, ICDO_TOPOGRAPHY_CODE, ICDO_MORPHOLOGY_CODE or HEMEONC_CODE.

Note

  • The source file should be tab delimited and should contain one of the ontology: ONCOTREE_CODE, NCIT_CODE, UMLS_CODE, ICDO_TOPOGRAPHY_CODE, ICDO_MORPHOLOGY_CODE or HEMEONC_CODE in the file header.
  • We currently are allowing only one ontology to another ontology mapping. In the future, we plan to extend the tool to support mapping to multiple ontology systems.
- + \ No newline at end of file diff --git a/web/src/main/javascript/public/news.html b/web/src/main/javascript/public/news.html index be281a2..4a8cec9 100644 --- a/web/src/main/javascript/public/news.html +++ b/web/src/main/javascript/public/news.html @@ -18,7 +18,7 @@

Appearance

News ​

November 2, 2021 ​

  • New Stable Release OncoTree version oncotree_2021_11_02 is now the latest stable release. The previous stable version is still accessible as version oncotree_2020_10_01.
  • New nodes added:
    • Desmoplastic/Nodular Medulloblastoma, NOS (DMBLNOS)
    • Desmoplastic/Nodular Medulloblastoma, SHH Subtype (DMBLSHH)
    • Anaplastic Medulloblastoma, NOS (AMBLNOS)
    • Anaplastic Medulloblastoma, Non-WNT, Non-SHH (AMBLNWS)
    • Anaplastic Medulloblastoma, Group 3 (AMBLNWSG3)
    • Anaplastic Medulloblastoma, Group 4 (AMBLNWSG4)
    • Anaplastic Medulloblastoma, SHH Subtype (AMBLSHH)
    • Medulloblastoma, NOS (MBLNOS)
    • Medulloblastoma, Non-WNT, Non-SHH (MBLNWS)
    • Medulloblastoma, Group 3 (MBLG3)
    • Medulloblastoma, Group 4 (MBLG4)
    • Medulloblastoma, SHH Subtype (MBLSHH)
    • Medulloblastoma, WNT Subtype (MBLWNT)
    • Medulloblastoma with Extensive Nodularity, NOS (MBENNOS)
    • Medulloblastoma with Extensive Nodularity, SHH Subtype (MBENSHH)
    • Pancreatic Neuroendocrine Carcinoma (PANEC) in the original version of this news release this node was accidentally omitted
  • Nodes reclassified
    • The following list of oncotree codes had the mainType shortened to drop the suffix "NOS": ADRENAL_GLAND, AMPULLA_OF_VATER, BILIARY_TRACT, BLADDER, BONE, BOWEL, BRAIN, BREAST, CERVIX, EYE, HEAD_NECK, KIDNEY, LIVER, LUNG, LYMPH, MYELOID, OTHER, OVARY, PANCREAS, PENIS, PERITONEUM, PLEURA, PNS, PROSTATE, SKIN, SOFT_TISSUE, STOMACH, TESTIS, THYMUS, THYROID, UTERUS, VULVA
    • Cholangiocarcinoma (CHOL) now has direct parent Intraductal Papillary Neoplasm of the Bile Duct (IPN) [previously: Biliary Tract (BILIARY_TRACT)]
    • Gallbladder Cancer (GBC) now has direct parent Intracholecystic Papillary Neoplasm (ICPN) [previously: Biliary Tract (BILIARY_TRACT)]
  • oncotree candidate release version additions:
    • Three new nodes intended only for version oncotree_candidate_release were added (NVRINT, MPNWP, MDSWP). These nodes will not be incorperated into oncotree latest stable.
  • resources added
    • rdf formatted OWL ontology and taxomomy files for recent oncotree versions have been added to our github repository. They can be explored here .

November 4, 2020 ​

  • Ontology to Ontology Mapping tool available
    • The Ontology Mapping tool was developed to facilitate the mapping between different cancer classification systems. We currently support mapping between OncoTree, ICD-O, NCIt, UMLS and HemeOnc systems.
    • A mapping file containing mappings between the different ontologies and OncoTree codes as well as a python script to run the mapping is available on the OncoTree GitHub page . Details are also available on the Mapping Tools page .
    • The mapping file is expected to grow as we curate more ontology mappings for OncoTree codes.

October 1, 2020 ​

  • New Stable Release OncoTree version oncotree_2020_10_01 is now the latest stable release. The previous stable version is still accessible as version oncotree_2020_04_01.
  • New nodes added:
    • Basal Cell Carcinoma of Prostate (BCCP)
  • Node deleted:
    • Porphyria Cutania Tarda (PCT)
  • Node with updated name:
    • Goblet Cell Adenocarcinoma of the Appendix (GCCAP) [previously: Goblet Cell Carcinoid of the Appendix (GCCAP)].

April 1, 2020 ​

  • New Stable Release OncoTree version oncotree_2020_04_01 is now the latest stable release. The previous stable version is still accessible as version oncotree_2020_02_06.
  • New nodes added:
    • AML with Variant RARA translocation (AMLRARA)
  • Nodes reclassified:
    • Mixed Cancer Types (MIXED is now a child of Other (OTHER) [previously under: Cancer of Unknown Primary (CUP)].

February 6, 2020 ​

  • Web Link To Specific Nodes Available:
    • When providing web links to oncotree, you may include a search term as an optional argument and the oncotree you reference will be displayed with the search term located and highlighted. Use of this mechanism can be seen in the example output for the OncoTree-to-OncoTree code mapping tool.
    • As an example, you can provide a direct link to the TumorType node PANET in oncotree version oncotree_2019_12_01 with this link: http://oncotree.mskcc.org/#/home?version=oncotree_2019_12_01&search_term=(PANET)
  • New Stable Release OncoTree version oncotree_2020_02_06 is now the latest stable release. The previous stable version is still accessible as version oncotree_2020_02_01.
  • Nodes reclassified:
    • Gallbladder Cancer (GBC) is now a child of Biliary Tract (BILIARY_TRACT) [previously under: Intracholecystic Papillary Neoplasm (ICPN)].
    • Cholangiocarcinoma (CHOL) is now a child of Biliary Tract (BILIARY_TRACT) [previously under: Intraductal Papillary Neoplasm of the Bile Duct (IPN)].

February 1, 2020 ​

  • New Stable Release OncoTree version oncotree_2020_02_01 is now the latest stable release. The previous stable version is still accessible as version oncotree_2019_12_01.
  • New nodes added:
    • Intraductal Oncocytic Papillary Neoplasm (IOPN)
    • Intraductal Tubulopapillary Neoplasm (ITPN)
    • Intracholecystic Papillary Neoplasm (ICPN)
    • Intraductal Papillary Neoplasm of the Bile Duct (IPN)
  • Nodes reclassified:
    • Gallbladder Cancer (GBC) is now a child of Intracholecystic Papillary Neoplasm (ICPN) [previously under: Biliary Tract (BILIARY_TRACT)].
    • Cholangiocarcinoma (CHOL) is now a child of Intraductal Papillary Neoplasm of the Bile Duct (IPN) [previously under: Biliary Tract (BILIARY_TRACT)].

December 1, 2019 ​

  • New Stable Release OncoTree version oncotree_2019_12_01 is now the latest stable release. The previous stable version is still accessible as version oncotree_2019_08_01.
  • New nodes added:
    • Low-grade Appendiceal Mucinous Neoplasm (LAMN)

August 1, 2019 ​

  • New Stable Release OncoTree version oncotree_2019_08_01 is now the latest stable release. The previous stable version is still accessible as version oncotree_2019_05_01.
  • New nodes added:
    • Lacrimal Gland Tumor (LGT)
    • Adenoid Cystic Carcinoma of the Lacrimal Gland (ACLG)
    • Squamous Cell Carcinoma of the Lacrimal Gland (SCLG)
    • Basal Cell Adenocarcinoma (BCAC)
    • Carcinoma ex Pleomorphic Adenoma (CAEXPA)
    • Pleomorphic Adenoma (PADA)
    • Polymorphous Adenocarcinoma (PAC)
    • Atypical Lipomatous Tumor (ALT)

May 2, 2019 ​

  • OncoTree-to-OncoTree code mapping tool updated
    • The OncoTree-to-OncoTree mapping tool (now version 1.2) has been updated:
      • it no longer requires the installation of the python 'requests' module
      • it now is able to handle input files where lines end in carriage return (such as files saved from Microsoft Excel)

May 1, 2019 ​

  • New Stable Release OncoTree version oncotree_2019_05_01 is now the latest stable release. The previous stable version is still accessible as version oncotree_2019_03_01.
  • Nodes reclassified
    • Intestinal Ampullary Carcinoma (IAMPCA) MainType is now Ampullary Cancer [previously: Ampullary Carcinoma]
    • Mixed Ampullary Carcinoma (MAMPCA) MainType is now Ampullary Cancer [previously: Ampullary Carcinoma]
    • Pancreatobiliary Ampullary Carcinoma (PAMPCA) MainType is now Ampullary Cancer [previously: Ampullary Carcinoma]
    • Ependymoma (EPM) MainType is now Glioma [previously: CNS Cancer]
    • Rosai-Dorfman Disease (RDD) MainType is now Histiocytosis [previously: Histiocytic Disorder]

March 26, 2019 ​

  • OncoTree-to-OncoTree code mapping tool updated
    • The OncoTree-to-OncoTree mapping tool (now version 1.1) has been slightly improved, mainly by adding a separate section in the output summary for reporting OncoTree codes which were replaced automatically. Also, additional documentation and description of the tool has been added under the "Mapping Tools" tab.

March 14, 2019 ​

  • OncoTree-to-OncoTree code mapping tool available
    • A python program is now available for download under the webpage tab labeled "Mapping Tools". This tool will rewrite OncoTree codes in a tabular clinical data file, mapping from one version of OncoTree to another. When additional guidance is necessary, the program will insert a column containing options and comments next to the ONCOTREE_CODE column. After selecting an appropriate OncoTree code for cases which require action, this extra column can be deleted to produce a fully re-mapped clinical data file. More details about this tool and how to use it are available under the "Mapping Tools" tab.
    • The OncoTree-to-OncoTree mapping tool relies on an expanded model of OncoTree node history. This is reflected in the Web API schema for Tumor Types, which now has added properties called "precursors" and "revocations". Using these properties, and the existing "history" property, the tool is able to make proper mappings across OncoTree versions, and give suggestions when no clear mapping is available. It is also reflected in the main tree visualization of OncoTree, where a combination of these properties (when set) will be displayed in the pop-up information box with label "Previous Codes".

March 1, 2019 ​

  • New Stable Release OncoTree version oncotree_2019_03_01 is now the latest stable release. The previous stable version is still accessible as version oncotree_2019_02_01.
  • New node added:
    • NUT Carcinoma of the Lung (NUTCL)
  • Node with renamed OncoTree code:
    • Monomorphic Epitheliotropic Intestinal T-Cell Lymphoma (MEITL) [previously: MEATL]
  • Node with renamed OncoTree code and updated name:
    • Germ Cell Tumor with Somatic-Type Malignancy (GCTSTM) [previously: Teratoma with Malignant Transformation (TMT)]
  • Cross-version OncoTree code mapping tool coming soon
    • Development of a tool to map OncoTree codes between different versions of OncoTree is nearing completion.
    • Related to this, users of the OncoTree Web API should be aware that we will soon be adding two additional properties to the output schema returned by the api/tumorTypes endpoints. The properties "precursors" and "revocations" will be added alongside the "history" property (having the same type: an array of strings). These will help distinguish the kinds of possible relationships to OncoTree nodes in prior versions of OncoTree. We expect this new schema to be backwards compatible, but if your language or tools requires an exactly matching JSON schema you will need to make adjustments.

February 1, 2019 ​

  • New Stable Release OncoTree version oncotree_2019_02_01 is now the latest stable release. The previous stable version is still accessible as version oncotree_2018_11_01.
  • New node added:
    • Leiomyoma (LM)

November 1, 2018 ​

  • New Stable Release OncoTree version oncotree_2018_11_01 is now the latest stable release. The previous stable version is still accessible as version oncotree_2018_09_01.
  • New nodes added:
    • Gastrointestinal Neuroendocrine Tumors of the Esophagus/Stomach (GINETES)
    • High-Grade Neuroendocrine Carcinoma of the Esophagus (HGNEE)
    • High-Grade Neuroendocrine Carcinoma of the Stomach (HGNES)
  • Nodes reclassified:
    • Well-Differentiated Neuroendocrine Tumors of the Stomach (SWDNET) is now a child of Gastrointestinal Neuroendocrine Tumors of the Esophagus/Stomach (GINETES) [previously under: Bowel (BOWEL)].

September 1, 2018 ​

  • New Stable Release OncoTree version oncotree_2018_09_01 is now the latest stable release. The previous stable version is still accessible as version oncotree_2018_08_01.
  • Nodes with adjusted History:
    • Myeloid Neoplasm (MNM) previous code: LEUK
    • B-Lymphoblastic Leukemia/Lymphoma (BLL) previous code: BALL
    • T-Lymphoblastic Leukemia/Lymphoma (TLL) previous code: TALL
    • Essential Thrombocythemia (ET) previous code: ETC
    • Polycythemia Vera (PV) previous code: PCV
    • Diffuse Large B-Cell Lymphoma, NOS (DLBCLNOS) previous code: DLBCL
    • Sezary Syndrome (SS) previous code: SEZS

August 1, 2018 ​

  • New Stable Release OncoTree version oncotree_2018_08_01 is now the latest stable release. The previous stable version is still accessible as version oncotree_2018_07_01.
  • New nodes added:
    • Angiomatoid Fibrous Histiocytoma (AFH)
    • Clear Cell Sarcoma of Kidney (CCSK)
    • Ewing Sarcoma of Soft Tissue (ESST)
    • Extra Gonadal Germ Cell Tumor (EGCT)
    • Infantile Fibrosarcoma (IFS)
    • Malignant Glomus Tumor (MGST)
    • Malignant Rhabdoid Tumor of the Liver (MRTL)
    • Myofibromatosis (IMS)
    • Sialoblastoma (SBL)
    • Undifferentiated Embryonal Sarcoma of the Liver (UESL)

July 1, 2018 ​

  • New Stable Release OncoTree version oncotree_2018_07_01 is now the latest stable release. The previous stable version is still accessible through the OncoTree web API by requesting version oncotree_2018_06_15.
  • Node with renamed OncoTree code:
    • Atypical Chronic Myeloid Leukemia, BCR-ABL1- (ACML) [previously: aCML]

June 15, 2018 ​

  • New Stable Release OncoTree version oncotree_2018_06_15 is now the latest stable release. The previous stable version is still accessible through the OncoTree web API by requesting version oncotree_2018_06_01.
  • Nodes reclassified
    • Mature B-Cell Neoplasms (MBN) and Mature T and NK Neoplasms (MTNN) and their subnodes were relocated to be under Non-Hodgkin Lymphoma (NHL).
    • Rosai-Dorfman Disease (RDD) was relocated to be under Histiocytic and Dendritic Cell Neoplasms (HDCN). Previously RDD was under Lymphoid Neoplasm (LNM) in the Lymphoid category.

June 1, 2018 ​

  • New Stable Release OncoTree version oncotree_2018_06_01 is now the latest stable release. The previous stable version is still accessible through the OncoTree web API by requesting version oncotree_2018_05_01.
  • Blood and Lymph subtrees replaced with new Myeloid and Lymphoid subtrees:
    • 23 nodes in the previous Blood subtree have been deleted or relocated/renamed. Affected OncoTree codes from this tree: BLOOD, BPDCN, HIST, LCH, ECD, LEUK, ALL, BALL, TALL, AMOL, AML, CLL, CML, CMML, HCL, LGLL, MM, MDS, MPN, ETC, MYF, PCV, SM
    • 28 nodes in the previous Lymph subtree have been deleted or relocated/renamed. Affected OncoTree codes from this tree: LYMPH, HL, CHL, NLPHL, NHL, BCL, BL, DLBCL, MALTL, FL, MCL, MZL, MBCL, NMZL, PCNSL, PEL, SLL, SMZL, WM, TNKL, CTCL, MYCF, SEZS, PTCL, ALCL, AITL, PTCLNOS, RD
    • 122 nodes in the current Lymphoid subtree have been added or relocated/renamed from previous subtrees. OncoTree codes in this new subtree are: LYMPH, LATL, LBGN, LNM, BLL, BLLRGA, BLLHYPER, BLLHYPO, BLLIAMP21, BLLETV6RUNX1, BLLTCF3PBX1, BLLIL3IGH, BLLBCRABL1, BLLKMT2A, BLLBCRABL1L, BLLNOS, HL, CHL, LDCHL, LRCHL, MCCHL, NSCHL, NLPHL, MBN, ALKLBCL, AHCD, BCLU, BPLL, BL, BLL11Q, CLLSLL, DLBCLCI, DLBCLNOS, ABC, GCB, EBVDLBCLNOS, EBVMCU, EP, FL, DFL, ISFN, GHCD, HHV8DLBCL, HCL, HGBCL, HGBCLMYCBCL2, IVBCL, LBLIRF4, LYG, LPL, WM, MCL, ISMCL, MZL, EMALT, NMZL, SMZL, MCBCL, MGUS, MGUSIGA, MGUSIGG, MGUSIGM, MIDD, MIDDA, MIDDO, MHCD, PTFL, PCM, PLBL, PCLBCLLT, PCFCL, PCNSL, PEL, PMBL, SPB, SBLU, HCL-V, SDRPL, THRLBCL, MTNN, ATLL, ANKL, ALCL, ALCLALKN, ALCLALKP, BIALCL, AITL, CLPDNK, EATL, ENKL, FTCL, HSTCL, HVLL, ITLPDGI, MEATL, MYCF, NPTLTFH, PTCL, PCATCL, PCLPD, LYP, PCALCL, PCSMTPLD, PCAECTCL, PCGDTCL, SS, SPTCL, SEBVTLC, TLGL, TPLL, NHL, PTLD, CHLPTLD, FHPTLD, IMPTLD, MPTLD, PHPTLD, PPTLD, RDD, TLL, ETPLL, NKCLL
    • 101 nodes in the current Myeloid subtree have been added or relocated/renamed from previous subtrees. OncoTree codes in this new subtree are: MYELOID, MATPL, MBGN, MNM, ALAL, AUL, MPALBCRABL1, MPALKMT2A, MPALBNOS, MPALTNOS, AML, AMLMRC, AMLRGA, AMLRBM15MKL1, AMLBCRABL1, AMLCEBPA, AMLNPM1, AMLRUNX1, AMLCBFBMYH11, AMLGATA2MECOM, AMLDEKNUP214, AMLRUNX1RUNX1T1, AMLMLLT3KMT2A, APLPMLRARA, AMLNOS, AM, AMLMD, AWM, ABL, AMKL, AMOL, AMML, APMF, PERL, MPRDS, MLADS, TAM, MS, TMN, TAML, TMDS, BPDCN, HDCN, JXG, ECD, FRCT, FDCS, HS, IDCT, IDCS, LCH, LCS, MCD, CMCD, MCSL, SM, ASM, ISM, SMMCL, SSM, SMAHN, MDS, MDSEB, MDSEB1, MDSEB2, MDSID5Q, MDSMD, MDSRS, MDSRSMD, MDSRSSLD, MDSSLD, MDSU, RCYC, MDS/MPN, aCML, CMML, CMML0, CMML1, CMML2, JMML, MDSMPNRST, MDSMPNU, MNGLP, MLNER, MLNFGFR1, MLNPCM1JAK2, MLNPDGFRA, MLNPDGFRB, MPN, CELNOS, CML, CMLBCRABL1, CNL, ET, ETMF, MPNU, PV, PVMF, PMF, PMFPES, PMFOFS
  • Nodes reclassified
    • Adrenocortical Adenoma (ACA) MainType is now Adrenocortical Adenoma [previously: Adrenocortical Carcinoma]
    • Ampulla of Vater (AMPULLA_OF_VATER) MainType is now Ampullary Cancer [previously: Ampullary Carcinoma]
    • Parathyroid Cancer (PTH) MainType is now Parathyroid Cancer [previously: Head and Neck Cancer]
    • Parathyroid Carcinoma (PTHC) MainType is now Parathyroid Cancer [previously: Head and Neck Cancer]
    • Follicular Dendritic Cell Sarcoma (FDCS) was moved from the Soft Tissue subtree into the Myeloid subtree with direct parent Histiocytic and Dendritic Cell Neoplasms (HDCN)
    • Interdigitating Dendritic Cell Sarcoma (IDCS) was moved from the Soft Tissue subtree into the Myeloid subtree with direct parent Histiocytic and Dendritic Cell Neoplasms (HDCN)
  • New nodes added:
    • Inverted Urothelial Papilloma (IUP)
    • Urothelial Papilloma (UPA)
    • Oncocytic Adenoma of the Thyroid (OAT)
  • Character set simplification
    • Salivary Gland-Type Tumor of the Lung (SGTTL) used to contain a unicode character for a horizontal dash. This punctuation mark is now a hyphen.

May 1, 2018 ​

  • New Stable Release OncoTree version oncotree_2018_05_01 is now the latest stable release. The previous stable version is still accessible through the OncoTree web API by requesting version oncotree_2018_04_01.
  • New nodes added:
    • Primary CNS Melanocytic Tumors (PCNSMT)
    • Melanocytoma (MELC)
  • Node reclassified
    • Primary CNS Melanoma (PCNSM) now is a child of Primary CNS Melanocytic Tumors (PCNSMT) [previously under: CNS/Brain].

April 23, 2018 ​

  • New Web API Version Available
  • Details and Migration Guidance
    • The base URL for accessing all API functionality is being simplified from ~~http://oncotree.mskcc.org/oncotree/~~ to http://oncotree.mskcc.org/
    • The /api/tumor_types.txt endpoint is now deprecated. It is scheduled for deletion as part of the next API version release.
    • Most endpoint paths in the API remain the same and provide the same services. Exceptions are:
      • /api/tumorTypes used to accept a query parameter ("flat") which controlled the output format for receiving a tree representation or a flat representation of the full set of TumorTypes. Now this endpoint always returns a flat list of all TumorTypes and a new endpoint path (/api/tumorTypes/tree) is used to retrieve a tree representation of the OncoTree. Previous requests which included "flat=false" should be adjusted to use the /api/tumorTypes/tree endpoint. Otherwise "flat=true" should be dropped from the request.
      • /api/tumorTypes used to accept a query parameter ("deprecated") which is no longer recognized. This parameter should be dropped from requests. Deprecated OncoTree codes can instead be found in the history attribute of the response.
      • the POST request endpoint (/api/tumorTypes/search) which accepted a list of TumorType queries has been deprecated and is no longer available through the swagger-ui interface. The GET request endpoint /api/tumorTypes/search/{type}/{query} remains available as before. If you previously submitted an array of query requests, you should iterate through the array and call the GET request endpoint to make one query per request.
    • The output format (schema) of many endpoints has been simplified. You will need to adjust your result handling accordingly. Changes include:
      • responses no longer include a "meta" element with associated code and error messages. Instead HTTP status codes are set appropriately and error messages are supplied in message bodies. Responses also no longer contain a "data" element. Objects representing the API output are directly returned instead.
      • MainType values are no longer modeled as objects. Each MainType value is now represented as a simple string. The /api/mainTypes endpoint now returns an array of strings rather than an object mapping MainType names to MainType objects.
      • TumorType values no longer contain elements "id", "deprecated", "links", "NCI", "UMLS". A new element ("externalReferences") has been added which contains a JSON object mapping external authority names to arrays of associated identifiers. Such as "externalReferences":
    • Argument validation has been strengthened for several parameters, such as "type" and "levels" in the /api/tumorTypes/search/{type}/{query} endpoint. Now improper arguments cause an a HTTP status response indicating error, with a description of the problem in the body.
    • Some requests which fail to find matching entities now return NOT_FOUND HTTP status code 404 rather than an empty result. Examples: http://oncotree.mskcc.org/api/tumorTypes/search/code/TEST_UNDEFINED_CODE or http://oncotree.mskcc.org/api/crosswalk?vocabularyId=ICDO&conceptId=C15

April 1, 2018 ​

  • New Stable Release OncoTree version oncotree_2018_04_01 is now the latest stable release. The previous stable version is still accessible through the OncoTree web API by requesting version oncotree_2018_03_01.
  • New nodes added:
    • Adamantinoma (ADMA)
    • Tubular Adenoma of the Colon (TAC)
    • Parathyroid Cancer (PTH)
    • Parathyroid Carcinoma (PTHC)
    • Renal Neuroendocrine Tumor (RNET)

March 1, 2018 ​

  • New Stable Release OncoTree version oncotree_2018_03_01 is now the latest stable release. The previous stable version is still accessible through the OncoTree web API by requesting version oncotree_2018_02_01.
  • New node added:
    • Ganglioneuroma (GN)
  • Node reclassified
    • Rhabdoid Cancer (MRT) now has direct parent Kidney (KIDNEY) [previously: Wilms' Tumor (WT)] Main type is now "Rhabdoid Cancer" [previously: Wilms Tumor]

February 7, 2018 ​

  • OncoTree format expanded to support deeper tree nodes
    • To support upcoming expansion of the OncoTree, the 5 named levels of the OncoTree {Primary, Secondary, Tertiary, Quaternary, Quinternary} have been dropped in favor of level numbers {1, 2, 3, 4, 5, ...}. Web API functions have been adjusted accordingly, and an API function which outputs a table format of the OncoTree has been adjusted to output 7 levels of depth.
  • Additional improvements to the website :
    • tab-style navigation
    • more prominent version selection information
    • a new News page

February 1, 2018 ​

  • New Stable Release OncoTree version oncotree_2018_02_01 is now the latest stable release. The previous stable version is still accessible for use through version name oncotree_2018_01_01.
  • New nodes added:
    • Adenosquamous Carcinoma of the Gallbladder (GBASC)
    • Gallbladder Adenocarcinoma, NOS (GBAD)
    • Small Cell Gallbladder Carcinoma (SCGBC)
    • Juvenile Secretory Carcinoma of the Breast (JSCB)
    • Osteoclastic Giant Cell Tumor (OSGCT)
    • Peritoneal Serous Carcinoma (PSEC)
  • Nodes reclassified [from: Embryonal Tumor, to: Peripheral Nervous System]:
    • Ganglioneuroblastoma (GNBL)
    • Neuroblastoma (NBL)
  • Node with renamed OncoTree code:
    • Spindle Cell Carcinoma of the Lung (SPCC) [previously: SpCC]
- + \ No newline at end of file diff --git a/web/src/main/javascript/src/App.tsx b/web/src/main/javascript/src/App.tsx index 0e420e1..c276b7b 100644 --- a/web/src/main/javascript/src/App.tsx +++ b/web/src/main/javascript/src/App.tsx @@ -7,6 +7,7 @@ import { useCallback, useEffect, useState } from "react"; import "react-toastify/dist/ReactToastify.css"; import { Bounce, toast, ToastContainer } from "react-toastify"; import News from "./pages/News/News"; +import FAQ from "./pages/FAQ/FAQ"; import { DEFAULT_VERSION, ONCOTREE_TREE_URL, @@ -79,6 +80,7 @@ function App() { } /> } /> } /> + } />