17524 results for "fc 26 coins Buyfc26coins.com is EA Sports official for FC 26 coins They are definitely a top seller..rG5l"

in 27.18 milliseconds.

• IMCISION RNAseq

  RNA sequencing of 32 primary head and neck squamous cell carcinoma (HNSCC) samples prior to treatment with neoadjuvant anti-PD-1 (n=6) or anti-PD-1 + anti-CTLA-4 (n=26) immunotherapy, and 30 paired on-treatment HNSCC samples (i.e. after neoadjuvant immunotherapy). RNA quantity used: 10ng. Library Preparation Kit: SMART Stranded Total RNA Seq Kit (Takara). Sequencing parameters: NovaSeq 6000, 2x 100 bp. File type: fastQ

  Dataset EGAD00001008127

• HELIUS cohort

  The gut microbiota composition is unique to every individual but is shaped by common factors including diet, lifestyle, medication use, early-life determinants, living environment or genetics. Most of these factors may be influenced by ethnicity. This study explored variations in fecal microbiota composition in 6048 individuals with different ethnic backgrounds living in the same geographical area (Amsterdam, the Netherlands). The HELIUS data are owned by the Amsterdam University Medical Centers, location AMC in Amsterdam, The Netherlands. To allow sharing of microbiome data collected in HELIUS with (inter)national researchers, 16s rRNA sequence analysis has been stored at the European genome-phenome archive (EGA; accession code EGAD00001004106). This requires that access needs to be granted, also because the HELIUS data are stored with relevant phenotypical variables. Access is granted to all researchers affiliated with an internationally recognized research institution who request to use the HELIUS data within the EGA context, after having signed the data transfer agreement. Any researcher can request the data by submitting a proposal to the HELIUS Executive Board as outlined at http://www.heliusstudy.nl/en/researchers/collaboration, by email: heliuscoordinator at amsterdamumc dot nl. The HELIUS Executive Board will check proposals if they do not conflict with ethical approvals and informed consent forms of the HELIUS study.

  Study EGAS00001002969

• DAC Portal documentation

  DAC Portal Welcome to the DAC Portal documentation! If you are involved in governance or legal aspects, technical or operational aspects, or serving as a data steward, this page will be helpful for you. By exploring these materials, you can define your own Data Access Committee (DAC) and policies, understand the minimal requirements for a DAC and a policy object, and comprehend how the EGA data access requests are managed. DAC Portal Index Setting up your account DACs and Policies Pending Request table Manage Data Requests History page Audit your DACs, policies, and datasets Deprecation User Preferences DAC API - A programmatic approach Setting up your account Register yourself as an EGA user. The Helpdesk team will validate your account (this could take up to 48 hours). After validation, you will receive an email with a link to verify your email - Make sure you click on the link to verify your account! If you don’t receive the email, please check your spam folder. Once your account is active you can login to the DAC Portal. We recommend you to check out the Take The Tour! DACs and Policies Create a DAC Click on Create a DAC Add the title and description to your DAC. Once ready, click on the ‘Create’ button. You will have to wait until the Helpdesk Team validates the creation of your DAC. Once approved by Helpdesk, your DAC will be assigned with a persistent identifier (EGAC). Edit a DAC Once your DAC is registered and approved, you can edit it and add contacts. Remember, you can add as many contacts as needed. And, you can also remove/add contacts anytime. To add a contact, you must write the username or email of a registered EGA user in the Members field. Once you have typed the whole username or email, a drop-down menu will appear where you can select the contact. Select a contact from the drop-down menu. Make sure you write the full username or email of the contact so it appears as an option. Make sure that you select one main contact. Set up the role you want to grant to the new contact of the DAC. We recommend you to check out the FAQ to learn more about the different roles! After adding all the necessary contacts and assigning roles, click on Update. This will send an email notification to the new DAC member, letting them know about the invitation to managing the DAC. Once they log into the DAC Portal, they will be able to either accept or turn down the invitation. Create a policy First, please note that all information registered in a policy metadata object will be publicly available on the EGA website. For each released dataset, all users will be able to read the policy under the “Data Access” tab. Select Create a Policy from the Policies tab. Select the DAC that you want your policy to depend on. Add the title and terms and conditions for accessing and using your data. If you already have an external website for data access requests, you can add the URL directly here (see example here). You can find a template of a Data Access Agreement (DAA) document in our Policy documentation page. The DAA template is provided for guidance only and should be adapted to suit your own purpose depending on the security policies, terms for publication or embargoes, and restrictions on data use or sharing. You can also add Data Use Ontologies (DUO) to your policy. These DUO codes are used to semantically tag the terms and conditions of using the data linked to the policy (example). For more information, you can refer to the Data Uso Ontology documentation. Once completed, make sure to click the Create button in order to register your policy. A persistent identifier (EGAP) will be assigned automatically. Edit a policy Please, note that you will not be able to edit the policy if it shows in orange. Meaning that you are a member of the DAC linked to that policy. Members don’t have edit rights. Only admins can edit objects. You can check your registered policies on My policies, available at the menu in the top-right corner. Select your policy. It will then display the information of that policy, allowing you to edit the information. Once you are done with the modifications, click Update. Pending Requests Table Table Settings Upon selecting a specific DAC, you will be presented with a customisable table showcasing all pending data access requests. This table allows you to tailor the displayed information according to your preferences by selecting desired columns. Available Columns (Displayed with the Eye Icon): Date: The date when the data access request was submitted. Full Name: Name and surname of the user submitting the request. Email: Email address associated with the user's request. Username: The username linked to the EGA account of the user submitting the request. Organisation: Affiliated organisation of the user submitting the request. Dataset: EGA accession ID for the requested EGA dataset. Dataset Title: Title of the requested dataset. DAC Comment: Space provided for internal comments related to the request. Expiration: Option to specify an expiration date for granted permissions. Check more information on the pending request table here! Table Filters By default, all data access requests are displayed. However, you have the option to apply filters to refine your view. Follow these steps to apply filters: Click on the More button. This action will reveal the different columns available for applying filters. As you select columns, the checked fields will be displayed at the top of the request table. Choose the specific values within the selected columns that you want to filter for. Click the Search button to apply the selected filters. Do you find yourself frequently applying the same filters? You can save multiple combinations of filters for easy access at any time! Here's how: Click the Save button. Provide a descriptive name for the filter combination. Click Save to confirm. To load saved filters, simply select the saved filter from the dropdown menu to apply it automatically. Check more information on filters here! Advanced Search For users requiring more granular control over their data access requests, the DAC Portal offers an Advanced Search feature using JIRA Query Language (JQL). With JQL, you can craft precise and complex queries to filter and retrieve specific data access requests based on various criteria such as date, user details, dataset attributes, and more. Using JQL's flexibility, you can create custom queries to meet your specific needs, allowing for advanced filtering options beyond the standard filters provided. You can find the Advanced Search feature following these steps: Click the … button Select Advanced To view the allowed fields for filtering and explore all available options, simply click on the info icon. Once you have written the filtering values, click the Search button to apply. Check more information on filters here! Manage Data Requests Upon logging into the DAC Portal, you'll notice a sand clock icon next to the DAC ID, indicating the number of pending requests. Click on the DAC to review these requests. Accept requests Click on the right side of the toggle button to grant access to the user. You can manage other requests before proceeding to the next step. After managing the requests, click on the Apply button. A confirmation box will appear summarising the options to be applied. Click on Yes, Confirm to proceed with granting permissions. Deny requests Click on the left side of the toggle button to deny access to the user. Provide a reason for the denial. Note that the user will receive an email with this reason. Click on the Done button. You can manage other requests before proceeding to the next step. After managing the requests, click on the Apply button. A confirmation box will appear summarising the options to be applied. Click on Yes, Confirm to proceed with denying permissions. Tips! Apply a filter to view all requests to be managed at once. Use the toggle in the row with column names to grant or deny permissions for multiple requests simultaneously. You can grant and deny permissions in the same action, simplifying the process. The confirmation box will provide a summary of all actions, including grants, denials, DAC comments, and expiration dates. History Page The History page serves as a dedicated space to view information regarding all requests managed by all DAC members. Here, you can review active permissions and revoke them as needed. Go to the History page by clicking on the "HISTORY" button from a DAC page in the DAC Portal. Here are the different row types you may find: Current permissions: row in green with a toggle button to revoke permissions on the right. Approved requests: row in green, with no toggle button. Request denied: row in red with “request denied” on the right. Permission revoked: row in red with “permission revoked” on the right. Distinctions to Note! Between Request Denied and Permission Revoked: Request Denied: Refers to requests that were rejected from the outset, indicating that access to the dataset was never granted. Permission Revoked: Indicates that permissions were previously granted but have since been revoked. Users with permissions revoked have previously accessed the dataset. Between Approved Request and Current Permissions: Approved Request: Represents an entry when a data access request has been approved in the past. Current Permissions: Denotes ongoing permissions where a user has present access to the dataset. An approved request may now appear as Permission Revoked in the present. By observing these different rows, users can gain insight into the complete history of a user's interactions and permissions regarding a dataset over time. To revoke access to a specific user for a dataset, follow these steps: Go to History page Look for the row with the specific permissions. You can use the filters! Click on the toggle button to revoke access. Add a denial reason. Bear in mind that the requester will receive the denial reason! Click on the Apply button. Check more information on the Hisotry page here! Audit your metadata objects In the DAC Portal, you can efficiently manage and audit various metadata objects pertinent to your role as a Data Controller. Upon accessing the DAC Portal, you will encounter three primary tabs on the homepage: DAC: Contains information about Data Access Committees (DACs). Policies: Provides insights into linked policies. Datasets: Displays datasets and relevant details. Within each tab, you'll find a comprehensive list of the objects you manage, these being grouped by type (DAC, Policies, Datasets), as well as by your role (member/admin). Whilst the lists give you a quick look, to check how things are connected, we've added a table at the bottom DACs and policies. DACs Let’s check which policies are linked to a specific DAC: Go to "My DACs." Select a DAC. Click on "EDIT" to see more details. You are now on this page: Scroll down to see the linked policies. Click on “List of linked policies of this DAC” and you will see a list of all policies linked to your selected DAC. Policies Do you want to view a list of datasets connected to a particular policy? Follow the same steps mentioned earlier, but head to the policy tab this time. In the policy tab, you'll find a list of all your policies. Here, you may notice two different icons next to the policy ID (EGAP): DAC Icon (): This represents the DAC. Hover your mouse over the icon to see the DAC ID. Dataset icon (): This indicates datasets falling under that policy. The number next to the icon tells you how many datasets are linked to the policy. For example, if you see "2" next to the icon, it means there are two datasets linked to that policy. If you want to check the linked datasets and their relevant information, simply click on a specific policy. You'll then find the "List of linked datasets of this policy" at the bottom of the page. Datasets Finally, in the dataset tab, by default you will see a list of all the datasets you can manage with all your DACs and policies. Yet, we've included two handy ways to organise them: DAC vs. policy: You can group by datasets, either by DAC or policy. Released vs. unreleased: You can sort out datasets based on their release status. Feel free to experiment with both options! For instance, if you want to see which DACs have unreleased datasets, simply select DAC and unreleased, and you'll get the details you need! Deprecation Do you have a bunch of metadata objects like DACs and policies that you don’t need anymore? This section shows you how to get rid of them! But what does "deprecation" mean for EGA? It's basically changing the status of a metadata object to "deprecated," which means we won't be using it in the future. In simple terms, it's like saying these objects are no longer useful. However, because we believe in making metadata FAIR, once an object has a persistent identifier, we can't just delete it. So, instead of deleting, we deprecate it. Here's a helpful tip! If you want to make a metadata object disappear from the DAC Portal, deprecate it. You won’t see it in the portal anymore! Let’s say you want to deprecate a DAC. Let’s do it! Go to "My DACs." Select a DAC. Click "EDIT" to see more details. You are now in this page: Click on the Deprecate button It will then appear a message. There are two options here: Your DAC is not linked to any policy, hence it’s ready to be deprecated. Click on “Yes. Confirm” to deprecate your DAC object! Your DAC is linked to at least one policy, and you need to either: Deprecate the linked policy first, or Link the policy to a different DAC Now, let’s say you don’t want to get rid of the policy altogether, but you want to change the DAC it’s linked to. Here's how: Go to the policy tab. Find the policy you want to change (for example, EGAP50000000019). Choose a new DAC to link it to. Click on Update. See the Edit Policy section for more details. After ensuring that the DAC we want to deprecate isn’t linked to any policy, return to the "My DACs" section and follow the steps outlined previously. This will lead you to a confirmation message. You can only deprecate DACs and Policies. To deprecate a dataset, please contact our Helpdesk team. Check more information on how deprecation works here! User Preferences We have implemented email notifications in the DAC Portal. Here’s the complete list: DACs: Pending requests Approved by Helpdesk Rejected by Helpdesk DAC Invitation Requesters: Data access request approved Data access request denied Permissions revoked Upcoming expiration date As a DAC member, you will be able to decide whether you want to receive the DAC notifications or not. For that, go to the top-right corner menu, select User Preference. You will be able to decide whether you want to receive notifications for: Approved by Helpdesk Rejected by Helpdesk DAC Invitation For pending requests, you will be able to select how often do you want to receive the notification: Daily Weekly Fortnightly As a DAC member, you are responsible for managing data access requests. Consequently, you will receive notifications for pending requests. If you prefer not to manage these requests, please arrange to be removed as a contact for your DAC. Here's a tip! Do you have a pending request that you don’t want to receive a notification? Add a DAC comment! 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! DAC API - A programmatic approach In addition to the new DAC Portal, we are excited to announce the release of the DAC API. This enables users to programmatically manage permissions. If you are interested in learning more about the technical specifications, you can click the button below. Check out the DAC API specification!

  Documentation access/data-access-committee/dac-portal

• Genetic determinants of monocyte splicing are enriched for disease susceptibility loci including for COVID-19

  These data correspond to samples used in the following papers: 1. GWAS and meta-analysis identifies 49 genetic variants underlying critical Covid-19 2. Genetic determinants of monocyte splicing are enriched for disease susceptibility loci including for COVID-19. 3. Identification of Genetic Determinants of Transcriptional Response to Metformin in Primary Human Monocytes. They are the raw RNA sequencing files as used in all downstream analysis.

  Dataset EGAD00001010176

• ALCHEMIST Study

  The ALCHEMIST study will accrue patients that are potentially eligible for the Intergroup adjuvant studies and perform central EGFR and ALK genotyping using a central reference laboratory certified by the Clinical Laboratory Improvement Amendments of 1988 (CLIA). Patients may either present prior to surgery with resectable NSCLC, may present following complete resection (before or after adjuvant chemotherapy). Eligibility is limited to those with NSCLC of a non-squamous histological subtype and those with adequate performance status and organ function for future trial eligibility. All subjects must submit tissue for central EGFR and ALK genotyping, as well as additional tissue for advanced genomics at the CCG. Subjects may have had local genotyping done prior to registration, however if these results shows no targetable EGFR or ALK alterations (or if it shows a KRAS mutation) then the patient will not be eligible for this screening protocol given the primary aim is to facilitate accrual to the adjuvant studies. All subjects will provide peripheral blood for matched normal DNA. All subjects (including those known to have EGFR or ALK alterations with local genotyping) will have formalin-fixed tissue collected for central genotyping. The testing will be performed at Response Genetics (Los Angeles, CA), a commercial CLIA-certified laboratory. ALK FISH will be performed using the Vysis break-apart probe and EGFR sequencing will be performed of exons 18-21. It is preferred that a full tumor block be submitted, but if unavailable, 15 unstained slides can be submitted. Genotyping results are expected to be provided to the treating clinician within 14 business days of submission so they can be used to determine eligibility for the randomized adjuvant studies, or to confirm the local results. Results will also be reported at intervals to the study team for update into the Alliance database. In addition to the commercial genotyping at Response Genetics, tissue will be collected for research genomics by CCG. For those patients with a block available, this will be forwarded to the CCG after clinical testing at Response Genetics. For patients without a block available, 15 unstained slides should be submitted to the CCG BCR for exploratory analysis. A peripheral blood specimen will also be collected and sent to the CCG BCR to use as matched normal. Specimens will be coded. Over the course of the study, the CCG will perform advanced genomic analysis of the resected lung cancer specimens in a research, non-CLIA environment. Following completion of the genomic analysis, the results can be matched with the clinical follow-up results using a link between the samples codes and the patient identifiers for correlative analyses. Subjects participating in the follow-up portion of the ALCHEMIST study, as well as those participating in the adjuvant therapeutic studies, are expected to undergo a standard-of-care diagnostic biopsy to confirm recurrence. At least two core biopsies, minimum, should be obtained as part of this recurrence biopsy. Paraffin embedded tissue from this biopsy will be used for confirmation of recurrence, for CLIA genomics to plan subsequent clinical trials, and for additional research genomics by the CCG. Plasma will additionally be collected at recurrence and sent to CCG for study of circulating free DNA (cfDNA). Data for the ALCHEMIST study is not yet available to be accessed by the public at this time; when ready it will be made available at the GDC Data Portal.

  Study phs001140

• Mutational Patterns in Metastatic Cutaneous Squamous Cell Carcinoma

  Cutaneous squamous cell carcinoma (cSCC) from the head and neck typically metastasizes to the lymph nodes of the neck and parotid glands. When a primary is not identified, they are difficult to distinguish from metastases of mucosal origin and primary salivary gland SCC. Ultraviolet radiation causes a mutation pattern that predominantly features cytosine to thymine transitions at dipyrimidine sites and has been associated with cSCC. In this study, we used whole genome sequencing data from 15 cSCC metastases and show that a UV signature mutation is pervasive across the cohort and distinct from mucosal SCC. The mutational burden was exceptionally high and concentrated in some regions of the genome, especially insulator elements (mean 162 mutations / Mb). We therefore evaluated the likely impact of UV-induced mutations on the dipyrimidine rich binding site of the main human insulator protein, CCCTC-binding factor (CTCF), and the possible implications on CTCF function and the spatial organization of the genome. Our findings suggest that mutation signature analysis may be useful in determining the origin of metastases in the neck and the parotid gland. Furthermore, UV-induced DNA damage to insulator binding sites may play a role in the carcinogenesis and progression of cSCC.

  Study EGAS00001003370

• National Human Genome Research Institute (NHGRI) GENEVA Genome-Wide Association Study of Venous Thrombosis (GWAS of VTE)

  Overview: Our overall long-term goal is to determine risk factors for the complex (multifactorial) disease, venous thromboembolism (VTE), that will allow physicians to stratify individual patient risk and target VTE prophylaxis to those who would benefit most. In this genome-wide association case-control study (1300 cases and 1300 controls) we hope to identify susceptibility variants for VTE. Mutations within genes encoding for important components of the anticoagulant, procoagulant, fibrinolytic, and innate immunity pathways are risk factors for VTE. We hypothesize that other genes within these four pathways or within other pathways also are VTE disease-susceptibility genes. Therefore, we performed a genome wide association (GWA) screen and analysis using the Illumina 660W platform to identify SNPs within 1,300 clinic-based, non-cancer VTE cases primarily from Minnesota and the upper Midwest USA, and 1300 clinic-based, unrelated controls frequency-matched on patient age, gender, myocardial infarction/stroke status and state of residence. This is a subset of a slightly larger candidate gene study using 1500 case-control pairs to identify haplotype-tagging SNPs (ht-SNPs) in a large set of candidate genes (n~750) within the anticoagulant, procoagulant, fibrinolytic, and innate immunity pathways. Study Populations. Cases. VTE cases were consecutive Mayo Clinic outpatients with objectively-diagnosed deep vein thrombosis (DVT) and/or pulmonary embolism (PE) residing in the upper Midwest and referred by Mayo Clinic physician to the Mayo Clinic Special Coagulation Laboratory for clinical diagnostic testing to evaluate for an acquired or inherited thrombophilia, or to the Mayo Clinic Thrombophilia Center. Any person contacted to be a control but discovered to have had a VTE was evaluated for inclusion as a case. Cases were primarily residents from Minnesota, Wisconsin, Iowa, Michigan, Illinois, North or South Dakota, Nebraska, Kansas, Missouri and Indiana. A DVT or PE was categorized as objectively diagnosed when (a) confirmed by venography or pulmonary angiography, or pathology examination of thrombus removed at surgery, or (b) if at least one non-invasive test (compression duplex ultrasonography, lung scan, computed tomography scan, magnetic resonance imaging) was positive. A VTE was defined as: Proximal leg deep vein thrombosis (DVT), which includes the common iliac, internal iliac, external iliac, common femoral, superficial [now termed "femoral"] femoral, deep femoral [sometimes referred to as "profunda" femoral] and/or popliteal veins. (Note: greater and lesser saphenous veins, or other superficial or perforator veins, were not included as proximal or distal leg DVT). Distal leg DVT (or "isolated calf DVT"), which includes the anterior tibial, posterior tibial and/or peroneal veins. (Note: gastrocnemius, soleal and/or sural [e.g., "deep muscular veins" of the calf] vein thrombosis was not included as distal leg DVT). Arm DVT, which includes the axillary, subclavian and/or innominate (brachiocephalic) veins. (Note: jugular [internal or external], cephalic and brachial vein thrombosis was not included in "arm DVT"). Hepatic, portal, splenic, superior or inferior mesenteric, and/or renal vein thrombosis. (Note: ovarian, testicular, peri-prostatic and/or pelvic vein thrombosis was not included). Cerebral vein thrombosis (includes cerebral or dural sinus or vein, saggital sinus or vein, and/or transverse sinus or vein thrombosis). Inferior vena cava (IVC) thrombosis Superior vena cava (SVC) thrombosis Pulmonary embolism Patients with VTE related to active cancer, antiphospholipid syndrome, inflammatory bowel disease, vasculitis, a rheumatoid or other autoimmune disorder, a vascular anomaly (e.g., Klippel-Trénaunay syndrome, etc.), heparin-induced thrombocytopenia, or a mechanical cause for DVT (e.g., arm DVT or SVC thrombosis related to a central venous catheter or transvenous pacemaker, portal and/or splenic vein thrombosis related to liver cirrhosis, IVC thrombosis related to retroperitoneal fibrosis, etc.), with hemodialysis arteriovenous fistula thrombosis, or with prior liver or bone marrow transplantation were excluded. Controls. A Mayo Clinic outpatient control group was prospectively recruited for this study. Controls were frequency-matched on the age group (18-29, 30-39, 40-49, 50-59, 60-69, 70-79, and 80+ years), sex, myocardial infarction/stroke status, and state of residence distribution of the cases. We selected clinic-based controls using a controls' database of persons undergoing general medical examinations in the Mayo Clinic Departments of General Internal Medicine or Primary Care Internal Medicine. Additionally persons undergoing evaluation at the Mayo Clinic Sports Medicine Center, and the Department of Family Medicine were screened for inclusion as controls. This study is part of the Gene Environment Association Studies initiative (GENEVA, http://www.genevastudy.org) funded by the trans-NIH Genes, Environment, and Health Initiative (GEI). The overarching goal is to identify novel genetic factors that contribute to venous thrombosis through large-scale genome-wide association studies of 1,300 clinic-based, VTE cases and 1300 clinic-based, unrelated controls. Genotyping was performed at the Johns Hopkins University Center for Inherited Disease Research (CIDR). Data cleaning and harmonization were done at the GEI-funded GENEVA Coordinating Center at the University of Washington.

  Study phs000289

• Transdisciplinary Research Into Cancer of the Lung (TRICL) - Exome Plus Targeted Sequencing

  The study was conducted under the auspices of the Transdisciplinary Research In Cancer of the Lung (TRICL) Research Team, which is a part of the Genetic Associations and MEchanisms in ONcology (GAME-ON) consortium, and associated with the International Lung Cancer Consortium (ILCCO). Ethics All participants provided written informed consent. All studies were reviewed and approved by institutional ethics review committees at the involved institutions. Sequencing data are derived from four sub-studies. The sub-studies that contributed include Harvard, Liverpool, Toronto, and IARC. The IARC and Toronto studies are described above. A description of the Harvard and Liverpool studies is provided below. Liverpool Lung Project: The Liverpool Lung Project (LLP)1 is a case control and cohort study, which has over 11,500 individuals, with detailed epidemiological, clinical and outcome data with associated specimens (i.e. tumour tissue, blood, plasma, sputum, bronchial lavage, EBUS and oral brushings). The participants have completed a detailed lifestyle questionnaire and updated data on clinical outcome and hospital events are collected through the Office of National Statistics, Cancer Registry and from Health Episode Statistics. The project is registered on the UK National Institute for Health Research (NIHR) lung cancer portfolio and has all the required ethical approvals and sponsorship arrangements in place. The LLP has detailed standard operating procedures (SOP) for all aspects of the recruitment, data, specimen collection as well as the data storage. The LLP Cohort study has 8,224 participants with blood and 7,761 with plasma samples. The LLP case-control samples have been incorporated into in a large number of international GWAS and molecular studies 2,3, methylation 4-7, microRNA 8and next generation studies 9-11, resulting in high ranking publications, as well as forming the basis for the LLP risk prediction model 12-14 which has been utilised in the UK lung cancer screening trial (UKLS) 15-17 Patient and control DNAs were derived from EDTA-venous blood samples. Harvard Samples. David Christiani at the Harvard University School of Public Health has been directing research studies to investigate etiological factors influencing lung cancer development since 1983 and has amassed a collection of 2000 controls and 5055 lung cancer cases. He has been actively collecting and storing snap frozen tumor samples since 1992. Around 1500 tumor samples have been collected and the average wet tumor yield is about 30 grams of tumor, of which 631 cases have completely annotated clinical and survival information. Pathology confirmation is provided by two pathologists. At the time of surgery, a minimum of 30 grams of wet lung tumor tissue and 30 grams of non-involved tissue from the same lobe is sectioned, flash frozen and sent to Dr. Christiani's lab for logging and storage. A blood sample for DNA and serum is collected. A structured interview by trained research staff is conducted on each case, and clinical outcomes and treatments is extracted and entered into the molecular epidemiology data base at Harvard. Fresh frozen samples have been collected from 1451 lung cancer and are available for study. Samples from this collaborative study have played key roles in major studies, including the initial finding describing EGFR mutations in lung cancer 22. Participants in this study are patients, > 18 years of age, with newly diagnosed histologically confirmed lung cancer. Samples that are included in the analysis have the following histologies: Adenocarcinoma: 8140/3, 8250/3, 8260/3, 8310/3, 8480/3 8560/3; LCC: 8012/3, 8031/3; squamous carcinoma: 8070/3, 8071/3, 8072/3, 8074/3; and other NSCLC: 8010/3, 8020/3, 8021/3, 8032/3, 8230/3. The Toronto Study: The Toronto study was conducted in the Great Toronto Area between 1997 and 2014. Cases were recruited at the hospitals in the network of University of Toronto and Lunenfeld- Tanenbaum Research Institute. At the time of recruitment in the clinical setting, provisional diagnoses of lung carcinoma were first assigned based on clinical criteria. Diagnoses for all cases included were histologically confirmed by the reference pathologist who is a specialist in pulmonary pathology, based on review of pathology reports from surgery, biopsy or cytology samples in 100% of cases. Diagnostic classification was done initially according to ICD-9, ICD-10, and ICD for oncology-2, and subsequently converted to ICD-O-3. Tumors were grouped into the major categories included in this analysis according to primary cancer type based on the ICD-3 definitions. Controls were randomly selected from individual visiting family medicine clinics and Ministry of Finance Municipal Tax Tapes. All subjects were interviewed using a standard questionnaire and information on lifestyle risk factors, occupational history, medical and family history was collected. Blood samples were collected from more than 85% of the subjects. IARC: The IARC data are derived from case-control studies conducted in Russia and include samples that have available tissue samples. Patient and control DNAs were derived from EDTA-venous blood samples. The lung cancer patients were classified according to ICD-O-3; SQ: 8070/3, 8071/3, 8072/3, 8074/3; AD: 8140/3, 8250/3, 8260/3, 8310/3, 8480/3, 8560/3, 8251/3, 8490/3, 8570/3, 8574/3; with tumous with overlapping histologies classified as mixed. The Lung Cancer Transdisciplinary Research Cohort is utilized in the following dbGaP sub-studies. To view genotypes, other molecular data, and derived variables collected in these sub-studies, please click on the following sub-studies below or in the "Sub-studies" section of this top-level study page phs000876 Lung Cancer Transdisciplinary Research Cohort. phs000877 Meta Analysis phs000878 CIDR Lung Cancer phs001681 Affy Axiom Array

  Study phs000876

• How to use the EGA search box

  Tips on how to search Tip 1: Use simple and clear keywords No matter what you are searching: a study, a dataset or a committee; the search will look recursively in all the fields of all the entities in the database. Thus, there is no need to specify which type of data you are looking for. Try to use single and specific words and avoid long and complex expressions. Try it out: cancer rna-seq instead of cancer studies using RNA-seq. Tip 2: Narrow your results using search operators Search operators give you more control over the results. They manage the way keywords are used to restrict the search. By default, the search engine applies an OR operator when a space is inserted between two words. Include AND (capitalised) between the keywords in your search in order to show only pages containing both terms. Try it out: Search all the studies based on transcriptomic data, including those ones that use RNA sequencing to obtain this data. Tip 3: Do not worry about details The search engine automatically checks for the most common spelling mistakes of given words and suggests the use of the correct version. It also ignores capital letters and most punctuation so none of these mistakes will hamper the accuracy of your search. Besides, when using a combination of words, the search engine will suggest similar combinations with a higher number of results. Tip 4: Use words that are likely to appear within the text Unfortunately, our search engine is not able to interpret words yet. Therefore, words which do not appear in the body text will not return any result despite them denoting a group of present terms. For instance, if we are looking for studies focused on neurological diseases, using neurological as a keyword would not be the best option. Instead, you should use the name of each neurological disease such as bipolar disorder, schizophrenia or depression. In the same fashion, incomplete words do not return any result. Please include an asterisk (*) before and/or after the incomplete word in order to allow for partial matching. Try it out: canc* instead of canc(without wildcard). Also you can try out *oma, or even *geneti* Tip 5: Narrow down your search by filtering the results You can filter the results by the following options: general, study, and dataset. Under these categories, you will find more sub-filters to refine your search. Make sure that you click on Apply in order to filter the results. You can clear the filtering anytime. Advanced Searches Additional example queries: Search for DUO:0000005 and word lung example query Or write: DUO:0000005 AND lung Search for an exome sequencing study in dbGaP example query Or write: study_type: "exome sequencing" AND repository:dbGaP Search for an exome sequencing study in EGA example query Or write: study_type: "exome sequencing" AND repository:ega Search for a dataset that is at the EGA beacon and with type "Whole genome sequencing" and with number of samples between 100 and 2000 and with technology "Illumina HiSeq 2000" example query Or write: is_in_beacon:true AND dataset_types:"Whole genome sequencing" AND samples:[100 TO 2000] AND dataset_technologies:"Illumina HiSeq 2000" Search for PMIDS example query Or write: pmids:32025007

  Documentation discovery/metadata/search-box

• Evaluating genetic ancestry and self-reported ethnicity in the context of carrier screening

  Current professional society guidelines recommend genetic carrier screening be offered on the basis of ethnicity, or when using expanded carrier screening panels, they recommend to compute residual risk based on ethnicity. We investigated the reliability of self-reported ethnicity in 9125 subjects referred to carrier screening. We identified several discrepancies between the two sources of self-reported ethnicity and genetic ancestry. As a result, carrier rates and residual risks provided for patient decision-making are impacted if using self-reported ethnicity. We recommend the routine use of pan-ethnic carrier screening panels in reproductive medicine. Furthermore, the use of an ancestry model would allow better estimation of carrier rates and residual risks.

  Study phs001482