-
Notifications
You must be signed in to change notification settings - Fork 11
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
BTE and "reverse" semmed operations #227
Comments
There are three options for solving this:
After discussion with @colleenXu, we will go forward with option 2 above -- Colleen will update |
After talking with Andrew Su today, this ticket is on hold for two reasons.
Details below: The original inspiration for this ticket was "reverse" operations for SEMMED apis. However, only annotating the operations in x-bte did not result in successfully-executed operations (the saved yaml with these reverse operations added is here)...BTE looks to execute the query correctly, but doesn't seem to process it correctly to pick out the output IDs. One can try it themselves by converting the yaml to json, then saving it to the test/smartapi.json in bte-trapi, compiling their local instance, and then sending queries (POST) to the test/query endpoint of the local instance. It looks like BTE's code for processing the SEMMED APIs' responses would need refactoring (recognizing the two different structures for reverse vs forward querying and processing them differently?). Example: to get from the Disease "Congenital pectus carinatum" (UMLS:C0158731) to the chemicals that treat it, we can do this "reverse" query to SEMMED chemical API: POST to https://biothings.ncats.io/semmedchemical/query?fields=umls
The response looks like this:
This is a different structure compared to what BTE "sees" with forward querying, and I think it's being processed incorrectly by BTE's current code for handling SEMMED API responses... |
need to check that this query works before closing... |
I've confirmed that we are now able to do this query with semmeddb (after modifying it to use ChemicalEntity)....and get the expected result. This is because semmeddb is annotated with the reverse operations. The SRI-ID resolver does equate HP:0002013 to UMLS:C0042963. However, it currently does not recognize UMLS:C0022237, so BTE does not have its name as isoproyl alcohol... The query
Returns a node
with this edge:
|
When issuing this query for ChemicalSubstances related to cyclic vomiting, we expect BTE to return a result for (at least) isopropyl alcohol. Currently BTE returns no results.
HP:0002013
should get translated toUMLS:C0042963
via http://pending.biothings.io/hpo/phenotype/HP:0002013, and then we should be able to get thatUMLS:C0042963
is treated by isopropyl alcohol (UMLS:C0022237
) via http://pending.biothings.io/semmedchemical/query?q=treats.umls:C0042963&limit=500&fields=name.Source issue: NCATSTranslator/testing#91
The text was updated successfully, but these errors were encountered: