This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
documentation:oncology:meeting_notes_2017_apr_04 [2017/04/10 03:23] rimma_belenkaya1 |
documentation:oncology:meeting_notes_2017_apr_04 [2017/04/10 03:36] (current) rimma_belenkaya1 |
||
|---|---|---|---|
| Line 14: | Line 14: | ||
| **Exploratory data set** | **Exploratory data set** | ||
| + | |||
| · Christian would try putting together a working data set | · Christian would try putting together a working data set | ||
| Line 24: | Line 25: | ||
| - | · Iker suggested that the ICD-O-3 could be mapped to SNOMED and agreed to provide some links to the group. | + | **ICD-O-3 Mapping** |
| + | |||
| + | * Iker suggested that NCI Metatethaurus provides mapping of ICD-O-3 to SNOMED and some other vocabularies | ||
| + | |||
| + | * Memorial Sloan Kettering (MSK) Oncotree mapping | ||
| + | |||
| + | At MSK we maintain a cancer tumor terminology called oncotree (which is publicly available) | ||
| + | http://oncotree.mskcc.org/oncotree/ | ||
| + | |||
| + | We also have a public API that maps ICDO site and histology combinations to Oncotree concepts, which at the same time are mapped to NCI Thesaurus and UMLS, see | ||
| + | http://oncotree.mskcc.org/oncotree-mappings/ | ||
| + | |||
| + | An example for that API would be | ||
| + | http://oncotree.mskcc.org/oncotree-mappings/crosswalk?vocabularyId=ICDO&conceptId=&histologyCode=8490/3&siteCode=C16.1 | ||