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

annotate mychem.info fda_adverse_event mapping to "biolink:causes_adverse_event" #217

Closed
andrewsu opened this issue Jun 29, 2021 · 7 comments
Assignees

Comments

@andrewsu
Copy link
Member

mychem reports adverse event data from FAERS (through drug central). For example: https://mychem.info/v1/query?q=drugbank.name:nitisinone&fields=drugcentral.fda_adverse_event

{
    "took": 4,
    "total": 1,
    "max_score": 8.669861,
    "hits": [
        {
            "_id": "OUBCNLGXQFSTLU-UHFFFAOYSA-N",
            "_score": 8.669861,
            "drugcentral": {
                "_license": "http://bit.ly/2SeEhUy",
                "fda_adverse_event": [
                    {
                        "drug_ae": 5,
                        "drug_no_ae": 142,
                        "level": "PT",
                        "llr": 11.1531004639185,
                        "llr_threshold": 94.8398736756999,
                        "meddra_code": 10040047,
                        "meddra_term": "Sepsis",
                        "no_drug_ae": 32368,
                        "no_drug_no_ar": 3353344
                    },

...

We should add an edge in the mychem openapi file (https://github.com/NCATS-Tangerine/translator-api-registry/blob/master/mychem.info/openapi_full.yml) that links ChemicalSubstance to DiseaseOrPhenotypicFeature using the predicate biolink:causes_adverse_event.

Prompted by this Translator standup query: NCATSTranslator/testing#82

@colleenXu
Copy link
Collaborator

colleenXu commented Jul 7, 2021

My understanding is that we try NOT to map to those higher biolink entity classes.

I would suggest using PhenotypicFeature (or maybe Disease) rather than DiseaseOrPhenotypicFeature. With the example link above, most things look like PhenotypicFeatures (one exception is Hepatocellular carcinoma).

For the operation above, the IDs are names (ChemicalSubstances) and MEDDRA (PhenotypicFeatures?). Perhaps we should use something else for ChemicalSubstances (other drugcentral-based operations are using CHEMBL.COMPOUND ids)? There are MEDDRA mappings for PhenotypicFeature in the biomedical id resolver config file currently....and I added Disease MEDDRA mappings in this PR: biothings/biomedical_id_resolver.js#61

colleenXu added a commit to NCATS-Tangerine/translator-api-registry that referenced this issue Jul 7, 2021
note: mapping to PhenotypicFeature MEDDRA rather than Disease....is that okay?

To address biothings/biothings_explorer#217
@colleenXu colleenXu self-assigned this Jul 7, 2021
@andrewsu
Copy link
Member Author

The commit to add x-bte-kgs-operations/causesAdverseEvent and x-bte-kgs-operations/adverseEventCausedBy in NCATS-Tangerine/translator-api-registry@9155bf8 looks good to me. The use of Phenotypic Feature instead of DiseaseOrPhenotypicFeature sounds good to me. Do we also need to add MEDDRA as a Disease ID (biothings/biomedical_id_resolver.js@4d4e1ad), or can we treat all MEDDRA IDs as Phenotypic Features only?

@colleenXu
Copy link
Collaborator

TDLR: deciding to map MEDDRA IDs to Disease semantic type right now, since

  1. we have the most mapping support for it in MyDisease right now
  2. this will likely be useful for use cases (doing another hop from the Disease to treatments like chemicals, for instance)

Comparing the xrefs to MEDDRA that we have right now:

colleenXu added a commit to NCATS-Tangerine/translator-api-registry that referenced this issue Jul 19, 2021
Making it Biolink Disease for now, since we have more support for mapping to other IDs through MyDisease (see [comment](biothings/biothings_explorer#217 (comment))).
@colleenXu
Copy link
Collaborator

colleenXu commented Jul 19, 2021

How to find examples to test BTE with:

  1. Look at MyDisease for records with the meddra xrefs
  2. Query MyChem for records with the meddra code like this. If you return results, then these can be used as examples.

Some associations that we can expect to retrieve:

  • Disease acute respiratory distress syndrome (MEDDRA:10001052) <-> ChemicalSubstance neulasta (CHEMBL.COMPOUND:CHEMBL1201568)
  • Disease angioimmunoblastic T-cell lymphoma (MEDDRA:10002449) <-> ChemicalSubstance brentuximab vedotin (CHEMBL.COMPOUND:CHEMBL1742994)
  • Disease Clostridium difficile colitis (MEDDRA:10009657) <-> ChemicalSubstance nivestim (CHEMBL.COMPOUND:CHEMBL1201567)

@andrewsu
Copy link
Member Author

I didn't do a live test, but these changes look like they address the intent and desired behavior describe in this issue...

@colleenXu
Copy link
Collaborator

colleenXu commented Jul 22, 2021

[edit: Fix was to use drugcentral.xrefs.chembl_id (1994 / 2016 of the drugcentral adverse event records also have this field]

The operation for Chemical -> Disease will sometimes encounter issues with ID resolving the chemical.

There are 2016 records with drugcentral adverse event info, and 1768 of them also have chembl.molecule_chembl_id. This leaves 248 records that don't have the chembl field; however, their _id does seem to be CHEMBL.COMPOUND.

For Disease -> Chemical, I can handle this by changing the scope of the mychem query (to have "_id,chembl.molecule_chembl_id").

But for Chemical -> Disease, I can only give one field for the output ID mapping...so I'll do chembl.molecule_chembl_id since more records will have this.

colleenXu added a commit to NCATS-Tangerine/translator-api-registry that referenced this issue Aug 4, 2021
note: mapping to PhenotypicFeature MEDDRA rather than Disease....is that okay?

To address biothings/biothings_explorer#217
colleenXu added a commit to NCATS-Tangerine/translator-api-registry that referenced this issue Aug 4, 2021
Making it Biolink Disease for now, since we have more support for mapping to other IDs through MyDisease (see [comment](biothings/biothings_explorer#217 (comment))).
@colleenXu
Copy link
Collaborator

Should be addressed, since both PRs are merged now.

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

No branches or pull requests

2 participants