You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I believe these two predicates are not semantically equivalent. For most (probably more than 95%) of the triples in SemMedDB that have the SEMMEDDB:diagnoses relation, the subject concept has a semantic type of Procedure. Also, this semantically inequivalent mapping is causing problems with real use-cases for Translator, as shown here: RTXteam/RTX#1774
As it happens, now there is a predicate biolink:diagnoses, which I think may be a better fit for SEMMEDDB:diagnoses:
Is your feature request related to a problem? Please describe.
Currently, the relation
SEMMEDDB:diagnoses
is mapped tobiolink:biomarker_for
.biolink-model/biolink-model.yaml
Line 4469 in ca93f7e
I believe these two predicates are not semantically equivalent. For most (probably more than 95%) of the triples in SemMedDB that have the
SEMMEDDB:diagnoses
relation, the subject concept has a semantic type ofProcedure
. Also, this semantically inequivalent mapping is causing problems with real use-cases for Translator, as shown here:RTXteam/RTX#1774
As it happens, now there is a predicate
biolink:diagnoses
, which I think may be a better fit forSEMMEDDB:diagnoses
:biolink-model/biolink-model.yaml
Line 2002 in ca93f7e
What working group (or team) did this request originate from?
Team Expander Agent
Note: This is relevant for members of NCATS Translator.
Describe the solution you'd like
Could the relation mapping be updated so that
SEMMEDDB:diagnoses
is mapped tobiolink:diagnoses
?Additional information to support this request (optional)
Tag relevant members for discussion
@sierra-moxon
The text was updated successfully, but these errors were encountered: