This shows you the differences between two versions of the page.
Next revision | Previous revision Last revision Both sides next revision | ||
documentation:oncology:meeting_notes_2019_aug-29 [2019/08/30 11:35] mgurley created |
documentation:oncology:meeting_notes_2019_aug-29 [2019/08/30 13:49] mgurley |
||
---|---|---|---|
Line 4: | Line 4: | ||
+ | * Robert Miller asked about how code that prepares data for the common ETL input format should deal with ambiguous ICDO site/histology combination in multiple NAACCR schemas. | ||
+ | * It was decided that pre-reprocessing code should not consider the ambiguity and rely ETL code to skip ambigious ICDO site/histology combinations. SQL for identifying NAACCR ambiguities is here: https://github.com/OHDSI/OncologyWG/blob/master/documentation/debug_naaccr_ambiguites.sql | ||
* It was agreed that 'Create ICDO concept for 'Unknown Histology' and precoordinate with all ICDO sites.' is not on the critical path for the symposium. | * It was agreed that 'Create ICDO concept for 'Unknown Histology' and precoordinate with all ICDO sites.' is not on the critical path for the symposium. | ||
* https://github.com/OHDSI/OncologyWG/issues/67 | * https://github.com/OHDSI/OncologyWG/issues/67 | ||
Line 27: | Line 29: | ||
* We discussed timelines for Symposium. | * We discussed timelines for Symposium. | ||
* Dymytry said that the vocabulary will aim to have the tasks done by 9/5 | * Dymytry said that the vocabulary will aim to have the tasks done by 9/5 | ||
- | * The group agreed that analysis code should aim to be done by the 9/16 | + | * The group agreed that analysis code should aim to be done by the 9/9 |
- | * The group agreed that ETL work shold aim to be done by 9/16. | + | * The group agreed that ETL work shold aim to be done by 9/9. |
* We discussed Andrew Williams concerns about how to frame the results. | * We discussed Andrew Williams concerns about how to frame the results. | ||
* The group agreed that we should frame the results as a beta test proof-of-concept. That many problems, flaws and challenges exist but that have a version 1 accomplished. | * The group agreed that we should frame the results as a beta test proof-of-concept. That many problems, flaws and challenges exist but that have a version 1 accomplished. | ||