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

Clinical Data ARS Use Case - Y3 Prioritization #1 - Clinical x Genetics #4

Open
karafecho opened this issue Mar 5, 2021 · 4 comments
Assignees

Comments

@karafecho
Copy link
Contributor

This issue is intended to initiate discussion on how Translator clinical KPs can best leverage the genetics knowledge available via the Translator Genetics Provider.

@karafecho
Copy link
Contributor Author

As I mentioned on the last Clinical Data Committee call, Exposures Provider is considering a new use case on 'rare disease phenotypes'. This is an idea that I had to (1) overcome the challenges that clinical KPs face when trying to use EHR data to study rare diseases and (2) better align the Exposures Provider with the goals of the Translator program (i.e., move away from common diseases such as asthma toward rare diseases).

The general idea is as follows. Rare diseases typically do not have a definitive ICD code, and EHR data on patients with rare diseases generally cannot be exposed due to privacy concerns. However, rare diseases are often associated with clusters of phenotypes that do have ICD and LOINC codes associated with them. Moreover, ontologies such as MONDO are working to map rare-disease 'concepts' or 'leaf terms' (terminal nodes in ontology trees) to ICD and LOINC codes. These EHR codes can be used as 'selection criteria' when creating a cohort of patients.

I can envision the integration of clinical data with genetics data as part of the proposed 'rare disease phenotype' use case. For instance, hypermobility-EDS is associated with phenotypes such as generalized joint hypermobility, abdominal pain, soft velvety skin, and bruising. A causal genetic variant(s) for hEDS has not been established. The Genetics Provider may be able to suggest variants that are shared by hEDS-associated phenotypes.

@flannick : Thoughts?

@karafecho
Copy link
Contributor Author

karafecho commented Mar 12, 2021

In addition, I think that our existing use case on asthma and related common disorders might identify clusters of phenotypes for which Genetics Provider might suggest causal variants.

@karafecho karafecho changed the title How do clinical KPs leverage genetics data? Use Case #2, Option A: Clinical x Genetics [Unsecret Agent] Mar 19, 2021
@karafecho karafecho changed the title Use Case #2, Option A: Clinical x Genetics [Unsecret Agent] Use Case #2, Option A: Clinical x Genetics [Genetics Provider] Mar 19, 2021
@karafecho
Copy link
Contributor Author

karafecho commented Mar 19, 2021

Note that this use case works for Exposures Provider and possibly other clinical KPs.

@flannick flannick mentioned this issue Mar 22, 2021
@karafecho karafecho changed the title Use Case #2, Option A: Clinical x Genetics [Genetics Provider] Clinical x Genetics Use Case [proposed by Genetics Provider] Apr 2, 2021
@karafecho karafecho changed the title Clinical x Genetics Use Case [proposed by Genetics Provider] Clinical Data ARS Use Case - Y3 Prioritization #1 - Clinical x Genetics Nov 15, 2021
@karafecho
Copy link
Contributor Author

Does this use case still seem relevant to folks?

@karafecho karafecho changed the title Clinical Data ARS Use Case - Y3 Prioritization #1 - Clinical x Genetics Clinical Data ARS Use Case - Y3 Priority #1 - Clinical x Genetics Nov 16, 2021
@karafecho karafecho changed the title Clinical Data ARS Use Case - Y3 Priority #1 - Clinical x Genetics Clinical Data ARS Use Case - Y3 Prioritization #1 - Clinical x Genetics Nov 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants