Search Results - EGA European Genome-Phenome Archive

Spatial whole exome sequencing of metastatic melanoma

We performed whole exome sequencing of 8 samples derived from a patient with metastatic melanoma. These represent six different regions of a metastatic melanoma biopsy that was treated with anti-PD-1 inhibitor, one pre-treatment biopsy that was treatment naive and one post-PD-1 inhibitor treated lesion. Exome sequencing data was generated using methods as previously described, including library preparation using the Agilent SureSelect XT Target Enrichment protocol (#5190-8646) prior to sequencing on an Illumina HiSeq 2000/2500 v3 system using 76bp paired-end reads. Raw sequencing data was then processed using Saturn V, the next generation sequencing data processing and analysis pipeline developed by the Department of Genomic Medicine at the UT MD Anderson Cancer Center.

Dataset EGAD00001005819

Genome-Wide Association Study of HCC in Non-Asian USA Population

This GWAS of HCC relied on existing biological and data resources from 7 USA sites and one Canadian site which allows for the integration of genetic and environmental data. Total of 2199 case patients and 1103 non cancer controls were genotyped. Case patients are defined as patients with pathological or radiological diagnosis of HCC with and without chronic hepatitis C virus infection. Study was restricted to Caucasian population without prior infection with chronic HBV infection. All DNA samples were extracted from peripheral blood. Study population of the participated sites are: Site-1: University of Texas MD Anderson Cancer Center A hospital based-case-control study was initiated at UT MD Anderson Cancer Center in 2000 and approved by the Institutional Review Board of The University of Texas M. D. Anderson Cancer Center. Study design was previously described in detailed (1-3). Written informed consent for an interview and for a biological sample was obtained from each participant. At time of diagnosis prior to treatment exposure. Case patients were recruited from the population of patients with newly diagnosed HCC who were evaluated and treated at the institution's gastrointestinal medical and surgical oncology outpatient clinics. Inclusion criteria were as follows: a pathologically confirmed diagnosis of HCC, U.S. residency, and the ability to communicate in English. Patients with concurrent or past history of other types of cancers were excluded. Control subjects were healthy spouses of patients with cancers other than liver, gastrointestinal, lung, or head and neck (smoking-related cancers) undergoing treatment at our institution. Eligibility criteria for control subjects were the same as those for patients, except that control subjects could not have ever had cancer. A short, structured questionnaire was used to screen potential control subjects on the basis of eligibility criteria. Control subjects and patients were recruited simultaneously. Case patients and control subjects were interviewed by well-trained interviewers who followed a written protocol to guide ascertainment and reduce surveillance, interviewer, and recall bias. No proxy interviews were conducted. The interviewers used a structured and validated questionnaire to collect information about demographic characteristics and potential risk factors for HCC such as personal smoking history, alcohol use, medical history, occupational history, and family history of cancer. Blood samples from cases and controls were tested for HBV and HCV. HCV antibodies, hepatitis B surface antigen, and antibodies to hepatitis B core antigen were detected by use of a third-generation enzyme-linked immunosorbent assay (ELISA) (Abbott Laboratories, North Chicago, IL). Important clinical information were retrieved from patients' medical records. Total of 1188 case patients and 278 controls from MD Anderson study were genotyped. Site-2: Mayo Clinic Case patients and controls included in the study from Mayo clinic were recruited as part of Mayo International Hepatobiliary Neoplasia Register and Biorepository. Only USA patients and controls were participated. All cases and controls signed informed consent indicating their willingness to participate in genetic studies. Epidemiological and clinical data were collected from participants and retrieved from medical records. Total of 522 HCC case patients and 182 controls were genotyped in this study. Site-3: Toronto University Molecular Epidemiology of Hepatobiliary Tumors (HBT study, CAPCR 09-0289) is a hospital-based study that includes 1710 patients diagnosed with liver, bile duct or gallbladder adenocarcinoma (Hepatocellular carcinoma - HCC; cholangiocarcinoma - CCA; and gall bladder adenocarcinoma -GBCa) recruited at University Health Network (UHN) between 2009 and 2018. HBT study is a prospective study of cancer patients that collects self-reported demographic and epidemiological data, medical records/clinical information and blood samples for research purposes. Eligible patients recruited between 2009 and March 15 2016 were selected to participate in the Genome-Wide Association Study in Patients with Hepatocellular Carcinoma (GWAS in HCC, CAPCR 15-9943-CE), a sub-study of the HBT study. Eligible prospective patients recruited after March 15 2016 signed the Addendum to the HBT consent form and became eligible to participate in the GWAS in HCC study. Total of 271 cases and 21 controls were genotyped from Toronto University Site-4: University of Pittsburgh The design of the study has been described previously (4-6). Briefly, this population-based study enrolled 120 HCC patients and 230 matched controls from black, Hispanic, and non-Hispanic white residents of Los Angeles County who were between 18 and 74 years of age at diagnosis from January 1995 through December 2001. HCC Cases were identified through the Los Angeles County Cancer Surveillance Program. We sought to recruit up to two control subjects per case from the neighborhoods where HCC patients resided at the time of diagnosis, who were matched to the index case by sex, age (within 5 years), and race (Hispanic white, non-Hispanic white, black). Blood samples (plasma and buffy coat), medical and lifestyle factors were collected from all consenting participants. Total of 65 cases and 60 controls were genotyped in this study Site-5: South Western Dallas Under IRB approval, HCC Cases and controls were prospectively collected since 2015 from the outpatient Liver clinics from Parkland Health and Hospital System and UT Southwestern Medical Center, two large health systems in Dallas TX. A Total of 31 cases and 29 controls were genotyped from site 5. Site-6: Columbia University HCC patients from Columbia are those recruited as part of the Herbert Irving Comprehensive Cancer Center Database Shared Resource which seeks to recruit all cancer patients for potential future studies. The PI is Dr. Katherine Crew AAAL5871. This resource collects sociodemographic, lifestyle and clinical data on patients as well as a blood sample. Those who indicated on their consent form that they would participate in genetic studies were included. Total of 79 case patients with HCC were genotyped from Columbia University. Site-7: University of Michigan The study population included from University of Michigan were included from a prospective study of with chronic HCV infection recruited in Ann Arbor Patients who had under- gone liver transplantation, known coinfection with HIV, life expectancy <12 months due to extra-hepatic illnesses, or were receiving HCV treatment at enrolment, were excluded. Protocol, surveys, and data forms were developed where each enrolled patient completed the same questionnaire All patients provided written informed consent before enrolment in the study. The study was approved by the institutional review board or ethics committee at the University of Michigan. Detailed study description was previously published (7). Total of 44 cases and 347 controls were genotyped Site-8: Veteran Administration Medical Center in Houston This research including written informed consent form was jointly approved by Institutional Review Boards for the Baylor College of Medicine and the Michael E. DeBakey VA Medical Center in Houston, Texas. Study details have been previously published (8). Briefly, we prospectively recruited consecutive HCV-infected veterans prior to their previously scheduled HCV clinic visit at a large tertiary care VA medical center between May 1, 2009 and December 31, 2012. Patients completed a research assistant (RA) administered survey interrogating medical and risk factor history including lifetime alcohol use, had anthropometric measurements taken, and completed a fasting venipuncture for performance of the FibroSure-ActiTest as a measure of hepatic pathology. We restricted our current analysis to individuals who were: (1) White male veterans between 18 and 70 years; (2) had no history of HCC, liver transplant, decompensated liver disease including ascites, dementia, or psychosis; (3) were serologically-confirmed to have chronic HCV and to be negative for both HIV and active HBV infection; (4) were not currently receiving anti-HCV pharmacotherapy; and (5) had FibroSURE testing shown F3/F4 fibrosis consistent with cirrhosis.

Study phs001744

WGS sequencing of an ES tumor sample

This Datasets contains whole genome sequencing data of one ES tumor sample. Sequencing was performed on Illumina NovaSeq 6000. The sequencing was paired in bulk.

Dataset EGAD00001015607

miRNA seq data of 43 cases out of dataset EGAD00001000650 (+ one read_me file)

miRNA seq data of 43 cases out of dataset EGAD00001000650 (MMML)

Dataset EGAD00001001619

What is a DAC?

What is a DAC? Given the complexity, scale, and diversity of global submitters and studies, the EGA operates a distributed data access model in which requests are made to the data controller, not to the EGA. The European Commission defines a data controller, in the General Data Protection Regulation (GDPR), as the person that determines the purposes for which and the means by which personal data is processed. A Data Access Committees, commonly referred to as DACs, comprise on or more individuals (or data controllers) that review data access requests and make decisions on who can access personally identifiable genetic, phenotypic, and clinical data deposited at the EGA. Therefore, the members of a DAC should be individuals who have the authority to approve data access requests. The animation describes how you can authorise access to your sensitive data with the help of Data Access Committee and Authorisation tool. Acknowledgement to CSC - IT Center for Finland, Elixir Finland, Elixir Europe. Frequently Asked Questions How can I create a Data Access Committee? How can I create a Data Access Committee? The members of a DAC can come from different areas of expertise, such as data management, data analysis, information technology, legal and compliance, subject matter experts, privacy and security, and representatives from the organisations or individuals that provide data to the DAC. The specific members of a DAC can vary depending on the needs of the organisation and the type of data being managed. The EGA strongly suggests checking with your organisation to align with its regulations How should a DAC be named? The chosen name must be informative to the applicant. For example, internal identifiers, such as grant numbers, should not be used. Individual PI names should also not be used. DAC's are often named after the organisation or department of the data source. Browse the full list of DAC names currently in the EGA. How can I become an EGA DAC contact? To register a DAC at the EGA you must create first as an EGA user. Once your EGA user has been approved by the Helpdesk team, you will be able to log in to the DAC Portal. How can I register a DAC? To register a DAC, follow the DAC Portal instructions. You will be required to provide a DAC name, name of the individual(s) that make up your DAC and contact details for your DAC including your Institutional email(s). Wherever possible, the DAC should make sure that all points of contact are readily available and able to answer any initial data requests/queries in < 2 weeks. Once your DAC is registered, you will have to wait upon the validation from our Helpdesk team. As soon as all the validations have been completed, your DAC will be activated. Alternatively, you can also establish a DAC at the EGA during a programmatic submission through Webin API. Which are the possible roles of a DAC contact? There are two possible roles for DAC contacts: member and admin. An admin has additional privileges compared to a member: An “admin” can manage data requests, create and edit policies, edit the content of the DAC, add or remove contacts, and decide the role of each contact. A “member” can manage data requests and create policies. However, a member does not have permission to modify DAC details, edit information from policies where they are not admins, or add/remove contacts. There is no limit to the number of admins in a DAC, and each admin is responsible for deciding who should have editing privileges. This allows for a more decentralised and democratic approach to managing the DAC. How can I modify the information of a DAC? To modify a DAC, follow the instructions here. Keep in mind that only DAC contact with an admin role can modify the information of a DAC. If your DAC was registered before the lauch of the DAC Portal, and its ID is EGAC0 (not EGAC5), you must use the programmatic submission to modify it. Please, do not hesitate to contact our Helpdesk team if you need help with this! To prevent potential data breaches and ensure adherence to GDPR regulations, it is essential that the European Genome-Phenome Archive (EGA) is informed via the Helpdesk team of any changes to the Data Access Committee (DAC). This should be done in addition to any changes being made on the DAC portal. Data Controllers (as per the definition in the DPA) are also responsible for notifying the previous DAC of any modifications. Without proper notification, changes might not be automatically updated in our system, leading to the risk of incorrect permissions being applied and potential data access issues. Therefore, it is imperative that all Data Controllers follow this protocol to maintain data integrity and security. What’s the link between DAC, policy and dataset? A dataset is linked to one single policy. At the same time, one policy has a one to one relationship with a DAC. In this example, you can see that in this dataset page, we are only showing the information of one DAC (1 dataset - 1 DAC). However, the ratio of objects does not work the same in the other direction. One DAC can own multiple policy objects. And each policy object can be reused in several datasets. Thus, one DAC can manage one or more datasets. In this example, you can see that in this DAC page, we are showing all the datasets that are managed by one DAC (1 DAC - >400 datasets). EGA Data Access Committee Best Practices Which are the EGA DAC best practices? Refer to DAC Best Practices What happens if a DAC member changes institutions? EGA is committed to the protection and ownership of the data stored in our systems. We respect the institution's ownership of the data, and as such, if a DAC member changes institutions, the ownership of the data will not be transferred to the new institution. Therefore, before changing institutions, we request that the DAC contact add a new member who will replace them once they no longer work at the institution. This ensures that the data remains protected and is accessible to authorised personnel at the institution. To prevent potential data breaches and ensure adherence to GDPR regulations, it is essential that the European Genome-Phenome Archive (EGA) is informed via the Helpdesk team of any changes to the Data Access Committee (DAC). This should be done in addition to any changes being made on the DAC portal. Data Controllers (as per the definition in the DPA) are also responsible for notifying the previous DAC of any modifications. Without proper notification, changes might not be automatically updated in our system, leading to the risk of incorrect permissions being applied and potential data access issues. Therefore, it is imperative that all Data Controllers follow this protocol to maintain data integrity and security. What happens if EGA detects an unresponsive DAC? EGA defines an unresponsive DAC as a DAC with one or more contacts who do not respond to data access requests. EGA has procedures in place to identify these types of DACs, escalate the issue, and attempt to reassign the DAC to a responsive contact. This is a crucial step in ensuring that data can be accessed and utilised by researchers. If EGA identifies an unresponsive DAC, the organisation will first try to resolve the issue by escalating it to the appropriate parties. This may involve attempting to reassign the DAC to a more responsive contact. Unfortunately, in situations where we cannot reassign the DAC, the dataset will be withdrawn from the public website and the files will be removed from our system. If an EGA ID is referenced in a publication, the EGA will take extra steps to ensure that the public is made aware of the data's unavailability. I don't want to receive an email notification for pending requests. How can I do that? If you are an EGA DAC with pending requests, you will always receive emails for new data access requests. However, the EGA understands that a request resolution can take some time, for this reason, if you add a comment (make sure you save it by clicking the APPLY button!) we will filter those requests at the time of sending the notification! How can I manage data access requests? What documentation does the DAC need to provide? Each dataset that is submitted to the EGA must be linked to a policy object. The policy is a Data Access Agreement (DAA), which defines the terms and conditions of using the dataset, such as how the data files should be stored once downloaded or details of publication embargoes that should be observed by the approved user. As part of the Data Access Agreement, information regarding the application can be captured to help inform the DAC when making its decision. For example, requestors could be asked to provide a proposed title for their research and a proposal of how the data will be used. By asking for provision of such information the DAC can be assured that the requestor fully understands any consents associated with the data. It is important that accounts created at the EGA, are created solely for those individuals that will be downloading the data from the EGA. As part of the data access request, we strongly encourage you to identify individuals that will need an account at the EGA in order to prevent sharing of login details, which is strictly prohibited under EGA user account policy. Such information can easily be captured in the DAA. NOTICE The data access agreement template below is provided for guidance only and should be adapted as you see fit to suit your own purpose. In the interest of promoting data sharing, we suggest that if an agreement cannot be met around clause 19 in this example that both parties should agree to remain silent, and that the clause should be removed from the agreement. Example DAA How can the DAC provide the DAA? The DAC should provide their own DAA when registering a policy. Data requestors will download this document and should fill it in and send it back to the DAC. Data access decisions should be based on such documentation. The DAA can be downloaded through the request data webpage. Once it has been filled in, the signed copy of the DAA can be uploaded back to the request data webpage and sent to the DAC for review. How can I grant access to the data? Once you receive a data access request, you can login to the DAC Portal. In this portal you will see all your pending requests and will be able to grant or decline access to the requestors. I am a member of the Data Access Committee. Could I approve somebody else to deal with the requests on my behalf? If you want to delegate data access decisions to someone else, make sure that the individual's account is officially registered as a member of the DAC. Remember that a DAC contact with an "admin" role can always add new members to an existing DAC, remove members, and modify contact details through the DAC Portal. Can I automatise the process of managing data access requests? The answer is yes! You can use a programmatic approach using our DAC API! Check out the DAC API specification! Data Breach What should a DAC do if they suspect a breach? If a DAC suspects a data breach of one or more of their datasets, they should immediately contact the EGA Helpdesk team at this link. The DAC must provide the following information when contacting the EGA Helpdesk team: A list of affected datasets An estimated date of the data breach (or interval of dates) A list of unauthorised users who accessed the data (if available). Otherwise, they can provide a list of authorised users for the affected datasets Any observations they would like to raise to the EGA team Once the DAC has contacted the EGA team, we will respond within 48 hours (please allow some leeway during peak times) and activate our data breach protocol. What can I expect from the EGA if they detect a breach? Once the EGA determines that a security incident has occurred, we will notify all DAC members that a data breach has been detected, and take steps to contain the incident. Containment approaches may include: Revoking a data provider's access to the EGA resources, such as by changing passwords. Removing affected EGA datasets from distribution, such as by withdrawing a dataset. Disabling certain functions or services, such as the EGA ingestion pipeline. Shutting down the system or disconnecting it from the network. After the incident has been contained, the EGA will determine whether it is necessary to eradicate components related to the incident. Finally, the EGA will enable recovery of the service to normal operation and confirm that all services are functioning normally.

Documentation access/data-access-committee/what-is-dac

WES_dataset1

Fourteen MEITLs and one EATL previously had been sequenced using the SureSelectXT Target Enrichment System (Agilent Technologies, Santa Clara, CA, USA).

Dataset EGAD50000001620

PBMCs of HCC Patients treated with anti-PD1 ICB

10 samples (one baseline, 9 on-treatment). Fastq files containing 5'GEx data, prepared using 10x Genomics pipeline, sequenced on Illumina HiSeq4000.

Dataset EGAD00001006645

Identification of Recurrent SMO and BRAF Mutations in Ameloblastomas

RNA-seq data from two cases of ameloblastoma was analyzed for candidate gene fusions and point mutations. Recurrent point mutations identified in the RNA-seq data, as well as mutations identified with limited panel targeted deep sequencing, were validated as somatic. Expanding to a larger cohort of 28, one of two activating mutations was found in 80% of cases. No recurrent gene fusions events were identified.

Study phs000739

Large Scale Meta-analysis Characterizes Genetic Architecture for Common Psoriasis-associated Variants

The genotypes obtained from the Affymetrix Biobank Plus array constituted one of eight Caucasian datasets used in a large genome-wide meta-analysis of the association of psoriasis cases versus unaffected controls. With a combined effective sample size of > 39,000 individuals, this study identified 16 new psoriasis loci achieving genome-wide significance, increasing the total number of identified psoriasis loci for European-ancestry populations to 63.

Study phs001306

Demographic History and Local Adaptation in Asian Population

Due to harboring high genetic and cultural diversity of populations, Central Asia is one key area for understanding the recent evolutionary history of humans. In this project, our aims include: (1) to resequence genome sequences with high sequencing depth for Central Asian populations Balti; (2) to discern the genomic diversity, populations structure and demographic history of Balti; (3) to investigate the genetic mechanisms for local adaptations in Balti.

Study JGAS000238

1567 results for "Sweden+NDA+enforceability+one+party+signed"

in 13.67 milliseconds.