Was I asleep when NAACCR was added to Athena?
We added that 3 am last night? You are saying you slacked off and didn’t stay awake to catch that event, @jliddil1?
Not sure how much you are aware of the plans. Well, “plans” is a strong word. We are trying to find the trajectory as we go. Currently, the plan is:
- Bring in NAACCR data dictionary (done)
- Evaluate CAP Cancer Checklists
- Map these to the emerging Nebraska Lexicon
- Help with its development and the incorporation into SNOMED
- Iterate over HemOnc
- Build an Episode vocabulary
- Link and map the hell out of these so we have one concept for each important cancer attribute
@mgurley: Something I am missing?
That looks about right. Small tweaks:
- Bring in ICDO vocabulary (done but needs to be tested).
- Bring in Hemonc.org (done but needs to be tested).
- Bring in NAACCR data dictionary (done but needs to be tested).
- Bring in first version of Episode vocabulary (done by needs to be tested).
- Publish first version of ETL documentation.
- Test ETLing targeting NAACCR and Hemonc.org vocabularies.
- Expand ETL documentation from non-NAACCR sources.
- Evaluate Observational Research in Oncology Toolbox for treatment algorithm derivations.
- Evaluate CAP Cancer Checklists for cancer modifier vocabulary.
- Bring in Nebraska Lexicon data dictionary for cancer modifier vocabulary.
- Link and map the hell out of these so we have one concept for each important cancer attribute.
- Expand Episode vocabulary to cover recurrence/progression/remission/relapse.
- Conventionalize outcome vocabularies and representation (for example, performance status declarations)
- Merge Oncology Workgroup work with Genomic CDM workgroup work.
More than this but this is a good big outline.
Cool. I’ll be remapping some terms now that NAACCR is in the list via USAGI to see how things compare
How to know about the vocabulary updates?
subscribe to https://github.com/OHDSI/Vocabulary-v5.0/releases/
Updated version of NAACCR is released. Some inaccurracies fixed.
Now it supports concept_numeric.xlsx (111.6 KB)
table (not ratified by OHDSI community yet).
The overall idea is that if the concept stands for some numeric value, for example “4 or more phases” or “Greater than 10,000 ng/mL” it can be easily put in MEASUREMENT as value_as_number, unit and operator.
More detailed documentation and proposal on CONCEPT_NUMERIC will be posted later.
This is most excellent