Maintaining calcium levels within a narrow normal range is of critical importance for numerous different cellular functions. One of the most important regulators of blood calcium levels is parathyroid hormone (PTH), which mediates its actions through the PTH/PTHrP receptor, a Gαs-coupled receptor. Few inherited disorders are characterized by diminished blood calcium levels and elevated blood phosphate levels; some of these disorders are caused by too little PTH synthesis and/or secretion (hypoparathyroidism, HP), while others are caused by resistance towards PTH (pseudohypoparathyroidism, PHP). Only few of the inherited forms of HP (<10%) have been defined at the molecular level. In contrast, genetic mutations have been identified for several inherited forms of PHP. For example, PHP type Ia (PHP-Ia) is caused by maternally inherited mutations in those GNAS exons that encode Gαs, while autosomal dominant PHP type Ib (AD-PHP-Ib) is caused by maternal inherited deletions within or up-stream of GNAS, which are associated with abnormal GNAS methylation. However, a large number of patients with PTH-resistance and thus hypocalcemia show GNAS methylation changes, but their underlying genetic defects have not yet been defined at the DNA level. These "sporadic" patients may be affected by an autosomal recessive form of PHP-Ib (AR-PHP-Ib), which is most likely not linked to the GNAS locus. In our studies, we propose to search through exome sequence analyses for novel genetic mutations responsible for novel autosomal dominant forms of HP that are not caused by mutations in the known disease-causing genes; some of these families are large enough to perform genetic linkage studies. We furthermore propose to search for the genetic mutation(s) responsible for the autosomal recessive variant of PHP-Ib through the analysis of whole exome sequences; for these studies we focus particularly on patients, whose parents are likely to be consanguineous. The proposed efforts are expected to lead to the identification of novel genes that are involved in parathyroid development and function (HP) and genes that are involved in the establishment or maintenance of GNAS methylation (AR-PHP-Ib).
One of the great challenges of therapeutic oncology is determining who might achieve survival benefit from a particular therapy. Circulating tumor DNA (ctDNA) provides real-time assessments of patient prognosis and response to treatment using a simple blood draw. While ctDNA positivity is established as a poor prognostic factor, studies on longitudinal ctDNA dynamics have been small and non-randomized, with ctDNA assessments done at disparate time points. To address this, we performed high-sensitivity longitudinal ctDNA testing in 466 patients across 5 time points (1,954 samples total) in a randomized phase III study comparing different chemotherapy-immunotherapy combinations. We leverage machine learning to jointly model multiple ctDNA metrics to predict overall survival in a training/testing framework. _ . Treatment initiation correlated with reductions in ctDNA levels, and training of our machine learning model suggests that assessment of ctDNA dynamics at C3D1 (cycle 3 day 1) of chemo-IO treatment may be optimal to predict OS. The model performs well in the hold-back test data, enabling stratification of patients with Stable Disease (SD) into high-risk vs low-intermediate-risk (HR = 3.2 [2.0-5.3], p <0.001; median 7.1 versus 22.3 months respectively); similarly, the model stratifies patients with a Partial Response (PR) (HR =3.3 [1.7-6.4], p <0.001; median 8.8 versus 28.6 months). Importantly, the model validates well in an external cohort of patients in a different treatment setting and assayed with a different ctDNA technology, in which model predictions similarly identified high-risk patients (OS HR=3.73 [1.83-7.60], logrank p=0.00012). Simulations of clinical trial scenarios employing our ctDNA model further suggest that early ctDNA testing outperforms early radiographic imaging for predicting trial outcomes (increasing the rate of ‘True Go’ decisions by 5.2 - 22.8% depending on the drug combination). Overall, we show that measuring ctDNA dynamics during the course of therapy dramatically improves patient risk stratification, and may provide a means to differentiate between competing therapies at an early time point during clinical trials.
Metadata Distribution Welcome to the realm of Metadata Distribution within the EGA ecosystem! Our Metadata REST API empowers you to effortlessly retrieve metadata from the expansive landscape of EGA. By utilising this API, you gain access to publicly available insights across various EGA domains, including studies, samples, experiments, runs, analyses, policies, DACs, and datasets. Furthermore, this API facilitates cross-referencing of objects, enabling you to gather, for example, all the datasets associated with a specific DAC, seamlessly. In addition, we have added the ability to query private data using the metadata API. If you possess the necessary permissions, you can access behind-the-login private data for a specified list of datasets. Metadata Distribution Index Identifiers Dataset Mappings Website Download Metadata API - Private Identifiers At the core of EGA's organisational structure are unique accessions that serve as essential tags for our diverse objects. Here's a quick overview of the accessions and their corresponding object types: EGA Accession ID EGA Object description EGAS EGA Study Accession ID EGAC EGA DAC Accession ID EGAP EGA Policy Accession ID EGAN EGA Sample Accession ID EGAR EGA Run Accession ID EGAX EGA Experiment ID EGAZ EGA Analysis Accession ID EGAD EGA Dataset Accession ID EGAB EGA Submission ID EGAF EGA File Unique Accession ID For further information check our metadata schema documentation. Dataset Mappings For authorised datasets, comprehensive mappings reveal meaningful connections: Sample_file: This file presents information about the linkage between samples and files available in the dataset. Study_experiment_run_sample: This file presents information about the linkage between studies, experiments, runs, and samples within the dataset. Study_analysis_sample: This file presents information about the linkage between studies, analyses, and samples contained within the dataset. Run_sample: This file presents information about the linkage between runs and samples within the dataset. Analysis_sample: This file presents information about the linkage between analyses and samples within the dataset. An empty file indicates the absence of corresponding information. Website Download Our website serves as your gateway to downloading metadata. Simply navigate to the dataset page, and you'll find a blue Metadata button. Once authenticated, you can click this button for authorised datasets. If you lack permissions for a particular dataset, request access by clicking the 'Request Access' button. For authorised datasets, choose your preferred metadata format: CSV, TSV, or JSON. Metadata API - Private Leverage the power of programmatic metadata downloads! Start by authenticating yourself with your credentials to obtain an access token. With this token, programmatically query private information. Queries mirror the structure of the Public Metadata API. However, behind the login, you can delve into specific mapping information (as mentioned above in dataset mappings) alongside object-level exploration. Authentication An active session is required to work with the API. Each time you log in with your credentials a new session is started, which is identified by an access_token. Below an example on how to obtain one using curl: curl https://idp.ega-archive.org/realms/EGA/protocol/openid-connect/token \ -d 'client_id=metadata-api' \ -d 'username=...' \ --data-urlencode 'password=...' \ -d 'grant_type=password' All responses from the API are in JSON format. A successful response should include a new token to be used for the session: {"access_token":"eyJhbGciOiJSUzI1NiIsInR5cCIgOiA...TNw", "expires_in":300, "refresh_expires_in":1800, "refresh_token":"eyJhbGciOiJIUzI1NiIsInR5cCIgOiA...pTX10", "token_type":"Bearer", ... } Save the access_token value and include it in the API call headers. Example query usage Below you can find some example of queries available behing authentication and authorisation. Querying study-experiment-run-sample mappings: curl https://metadata.ega-archive.org/datasets/{datasetID}/mappings/study_experiment_run_sample \ -H 'Authorization: Bearer access_token' Querying run-sample mappings: curl https://metadata.ega-archive.org/datasets/{datasetID}/mappings/run_sample \ -H 'Authorization: Bearer access_token' Querying study-analysis-sample mappings: curl https://metadata.ega-archive.org/datasets/{datasetID}/mappings/study_analysis_sample \ -H 'Authorization: Bearer access_token' Querying analysis-sample mappings: curl https://metadata.ega-archive.org/datasets/{datasetID}/mappings/analysis_sample \ -H 'Authorization: Bearer access_token' Querying sample-file mappings: curl https://metadata.ega-archive.org/datasets/{datasetID}/mappings/sample_file \ -H 'Authorization: Bearer access_token' You can get a different output format by adding one of these options to the curl command: -H 'Accept: text/tsv' -H 'Accept: application/json' -H 'Accept: text/csv' For more detailed information, refer to the Metadata API Specification.
RNA-SEQ data from 3 recurrent and 1 ovarian primary Granulosa Cell Tumour samples
