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

in 14.43 milliseconds.

• CTSP: Clinical Trial Sequencing Project

  For the Clinical Trials Sequencing Project (CTSP), National Cancer Institute (NCI) will utilize whole genome sequencing and/or whole exome sequencing in conjunction with transcriptome sequencing to try to identify recurrent genetic alterations (mutations, deletions, amplifications, rearrangements) and/or gene expression signatures that would be important to the hypothesis(es) submitted by the investigators. The samples will be processed and submitted for genomic characterization using pipelines and procedures established within The Cancer Genome Analysis (TCGA) project. Data analysis will be performed as a collaboration between the National Clinical Trials Network (NCTN) Group and its investigators submitting the proposal. The investigators at the NCI-sponsored Genomic Data Analysis Center (GDAC) will characterize the samples. The NCTN Group will be responsible for providing the clinical data needed for the proposal to the open clinical system maintained by NCI CCG's Biospecimen Core Resource (BCR) at Nationwide Children's Hospital in Columbus, Ohio. The project team (Network Group/investigators and GDAC) will analyze the data together. Additionally, clinical and genomic data related to the analyses will also need to be registered by NCI and will be made available to qualified researchers via a controlled-access database (e.g., dbGaP) upon publication of the primary analysis described in the study proposal. A substudy description and its molecular data information are provided under its own page: phs001184 CTSP Diffuse Large B-Cell Lymphoma (DLBCL) CALGB 50303

  Study phs001175

• Germline variants in patients with rare cancers and their implications for precision cancer medicine: experiences from the Multicenter MASTER Trial by the German Cancer Consortium (HIPO_021)

  The era of precision oncology entails an increasing amount of molecular data from tumor sequencing in research and diagnostics. In this setting, germline variant analysis may add clinical benefits for patients and family members. In this study, we evaluated germline variants from genome/exome matched tumor-blood sequencing in 1.485 advanced cancer patients within a prospective observational study carried out by the German Cancer Consortium. Included patients had cancers of rare entities (79.2%) or were under the age of 51 at first diagnosis (76.6%). Ten percent of the patients harbored pathogenic germline variants in 35 tumor predisposition genes with autosomal-dominant inheritance such as BRCA1, BRCA2, TP53, RB1, CHEK2, ATM, PALB2, SDHB etc., while 4.6% of the patients were carriers of pathogenic germline variants in 18 genes with autosomal-recessive inheritance of tumor predisposition. Based on pathogenic germline variants, 14% of the patients received genetic counselling recommendations in the molecular tumor board report. Forty five percent of pathogenic germline variants supported a molecular treatment recommendation, which was implemented for 28 patients. Furthermore, we compared our approach and results to previous studies, broadening the insight into pan cancer germline findings but also revealing differences between studies on various levels, such as cohort demographics, tumor entities, gene nominations, variant detection and variant interpretation. Our data support the importance of germline variant interpretation in precision oncology studies for patients and their families, if applicable. However, guidelines for evaluation and reporting of germline variants in the context of genetic tumor profiling need to be established and further research on the relevance of germline mutations as biomarkers for treatment recommendations is needed.

  Study EGAS00001005537

• Study of Controlled Human Malaria Infections to Evaluate Protection After Intravenous or Intramuscular Administration of PfSPZ Vaccine in Malaria-Naive Adults

  The study was performed to evaluate whole-blood transcriptomic profiles via RNA-seq before, during, and after immunization with the PfSPZ Vaccine in malaria-naïve, health adults enrolled in VRC 314 (NCT02015091). VRC 314 was designed as an open-label evaluation of the safety, tolerability, immunogenicity, and protective efficacy of the PfSPZ Vaccine. This study was designed to substantiate the initial results with the IV vaccination route for protection against CHMI that was observed in VRC 312 (NCT01441167). Based on the potential importance of dose and schedule in optimizing sustained immunity with this vaccine, an increase in PfSPZ IV dosage on schedules of 3 to 5 vaccinations was evaluated for protection against CHMI conducted early (about 3 weeks) and late (about 24 weeks) after completion of vaccinations. To assess if a higher dose given by another route confers protection, one group received PfSPZ IM, with half of the amount administered in each arm on a schedule with 4 vaccination. The primary objectives of the study were related to the safety and tolerability of vaccinations by the IV and IM routes of administration and protection against Plasmodium falciparum (Pf) challenge performed via a well-established CHMI procedure early (2-4 weeks) after completing schedules of 3 to 5 vaccinations. The secondary objective was related to the durability of protection at 20-26 weeks after the last vaccination, and exploratory objectives were related to the immunogenicity of the PfSPZ Vaccine and identifying potential immune correlates of protection. To further determine potential molecular correlates of immunogenicity and/or protection, RNA-seq was performed on whole blood collected from subjects in all dose groups at time points before, during, and after immunization.

  Study phs002423

• A Phase I Study with a Personalized Neoantigen Cancer Vaccine in Melanoma

  Effective anti-tumor immunity in humans has been associated with presence of T cells targeting neoantigens that arise from non-silent tumor-specific mutations. Here we conducted whole-exome sequencing of tumor and normal cells from individual patients to identify mutations. We assessed the expression of mutated alleles by RNA-sequencing of tumor. We demonstrated the feasibility, safety and immunogenicity of a vaccine that targets up to 20 personal neoantigens predicted to be presented by the autologous patient tumor.Antigen-specific CD8+ T cells that can recognize and eliminate cancer cells play a crucial role in anti-tumor immune responses. Here we conducted single-cell sequencing of cells infiltrating melanoma specimens originating from 4 patients and determine the TCR clonality of the CD8+ tumor infiltrating cells. We investigated the relationship between T cell clonality and phenotypic cell states coupling single-cell transcriptome to single-cell TCR seq. The surface expression of a panel of protein was detected in parallel using CITE-Seq antibodies. Sorted tumor and peripheral blood specimens were processed in parallel.In order to discover cancer antigens derived from annotated and unannotated protein-coding regions of the genome, we carried out matched ribosome profiling (Ribo-seq), RNA-sequencing, and whole genome sequencing on one of the patients, as well as Ribo-seq on an additional patient. We used it to discover novel or unannotated open reading frames (nuORFs), their expression levels, as well as somatic mutations within them to predict potential neoantigens.

  Study phs001451

• Investigating low frequency variants in CAD/MI cases, controls and pedigrees using whole exome sequencing and custom pulldowns

  The Cardiogenics re-sequencing study will consist of three parts: Eight pools of 25 individuals will be sequenced using a Nimblegen hybrid-capture solution specific to miRNA sequences, 80 pools of 25 individuals will be sequenced using a custom Agilent SureSelect array covering genes associated with coronary artery disease (CAD) and myocardial infarction (MI), 10 individuals from families with a history of CAD/MI will be exome sequenced using the Sanger exome array. The experiment will use the early onset patients from the German MI cohort and the UK BHF CAD/MI cohort both of which have strong family history. For controls we will consider individuals from the UKBS and KORA cohorts.

  Dataset EGAD00001000400

• 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

• Beacon v2 and Federated EGA, part of the GDI project Starter Kit to enable access to genomic and phenotypic data across borders

  The European Genomic Data Infrastructure project has released a ‘Starter Kit’ based on the rare disease and cancer proof-of-concepts from the Beyond 1 Million Genomes (B1MG) project. The Starter Kit, freely available to any interested parties, contains a set of software applications and components co-developed by the 20 GDI nodes and based on open community standards from the Global Alliance for Genomics and Health (GA4GH). Products in the Starter Kit give all countries the technical capability to access synthetic genomic and phenotypic data across borders. The image above shows the full workflow of the GDI Starter Kit user journey. The dotted circles are not included in the Starter Kit yet The EGA’s work is represented in the Starter Kit with Beacon v2 and Federated EGA among the software applications and components. About Beacon v2 Beacon is a protocol for data discovery. This API allows the search of genomic variants and associated information without breaching the datasets privacy. The European Genome-phenome Archive (EGA) is a key contributor to the Beacon v2 Protocol, the Beacon v2 Reference Implementation (B2RI) and the EGA Beacon(s). About Federated EGA The Federated EGA network offers a tool for data storage and sharing. Officially launched in 2022, this network of connected resources enables transnational discovery of and access to human omics data for research, while also respecting jurisdictional data protection regulations. The Federated EGA Onboarding Website contains all the information related to the establishment of a Federated Node.

  Blog beacon-v2-and-federated-ega-part-of-the-gdi-project-starter-kit

• PAGE: Global Reference Panel

  Stanford contributed samples to the PAGE study that can act as a population reference dataset across the globe. Therefore this dataset includes reference individuals, without phenotypes, chosen to help infer ancestry that will help us understand the diverse samples available in PAGE. The complete dataset comprises individuals of European, African, Asian, Oceanian, and Native American descent, from a total of over 50 populations. A subset of these individuals from Puno, Peru and Easter Island (Rapa Nui), Chile, are included in the PAGE samples that were whole genome sequenced in 2015. Additional details are available in the Study Acknowledgments. The Global Reference Panel comprises 6 sample sets: A population sample of Andean individuals primarily of Quechuan/Aymaran ancestry from Puno, Peru A population sample of Easter Island (Rapa Nui), Chile Individuals of indigenous origin from Oaxaca, Mexico Individuals of indigenous origin from Honduras Individuals of indigenous origin from Colombia Individuals of indigenous origin from the Nama and Khomani KhoeSan populations of the Northern Cape, South Africa In addition, we genotyped publicly available samples that will be hosted on the Bustamante lab website (https://bustamantelab.stanford.edu/). These comprise large public datasets to provide an open reference dataset for the world: The additional related individuals from the Americas in the Human Genome Diversity Panel (H952) plus all additional samples from the Americas A subset of the unrelated individuals from the Maasai in Kinyawa, Kenya (MKK) dataset from the International Hapmap Project hosted at Coriell Additional samples will be available for restricted use with a data access agreement with the Bustamante Lab. This study is part of the Population Architecture using Genomics and Epidemiology (PAGE) study (phs000356).

  Study phs001033

• How to request data

  Request Data Access If you're looking to access data from the EGA for your research, you are in the right documentation page! In this page you will find a step by step guide on how to request data archived at the EGA, as well as some frequently asked questions you might find useful. When requesting data, you'll need to provide information about your research project and intended use of the data. Keep in mind that your data access request may require additional approvals or agreements depending on the datasets and data providers involved. Step by step guide Register yourself as an EGA user. Validate your account. A validation link will be sent to your email to activate your EGA user account. Log into the EGA page. Search the dataset of interest from the dataset catalogue or search bar. Click on “Request access” Add a comment requesting these files and send your request Your request is successfully registered, and the DAC will receive a notification about your request In addition to submitting your request, you should also contact the DAC directly via e-mail. You can access the DAC's contact information from the relevant dataset page. Frequently Asked Questions (FAQ) Which is the role of the EGA in the data access process? The European Genome-phenome Archive (EGA) facilitates the secure distribution under controlled access of personally identifiable genetic and phenotypic data. Data Access Committee (DAC) is a body of one or more individuals who are responsible for data release to external requestors, based on participant consent and/or National Research Ethics terms. How do I request access to multiple datasets? To request access for multiple datasets managed by the same Data Access Committee (DAC), please start by visiting the DAC catalogue to locate the DAC of your choice. Once you've found the relevant DAC, proceed to its dedicated page where you'll find a "Request access" button. After logging in to the EGA website, you'll be presented with a comprehensive list of datasets under the chosen DAC. Select the datasets you're interested in, and then compose a message indicating your access request. Click the "Send" button to submit your request, which will include the chosen datasets. Please be sure to review the data usage policies for the requested datasets, as policies can vary among datasets managed by the same DAC. I am a co-applicant. Will I be given a joint access account? Each applicant needs to create an EGA account themselves, with unique login details. User log-in details are for individual use only and should never be shared, under any circumstances. EGA services are only provided to EGA account holders. Therefore, the co-applicant will send a formal request to the DAC. What happens if a co-applicant leaves or a new member needs to be added to an existing DAC application? The appropriate Data Access Committee (DAC) should be contacted and informed about the required changes so that the application can be updated. I have changed my place of work since my EGA account was created. Can I still have access to data? You must contact the relevant Data Access Committee (DAC). The DAC did not reply to my data access request. How should I proceed? There is no estimated time for DAC response. Please allow up to four weeks for a response. In the meantime, please send them a weekly reminder of the status of your request by emailing them directly.If the DAC becomes unresponsive, meaning that they fail to communicate with a requestor within the specified time frame, please contact the EGA Helpdesk team. I have an account with the EGA and would like access to further datasets. How should I proceed? You need to reapply to the relevant Data Access Committee (DAC). Once the DAC has approved your application your account will be updated and an email will be sent to notify you of a change made to your account. How do I download files of the datasets I have been granted access to? The preferred method for data download and decryption is the EGA Secure Download Client. Please carefully review the provided documentation. How do I download metadata? Metadata is retrieved from the EGA webpage; you will not need to use any download client. Be informed that you will only be able to download metadata of your approved datasets. For such download, you should first log in the EGA webpage with your credentials. Then browse the metadata's dataset you have gained access and you will find a metadata download button. You may also want to have a look our metadata schema. I have forgotten or misplaced my user account password; how do I get a new one? Click on “Log in”, located in the top right corner of the EGA homepage. Then click “Forgot password”, type in your registered institutional email address, and instructions for resetting your password will be sent to you. Please check both regular and junk/spam folders. I was sent a link to set a password for my download account, but it seems like the link has expired. What should I do? The procedure is the same as the one for a forgotten password, explained in the previous question.

  Documentation access/request-data/how-to-request-data

• RNA sequencing data of 142 samples from 142 patients with HER2+ breast cancer treated with letrozole or tamoxifen (SOLTI PAMELA trial)

  PAMELA (NCT01973660) is a non-randomized, open-label, multicentric, prospective translational research study in stage I-IIIA HER2+ breast cancer designed to evaluate the ability of the PAM50 intrinsic subtypes to predict pCR in the breast (pCRB) following 18 weeks of neoadjuvant lapatinib and trastuzumab (+/- hormonal therapy if hormone receptor [HR] positive). Patients with HR+ disease received letrozole (if postmenopausal) or tamoxifen (if pre-menopausal). The primary objective was to compare the pCRB rates of the HER2-E versus the non-HER2-E subtypes in the intent-to-treat population.

  Study EGAS00001006410