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

UBERON cites SNOMED E-node codes - why not the structure codes? #3287

Open
salai999 opened this issue Jun 3, 2024 · 1 comment
Open

UBERON cites SNOMED E-node codes - why not the structure codes? #3287

salai999 opened this issue Jun 3, 2024 · 1 comment

Comments

@salai999
Copy link

salai999 commented Jun 3, 2024

Hi there –
I am trying to figure out why UBERON cites the E-node (entire from SNOMED CT’s representation of anatomy Structure-Entire-Part (SEP) triples) instead of the structure codes in SNOMED-CT. For example, the breast in UBERON is 0000310 http://purl.obolibrary.org/obo/UBERON_0000310 and the cited SNOMED CT code is SCTID:181131000 (entire breast) while the higher level (which includes part-whole distinction) is SCTID:76752008. This is true of any terms that I have looked through in UBERON. The citation is e-node and not s-node. I wanted to see what was the rationale for this decision to better understand the relationship between UBERON and SNOMED-CT.

@cmungall
Copy link
Member

cmungall commented Jun 3, 2024

For context for everyone not familiar with SNOMED SEP model: https://confluence.ihtsdotools.org/display/DOCEG/Anatomical+Concept+Model

I think the E node is the correct one, since the uberon class represents the entity. More importantly, equivalence axioms can be made between E nodes without incoherency.

For example, snomedct:181500002 ! Entire skin of areola (body structure) is a subclass of the s-node 76752008. But the equivalent of this in Uberon would not be a subclass of breast, it would be a part of the breast, and entailing it is a subclass would likely lead to unsatisfiable classes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants