Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should we establish 'extension' and 'invasion' hierarchies with Cancer Modifier? #623

Open
Tracked by #614
rtmill opened this issue Oct 30, 2023 · 0 comments
Open
Tracked by #614
Assignees

Comments

@rtmill
Copy link
Collaborator

rtmill commented Oct 30, 2023

Extension and Invasion concepts exist within Cancer Modifier but have no linkages - neither mappings nor hierarchically.

Extension example: https://athena.ohdsi.org/search-terms/terms/36769838

Invasion example: https://athena.ohdsi.org/search-terms/terms/36769449


Alternatively, SNOMED has hierarchies we may be able to leverage rather than creating our own new hierarchies. They both fall under the "tumor finding" hierarchy.

SNOMED Invasion hierarchy : https://athena.ohdsi.org/search-terms/terms/4159956

SNOMED Extension hierarchy: https://athena.ohdsi.org/search-terms/terms/4300153


Option A) Rebuild our own hierarchies within Cancer Modifier
Option B) Leverage SNOMED instead and de-standardize extension/invasion concepts in Cancer Modifier
Option C) Something else

@rtmill rtmill moved this to Outstanding in Oncology Maturity Sprint Oct 30, 2023
@rtmill rtmill moved this from Outstanding to In Progress in Oncology Maturity Sprint Oct 30, 2023
@rtmill rtmill self-assigned this Nov 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: In Progress
Development

No branches or pull requests

1 participant