Search Results - EGA European Genome-Phenome Archive

Adaptive Therapy Exploits Fitness Deficits in Chemotherapy-Resistant Ovarian Cancer to Achieve Long-Term Tumor Control Open Access

Drug resistance results in poor outcomes for cancer patients. Adaptive therapy is a potential strategy to address drug resistance that exploits competitive interactions between sensitive and resistant subclones. Here, we showed that adapting carboplatin dose according to tumor response (adaptive therapy) significantly prolonged survival of murine ovarian cancer models compared to standard carboplatin dosing, without increasing mean daily drug dose or toxicity. Platinum resistant ovarian cancer cells exhibited diminished fitness when drug was absent in vitro and in vivo, which caused selective decline of resistant populations due to reduced proliferation and increased apoptosis. Conversely fitter, sensitive cells re-grew when drug was withdrawn. Using a bioinformatics pipeline that exploits copy number changes to quantify the emergence of treatment resistance, analysis of cell‐free DNA obtained longitudinally from ovarian cancer patients during treatment showed subclonal selection through therapy, and measurements of resistant population growth correlated strongly with disease burden. These preclinical findings pave the way for future clinical testing of personalized adaptive therapy regimens tailored to the evolution of carboplatin resistance in individual ovarian cancer patients.

Study EGAS50000001142

National Heart, Lung, and Blood Institute (NHLBI) Bench to Bassinet Program: The Pediatric Cardiac Genetics Consortium (PCGC) Study

Multi-center, prospective observational cohort study of individuals with congenital heart defects (CHD). Phenotypic data and source DNA derived from 10,000 probands, parents, and families of interest are being collected to investigate relationships between genetic factors and phenotypic and clinical outcomes in patients with CHD. Phenotype data will be stored at dbGaP, while molecular and sequence data will be stored at BioData Catalyst. The PCGC Cohort is utilized in the following dbGaP substudies. Please click on the following substudies below or in the "Substudies" section of this top-level study page phs001194 PCGC Cohort. phs000571 PCGC: whole exome sequences, whole genome sequences, targeted sequences, MIP sequences, and SNP array data phs001843 PCGC-CMG Collaboration: whole genome sequences The Gabriella Miller Kids First Pediatric Research Program (Kids First) subset of the PCGC project (phs001194) is now accessible through a separate dbGaP study accession: phs001138. To access this dataset, please submit a Data Access Request (DAR) for phs001138. Approval of this DAR will be expedited for approved users of phs001194. To learn about other Kids First datasets visit https://kidsfirstdrc.org/.NHLBI's TOPMed program has provided additional Whole Genome Sequencing for PCGC participants - that data is accessible through a separate dbGaP sudy accession: phs001735. Access to this data set should be requested through a Data Access Request (DAR) for phs001735.

Study phs001194

Indonesian Microbiome Ecology and Evolution v1 - Data Access Policy

This Data Access Policy sets forth the terms, conditions, and limitations governing access to and use of the raw sequencing data of samples in the Indonesian Microbiome Ecology and Evolution (IndoMEE) v1 dataset by individuals who are not part of the Data Producer. The IndoMEE v1 dataset comprises 126 human faecal samples collected across Indonesia between 2015 and 2021, that was collected to study patterns of human microbiome variation across Indonesia’s diverse geography and lifestyles.

Dac EGAC50000000587

Profiling RNA Translation in Pediatric Medulloblastoma

This study provides RNA-sequencing and ribosome profiling data for patient-derived cell lines and patient tissue samples for children with medulloblastoma. Ribosome profiling is a variant protocol of RNA-sequencing that directly sequences ribosome-bound RNA fragments only. Associated RNA-seq and Ribo-seq data obtained separately for some cancer cell lines can be found on the NCBI SRA as PRJNA957428. Samples were processed for poly-A mRNA sequencing using the Roche Kapa Kit. Ribosome profiling was performed as described in the manuscript referenced below (Hofman et al.) and based on the article by McGlincy et al., Methods (2017). Ribo-seq data were analyzed for sample quality using RiboseQC (Calviello, Nat Struct Mol Biol, 2020). These data were used to quantify P-sites of open reading frames. RNAseq and ribo-seq data were integrated and compared to determine translational efficiency values using TPM (Ribo-seq) over TPM (RNA-seq) as the metric. Ribo-seq data on 14 samples and RNAseq data on 21 samples derived from 16 fresh-frozen surgical samples for medulloblastoma and 5 autopsy samples are available through dbGaP. A second cohort of 4 medulloblastoma samples (RNAseq, Ribo-seq) related to this study can be found on the EGA at EGAS00001007426.

Study phs003446

Drug screening of patient-derived organoids from colorectal peritoneal metastases

Colorectal cancer (CRC) patients with peritoneal metastases (CRPM) have limited treatment options and the lowest CRC survival rates. We trialed the possibility of organoid directed precision treatment for CRPM patients. CRPM organoids (peritonoids) isolated from patients underwent next-generation sequencing and medium-throughput drug panel testing ex vivo to identify specific drug sensitivities for each patient. We measured the utility of such a service including: success of peritonoid generation, time to cultivate peritonoids, reproducibility of the medium-throughput drug testing, and documented changes to clinical therapy as a result of the testing. Peritonoids were successfully generated and validated from 68% (19/28) of patients undergoing standard care. Genomic and drug profiling was completed within 8 weeks and a formal report ranking drug sensitivities was provided to the medical oncology team upon failure of standard care treatment. This resulted in a treatment change for 2 patients, one of whom had a partial response despite previously progressing on multiple rounds of standard care chemotherapy. The barrier to implementing this technology in Australia is the need for drug access and funding for off-label indications. In conclusion, our approach is feasible, reproducible and can guide novel therapeutic choices in this poor prognosis cohort, where new treatment options are urgently needed. This platform is relevant to many solid organ malignancies.

Study phs002023

Whole_exome_sequencing_of_additional_thyroid_disease_cases

Whole-exome sequencing of a cohort of families (probands and affected/unaffected relatives) suffering from one of two rare thyroid disorders: congenital hypothyroidism (CH) and resistance to thyroid hormone (RTH).

Study EGAS00001001114

71 Whole-exome sequencing of Esophageal Squamous Cell Carcinoma on Chinese Patients

Esophageal Squamous Cell Carcinoma (ESCC) is one of the deadliest cancers worldwide. We performed 71 Whole-exome sequencing of Esophageal Squamous Cell Carcinoma on Chinese Patients.

Study EGAS00001001475

PyEGA3 download client

PyEGA3 Checks prior to download - Is the dataset available for download? Most datasets are available using the PyEGA3 Download client, except for specific legacy datasets. For these ones, refer to Live Outbox distribution, an alternative way to download these datasets.If the dataset you've been granted access to begins with the ID EGAD5XXXXXXX, please refer to the Live Outbox distribution. If the dataset you have been granted access to contains encrypted data (filename ending in .gpg), contact EGA Helpdesk for detailed information on how to download these files.General Information The PyEGA3 download client is available at its GitHub repository. In its README you will find a step by step guide on how to use it to download files you have been granted access to. PyEGA3 implements the GA4GH-compliant HTSGET protocol supporting requests over genomic ranges. This enables the download of specific regions of interest rather than the entire file. HTSGET is not possible for all the files held by EGA: if the dataset does not contain index files (e.g. filename ending in *.crai), then genomic range requests cannot be performed. The maximum number of connections allowed is 30. If more than 30 connections are used, the download client will encounter 500 errors. The recommended number of connections for maximum output is one. Check out our video tutorial! Frequently Asked Questions General questions How do I download the datasets to which I have been granted access? After setting up your EGA download account, you can proceed to download using the EGA download client – PyEGA3. The pyEGA3 download client is a python-based tool for viewing and downloading files from authorised EGA datasets. This download client is continuously being developed for more user-friendly download experiences. Can I download the dataset’s metadata via the download client? No, the download client cannot be used to download metadata. Registered EGA users can download metadata of an authorised dataset by logging into the EGA webpage and navigating to the dataset of choice. Approximately two thirds down the page you will find the option to download the metadata as a zip file. How do I download large datasets as quickly as possible? The main EGA download client is pyEGA3 download client, a python-based tool for viewing and downloading files from authorised EGA datasets.We could exceptionally consider the option of an Aspera download for users experiencing very slow download rates or facing particular issues.Contact the EGA Helpdesk for further information. Pre-requirement and Installation What are the major requirements for the PyEGA3 download client installation and usage? The PyEGA3 client is compatible with any OS with Python 3.6+ installed. The client requires a connection to the internet, sufficient space on the destination drive, and the EGA download account credentials. Where can I find the PyEGA3 download client installation and download instructions? We strongly recommend checking our video tutorial demonstrating the usage of PyEGA3 from installation to file download. More detailed information is available at PyEGA3 GitHub. What ports are required for the PyEGA3 download client to function? PyEGA3 makes HTTPS calls to the EGA Data API (https://ega.ebi.ac.uk:8443). This port 8443 must be reachable from the location where PyEGA3 is executed to avoid timeouts. PyEGA3 download client How to update the PyEGA3 download client to be on the latest version? Updating the client to the latest version can be achieved by running the following command: pip3 install pyega3 --upgrade I do not have an active EGA account. Can I test the download with the PyEGA3 download client? An EGA download test account (ega-test-data@ebi.ac.uk) has been created for troubleshooting and training purposes. The test account does not require an EGA username and password because it contains publicly accessible files from the 1000 Genomes Project. More information about the use of this account and log in details are available at pyEGA3. I lost my connection while the download was in progress. Does this mean that I have to download the file again from the start? The PyEGA3 download client supports automatic resumption of downloads. To enable quicker download speeds, the API breaks files into up to four segments and downloads them in parallel. With the resume feature, downloads will automatically resume if you encounter any errors or if the connection is interrupted. How can I improve the overall download speed of the PyEGA3 download client? Download speeds can be optimised using the --connections parameter which will parallelise download at the file level. If the --connections parameter is provided, all files >100Mb will be downloaded using the specified number of parallel connections. It is important to note that files are still downloaded sequentially, so using multiple connections does not mean downloading multiple files in parallel. The maximum number of connections allowed is 30. If more than 30 connections are used, the download client will encounter 500 errors. The recommended number of connections for maximum output is one. Why is my file taking a long time to be saved? Please note that when a file is being saved, it goes through two processes. First, the downloaded file "chunks" are pieced back together to reconstruct the original file. Secondly, PyEGA3 calculates the checksum of the file to confirm that the file was downloaded successfully. Larger files will take more time to reconstruct and validate the checksum. Why is the HTSGET protocol not working with my dataset of interest? PyEGA3 implements the GA4GH-compliant htsget protocol for supporting requests over genomic ranges. This exciting new feature means that for data files with accompanying index files (e.g. .crai for CRAM files) users can download specific regions of interest rather than the entire file, saving both time and storage space. Please note that in order for the genomic range requests to work for a BAM, CRAM or VCF file there must be an associated BAI, CRAI or TBI file, respectively. If the dataset does not contain these index files then genomic range requests cannot be performed. After download Do I need to decrypt data files downloaded through the pyEGA3 download client? Files are transferred over secure HTTPS connections and received unencrypted, thus there is no need for decryption after data download. What is the purpose of an MD5 file? After the download completes, file integrity is verified using checksums. The PyEGA3 download client automatically verifies each file’s unencrypted md5 after download to ensure that the file was downloaded correctly from the EGA. Errors Why do I get a “400 Client Error” while trying to access the download client? Ensure that your credentials are formatted correctly. Please contact the EGA Helpdesk if you are unsure about your account’s username (i.e. your email address). Why do I get a “500 Server Error”? It is important to note that files are still downloaded sequentially, so using multiple connections does not mean downloading multiple files in parallel. The maximum number of connections allowed is 30. If more than 30 connections are used, the download client will encounter 500 errors. The recommended number of connections for maximum output is one. Otherwise, 500 server errors are internal server errors from EGA’s end. Retry after some time and, if the 500 error persists: check our homepage or Twitter for any outage information or report it to EGA Helpdesk. Why do I get a “slice error”? This type of error occurs when one slice download was prematurely interrupted. Please re-start the same download. The download client will pick up any partial download and download any missing slices. Why do I get the error “Dataset' EGADXXXXXXXXXXX' is not in the list of your authorised datasets”? Please note that the data access was given to the email (username) provided to the Data Access Committee (DAC) in your official request. Therefore, you shall check that the account that you are using is the same one that you sent to the DAC. Why do I get “ERROR:root:Failed to obtain IP address”? This might mean that the connection ports are blocked. Check that the port 8443 is reachable.In case the port is reachable and the error persists, please try to modify the file pyega3.py on line 44 in the python module installation: Replace endpoint = 'https://ipinfo.io/json' with endpoint = 'https://api.myip.com' Why do I get the error “Invalid username, password or secret key - please check and retry”? Make sure that you are using the correct credentials (username and password) and there is no typo. Contact EGA Helpdesk if the problem persists.

Documentation access/download/files/pyega3

Submitter Portal

Submitter Portal The Submitter Portal does not support array submissions! Please refer to the array documentationAny new objects registered in the Submitter Portal will not be available for use in an array submission For further information please check our Submission FAQs, submission quickguide as well as submission terms! The metadata submission process can be difficult and time-consuming. For this reason, the EGA has developed the Submitter Portal, a tool that was created to offer a simplified and user-friendly method of registering metadata. Our portal provides features that are intended to make the input of metadata easier, ensuring that your data is registered correctly and effectively. Our page is divided into logical sections and includes a helpful video instruction to further assist you as you complete the submission process. With the Submitter Portal, you can rest assured that the submission of your data is in good hands. Submitter Portal Index Previous steps Access to Submitter Portal Start a Submission Take The Tour Tutorial Previous steps Create your EGA account To submit data, you first need to create your EGA user. Then, once your account has been verified by the Help Desk team, you will be able to request a submitter role and send the EGA Data Processing Agreement (DPA). In the case you already have an EGA account, or an ega-box (submission account), you can skip this step. Upload your files Please note that all your files must be encrypted using the Crypt4GH tool before upload them.As soon as you are assigned with a submitter role and added your public key to your profile, you will be able to connect to the EGA inbox and upload your files. Understand the EGA metadata schema It's crucial to comprehend the EGA metadata schema, a set of rules that specify how data is organised, described, and shared inside the EGA, in order to get the most out of this resource. Learn all about EGA metadata schema! Register your DAC and policy There are two objects in the EGA metadata schema that are registered in a separate portal. All DACs and policy objects are registered using the DAC Portal, a tool developed by EGA to help data controllers manage their data stored at the EGA. You can find relevant information in the DAC Portal Guide. Access to Submitter Portal 1. Request Submitter Role Once you have created your EGA user, request a Submitter Role and complete relevant information such as submission type and size. 2. Signature of the Data Processing Agreement The Data Processing Agreement (DPA) signed by CRG and EMBL-EBI (Joint Data Processors for the EGA) can be downloaded to the submitter for its signature. Further information related to the DPA can be in the Privacy Notice section. The DPA should be signed by a legal representative of the submitter with power of attorney/appointment duly authorised to sign contracts on behalf of the institution. The submitter will return a fully-executed copy of the DPA to us. Please note that due to the high volume of submissions to EGA the DPA is non-negotiable. Once you have completed all the information and attached the DPA signed, send your Submitter request and the EGA Helpdesk Team will validate it and send a confirmation to start submitting your metadata. Start a Submission The steps below will show you how to start a submission and are accompanied with a tutorial and the Take the tour of Submitter Portal. 1. Login Go to the Submitter Portal interface and log in using your EGA account credentials. 2. Create a submission The Submitter Portal interface will show you any already existing open submission. To start a new submission click on “Create a Submission”.In this phase you have the option to add any collaborator(s) as well as their permissions (“Read only” or “Read & Write”). If you want to invite all the collaborators from a previous submission, you can add them by selecting said submission.In the event that the submission has been closed, you will need to reopen it. To do this, you will need to modify one of the objects in the submission, for example, copy and paste the title. Once the submission is open, you can add a collaborator. Further information can be found in the Submission Tour 3. Create Study Click on add Study and complete the form with the relevant information. The fields with an asterisk (*) are mandatory. Further information can be found in the Submission Tour4. Create Sample Sample registration can be done either individually or in batch by using a template. Batch upload: download the template and complete it with information about the sequencing samples. Upload the samples.csv and the sample will be created.Add single sample: complete the mandatory fields with the metadata information of your sample. Further information can be found in the Submission Tour5. Create Experiment Register an experiment with information about the sequencing methods, protocols and machines. Experiments generate the connection between samples and study. Further information can be found in the Submission Tour6. Create Run Samples, experiments and files are linked through runs. To register a run, you will be asked to select the appropriate experiment and the file format. Run registration can be done either individually or in batch by using a template. Batch upload: download the template and complete it with the sample - file linkage. Upload the run.csv and the runs will register.As the INBOX is a directory, bear in mind to include the file path (/). Example: /filename.c4gh. Add single run: select the file format, sample and experiment from the drop box. For re-using submitted samples, please use the EGA accession ID (EGANXXX). Please note that files must be uploaded in your inbox before linking your files and samples. Further information can be found in the Submission Tour7. Create Analysis Analysis should be only used for BAM/BAI or CRAM/CRAI pair, VCF and phenotype linkage to samples. The analysis is an EGA specific metadata object that links samples to files. This object also stores some metadata about your experiments, such as the experiment type, genome reference, or the platform used. **If only BAM or CRAM alignment files are submitted but not the original unaligned FASTQ files, then please make sure that the BAM or CRAM files also contain the unaligned reads. This is critical to enable primary re-analysis and re-alignment of the dataset using new tools or future genome assemblies.** Start by selecting the samples to be linked to the file, and then populate the required attribute fields. Please be aware of the existence of mandatory fields that must be populated.When populating the chromosome field (mandatory), please select the chromosomes from the checkbox. Please take in consideration that EGA allows for the re-use of any registered metadata. Therefore, a previously registered study or samples can be referenced for the analysis in the current data submission.Further information can be found in the Submission Tour 8. Create Dataset Dataset contains the collection of runs/analysis data files subjected to controlled access by being associated with a Policy. Complete the mandatory fields such as title, description, type and policy. Please, take in consideration that DAC and Policy must be registered in advance in the DAC Portal. Similar to other metadata objects, you can re-use previous runs or analyses, using their EGA accessions IDs (runs - EGAR, analyses - EGAZ). Further information can be found in the Submission Tour 9. Finalise submission Once the files are ingested please delete them from your SFTP INBOX before finalising your submission. This will prevent the files from reappearing in your Submitter Portal Inbox. Once you have completed your submission, click on the Finalise button, and schedule an estimated release date. Afterwards, your submission will be sent to Helpdesk for approval. Please note that once the Helpdesk has approved your submission, you will receive the identifiers for your data. See the Frequently Asked Questions (FAQ) for more information. 10. Update closed submission If you want to append more file to a closed submission, you will need to re-open the submission where the dataset was registered. Find the Submission: go to the Submitter Portal Menu -> Datasets section and find the submission id (EGA0XXX). Reopen the submission where the dataset is located: to reopen a submission, you must edit any object within the submission. For example, you can copy and paste the title. Take The Tour The Submitter Portal Take The Tour is a visual guidance of all the steps described previously about how to start a submission. Tutorial In this tutorial we will show you how to use the Submitter Portal to register your metadata. Please note the video focuses on the run-based submission (for raw files - fastq - and aligned data - BAM/CRAM) and analysis-based submission (for your BAM/BAI pairs, variation -VCF - and phenotype files).

Documentation submission/metadata/submission/sequencing-phenotype/submitter-portal

Autosomal recessive

To define a genetic syndrome of combined immunodeficiency, severe autoimmunity, and developmental delay, 4 patients from two families who had similar syndromic features were studied. To identify disease-causing mutations, we performed whole exome sequencing for one patient and her healthy parent from Family 1 and also for one patient from Family 2. Disease segregated with novel autosomal recessive mutations in a single gene, tripeptidyl-peptidase II (TPP2) gene. The result defines a new human metabolic immunodeficiency.

Study phs000848

Genetic Landscape of Esophageal Squamous Cell Carcinoma Defined by Exome Sequencing on Chinese Patient Cohort and Cell Lines

Esophageal Squamous Cell Carcinoma (ESCC) is one of the deadliest cancers worldwide. To define the genetic landscape of ESCC, whole exome sequencing was performed on 113 pairs of tumor and normal DNA samples collected from Chinese individuals with treatment-naive primary ESCC, along with 8 cell lines, including 7 from KYSE series ESCC cell lines and one immortalized esophageal squamous epithelial cell line Het-1A.

Study EGAS00001000932

Acute Respiratory Distress Network (ARDSNet) Study 02 Late Steroid Rescue Study (LaSRS) (ARDSNet-LaSRS-BioLINCC)

Data Access NOTE: Please refer to the “Authorized Access” section below for information about how access to the data from this accession differs from many other dbGaP accessions. Biospecimens: Access to Biospecimens is through the NHLBI Biologic Specimen and Data Repository Information Coordinating Center (BioLINCC). Biospecimens from ARDSNet-LaSRS include BAL Slides, Bronchial Lavage, and Plasma. Please note that use of biospecimens in genetic research is subject to a tiered consent.Objectives: Since previous reports suggested that corticosteroids may improve survival, this project was developed as a multicenter, randomized controlled trial of corticosteroids in patients with persistent ARDS.Background: Persistent acute respiratory distress syndrome (ARDS) is characterized by excessive fibroproliferation, ongoing inflammation, prolonged mechanical ventilation, and a substantial risk of death.Participants: There were 180 participants.Conclusions: The results do not support the routine use of methylprednisolone for persistent ARDS despite the improvement in cardiopulmonary physiology. In addition, starting methylprednisolone therapy more than two weeks after the onset of ARDS may increase the risk of death. (NEJM April 20, 2006; Vol 354, No. 16, pp 1671-84).

Study phs003769

Genetics of Hypertension Associated Treatment (GenHAT) Study, Genomic Background of Blood Pressure Response to Treatment in African Americans

The GenHAT study is an ancillary pharmacogenomics study to the Antihypertensive and Lipid Lowering Treatment to Prevent Heart Attack Trial (ALLHAT). ALLHAT was a randomized, double-blind, multi-center trial that enrolled 42,418 participants ≥55 years of age with hypertension and at least one additional risk factor for cardiovascular disease (CVD). Participants were randomized to treatment with one of four primary antihypertensive drugs: chlorthalidone (thiazide-like diuretic), amlodipine (CCB), lisinopril (ACE-i), or doxazosin (alpha-adrenergic blocker) in a ratio of 1.7:1:1:1, respectively. Participants were followed for treatment response and CVD outcomes. The original GenHAT study (N=39,114) evaluated the association of candidate hypertensive genetic variants with CVD outcomes for participants consenting to genetic research. The current GWAS study focuses on a subset of African American GenHAT participants (n=6908).  

Study phs002716

Nyamasati study access committee

Dac EGAC00001001028

OMKar Study Data Access Committee

Dac EGAC00001003581

Integrative_Oncogenomics_of_multiple_myeloma

We used targeted capture and massively parallel sequencing of exomes of CD138 purified plasma cells and matched somatic DNA from 17 patients with Multiple Myeloma. For each patient, an early tumor sample (at diagnosis) and a late one (at relapse) were available. For few of them, an additional late sample (2nd progression) was present. In total, the study has 52 samples. 1044 variants were validated by 454 sequencing. The present study will validate an additional 4630 variants by targeted pull-down and sequencing. All 52 samples will be indexed and then will be pre-pooled in groups of 5 or 6. The sequence capture will use 10 reactions. All samples will then be pooled and go thorugh one lane of HiSeq.

Study EGAS00001000244

NICHD Genomic and Proteomic Network for Preterm Birth Research (GPN)

We performed genome-wide association studies (GWAS) to study the Spontaneous Preterm birth (SPTB). Maternal and neonatal DNA from 743 SPTB (20 to and less than 34 weeks), and 752 controls (39 to and less than 42 weeks) who fully consented for public research usage were collected from participants in several clinical centers in Alabama, Illinois, New York, North Carolina, Rhode Island, Texas, and Utah. Cases were 1:1-matched with controls according to race/ethnicity (White, Hispanics, African Americans, and Others), maternal age (<20, 20-29, 30-39, 40+), and parity (yes or no). To determine the case-control status for each participant, a Gestational Age (GA) was determined. DNA samples were taken from blood or saliva if blood was not available. Automated DNA extractions were performed on the Qiagen M48 robot, and samples were organized in 96-well plates with barcoding and sample tracking systems. Subsequent manipulations were performed on the Biomek FX liquid handling workstation with 96-channel pipetting. DNA quantitation was performed by dye-based assay on a Molecular Devices SpectraMax Plus plate reader. Samples were genotyped using Affymetrix Genome-Wide Human SNP Array 6.0. This work was conducted at the Microarray Facility at the University of Pennsylvania. Patient data were collected through chart reviews and patient interviews, which included Demographic information (parental age, race, ethnicity, etc.); Medical history (pre-pregnancy weight, height, medications, STD history, medical conditions, etc.); Social history (marital status, years of education, alcohol use and tobacco use); Obstetrical history including outcome of all prior pregnancies and dates of termination; History of preterm labor or premature rupture of membranes symptoms, evaluation or hospitalization for those symptoms in current pregnancy; Medications taken during current pregnancy; History of cervical evaluation (manually or ultrasonographically) or fetal fibronectin measurements; Pregnancy complications; Labor (type, indications, membrane status, and induction method); Delivery type and indications for cesarean section; Neonatal outcome (sex, weight, length, Apgar score, neonatal complications, admission to intensive care unit, etc.); and Maternal family history of SPTB.

Study phs000714

Lipodystrophy study Data Access Committee

Dac EGAC00001000997

PIVUS Study Data Access Commitee

Dac EGAC00001001170

Study EGAS00001005054 Data Access Committee

Dac EGAC00001002066

MBL2 study data access committee

Dac EGAC00001002678

ORIENT study Data Access Commitee

Dac EGAC00001002940

Rheumatoid Arthritis Finger Stick RNA Sequence Data

This is a longitudinal study of 355 blood samples collected weekly from 5 patients with Rheumatoid Arthritis with varying disease activity over the course of one to five years. Blood samples were self collected from finger sticks and mailed from home. RNA was extracted, purified and sequenced.

Study phs003179

Single nucleus RNA sequencing of squamous cell carcinoma arising from mature teratoma of the ovary

Squamous cell carcinoma arising from mature teratoma is one of the rare ovarian cancers. Therefore, the detailed molecular background of this disease has not been elucidated. The purpose of this study is to investigate the single-cell transcriptional landscape of this disease.

Study JGAS000521

Papua New Guinean Genome Diversity Project

Papua New Guinean populations have one of the highest genetic diversity of the world. Our dataset provides genomic data covering most of the Papua New Guinean territory (n=58).

Study EGAS00001005393

14456 results for "PLOS+ONE+Pennsylvania+German+ACS+language+code+pdc+open+access+study"

in 17.63 milliseconds.