-
Notifications
You must be signed in to change notification settings - Fork 3
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
Capture EPCs for Drug Concepts #436
Comments
Examples of other sources through RxNav API that might also have this type of data: https://lhncbc.nlm.nih.gov/RxNav/APIs/api-RxClass.getSourcesOfDrugClassRelations.html
|
Additional documentation on EPC: https://www.fda.gov/media/77834/download |
Also on the subject, might actually be useful to just grab both EPCs and MOAs |
We should put some firm requirements on what data we want, and for what purposes -- I think that will help us divvy up responsibilities for fetching and serving this. My general preference would be to fetch(/store?) data with regbot and then expose it in a way that the normalizer can easily integrate into downstream sources like DGIdb (e.g. DailyMed as a drug claim source that provides drug classes) or MetaKB (some kind of annotation onto therapies for grouping). |
I can figure out where all of this lives reliably, but immediately I'm thinking we would probably want EPC plus the components that contribute to EPC definition: Mechanism of Action (MOA), Physiologic Effect (PE), and Chemical Structure (CS). I think EPC, MOA, and CS have clear applications for classification and function in dgidb. For PE, looking at some examples of this field it seems like it is "free text-ish" in that you'll get descriptions that look like "Altered neurotransmitter activity" or "Decreased prostaglandin production". I think while not really standardized, this could potentially have applications in MetaKB as a field attached to TherapeuticAgent nodes. I am on-board for using regbot to fetch this data. Should I move this issue to the regbot repo? |
We should consider grabbing established pharmacologic classes (EPC) when available for drug concept groups. This information would have clinical benefits for downstream applications of Thera-py, such as in DGIdb where this EPC could help inform clinical relevance of interaction data.
This is available from sources like DailyMed. An example from https://rxnav.nlm.nih.gov/REST/rxclass/class/byDrugName.json?drugName=imatinib&relaSource=DAILYMED&relas=has_epc ->
The text was updated successfully, but these errors were encountered: