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
Looking at all the diseases returned back from ICEES @karafecho explained to me that those Ids are High level concepts. And when I was looking at the equivalent identifiers for those concepts, I see some that have might mean separate entities in robokop exist on the list of equivalent ids for a node,
Here is an example to illustrate:
'AsthmaDx': (id: SCTID:195967001) -- > this is not used by ROBOKOP
IN AsthmaDx equivalent ids these are some of them used
'MONDO:0011805'
'MONDO:0043919' --
'MONDO:0041850'
'MONDO:0012577'
'MONDO:0004649'
'HP:0002105'
and they exist as seperate entities
....
On solution to this might be going over the list of equivalent ids and generating more questions for the rest of the query when crossing from one KG to another
So, the identifier spreadsheet that I created includes different identifier schemes for each entity. If I'm not mistaken, our original plan was to attach all of them to each ICEES concept, such as 'AsthmaDx'. That way, the transition to ROBOKOP would return a broad range of downstream nodes.
I don't think that additional questions will solve this issue, as any solution should be high-level and query-agnostic. We may want to meet and discuss this.
Regardless of queries tested, transitions from ICEES diseases (pink nodes) to ROBOKOP genes (yellow nodes) are incomplete.
The text was updated successfully, but these errors were encountered: