10978 results for "division 1 coins fc 26 Buyfc26coins.com is FC 26 coins official site..AwVj"

in 13.87 milliseconds.

• Bladder cancer subtyping study across 4 atezo clinical trials

  Checkpoint inhibitors targeting the PD-1/PD-L1 interaction have revolutionized cancer therapy across many indications. In urothelial carcinoma (UC), several PD-1/PD-L1 inhibitors have been approved for treatment in localized and metastatic disease. While these agents provide durable clinical benefit in a number of patients, the majority do not respond. A better understanding of the molecular mechanisms underlying response and resistance is needed to tailor existing treatments and develop new therapeutics in UC. We profiled tumors from 2803 patients from four late-stage randomized clinical trials evaluating the PD-L1 inhibitor atezolizumab in metastatic UC and muscle-invasive bladder cancer by RNA-seq, a targeted DNA panel, immunohistochemistry, and digital pathology. A machine learning algorithm identified four UC transcriptional subtypes, representing luminal desert, stromal, immune, and basal tumors. Overall survival benefit from atezolizumab over standard-of-care was observed in immune and basal tumors (45% of patients). Digital pathology showed enrichment of human interpretable features in specific molecular subtypes, and a self-supervised approach could classify molecular subtypes from H&E slides with high accuracy, suggesting that machine-based image interpretation could accelerate tumor molecular profiling. Somatic alterations showed limited capacity to identify responders. Finally, mechanisms of benefit with PD-L1 blockade appeared different in immune and basal tumors, with immune tumors benefiting from B/plasma cell enrichment, while basal tumors benefited from granulocyte enrichment. This study represents the largest integration of UC molecular and curated clinical data in randomized clinical trials to date, paving the way for prospective clinical studies tailoring treatment regimens to specific tumor molecular subtypes in UC and other indications.

  Study EGAS50000000497

• Whole genome sequencing of tumor samples from advanced pre-treated NSCLC patients recruited in a phase I/II single-arm trial utilising CVA21, an oncolytic coxsackie virus, in combination with pembrolizumab.

  Acquired or de novo resistance to immune checkpoint inhibitors occurs in the majority of advanced non-small cell lung cancers (NSCLC). There is an unmet need to improve outcomes for patients with this condition. Oncolytic viruses represent an attractive treatment approach due to their dual activity in inducing tumor cell lysis directly and potentially augmenting anti-tumor immunity. Here, we present the safety, efficacy and translational findings from a phase I/II single-arm trial utilising CVA21, an oncolytic coxsackie virus, in combination with pembrolizumab in patients with advanced pre-treated NSCLC. We performed paired biopsies pre- and post-treatment in 10 patients who received intravenous CVA21 and pembrolizumab, 8 of whom had prior treatment with immune checkpoint inhibitor (ICI) therapy. Whole genome sequencing and spatial proteomics were performed to comprehensively characterise the response to CVA21. Combination CVA21/pembrolizumab (anti PD-1) therapy was well tolerated with no serious treatment-related adverse events. Partial responses were seen in two patients with prior acquired anti-PD-1 resistance and disease stabilisation in 6 patients, giving a clinical benefit rate of 80%. High baseline tumor mutational burden and PD-L1 expression were observed in patients with better response to treatment. Interestingly, an increase in antigen presentation and CD8+ T cell infiltration was observed on treatment compared with baseline in patients with better progression-free survival. This study demonstrates the potential of CVA21 to modulate the immunogenicity of tumor cells and remodelling the tumor microenvironment, providing novel insights for patient selection for trials involving novel immunotherapeutic approaches.

  Study EGAS00001008258

• Tubulointerstitial fibrosis is the histological hallmark of chronic kidney disease (CKD). Hypoxia and inflammation (i.e., interleukin (IL)-1β signalling) are independent mediators of tubulointerstitial fibrosis. However, the physiological response of human kidney tubular cells to IL-1β/IL-1RI signalling under the hypoxic conditions of CKD is poorly understood and remains a clinical imperative for therapeutic targeting. This study reports that hypoxia and IL-1β act in synergy to trigger cell cycle arrest/cellular senescence of ex vivo patient-derived primary proximal tubular epithelial cells (PTECs).

  Hypoxia and interleukin (IL)-1β are independent mediators of tubulointerstitial fibrosis, the histological hallmark of chronic kidney disease (CKD). Here, we examine how hypoxia and IL-1β act in synergy to augment maladaptive proximal tubular epithelial cell (PTEC) repair in human CKD. Ex vivo patient-derived PTECs were cultured under normoxic (21% O2) or hypoxic (1% O2) conditions in the absence or presence of IL-1β and examined for maladaptive repair signatures. Hypoxic PTECs incubated with IL-1β displayed a discrete transcriptomic profile distinct from PTECs cultured under hypoxia alone, IL-1β alone or under normoxia. Hypoxia+IL-1β-treated PTECs had 692 ‘unique’ differentially expressed genes (DEGs) compared to normoxic PTECs, with ‘cell cycle’ the most significantly enriched KEGG pathway based on ‘unique’ down-regulated DEGs (including CCNA2, CCNB1 and CCNB2). Hypoxia+IL-1β-treated PTECs displayed signatures of cellular senescence, with reduced proliferation, G2/M cell cycle arrest, elevated senescence-associated β-galactosidase (SA-β-gal) activity and increased production of pro-inflammatory/fibrotic senescence-associated secretory phenotype (SASP) factors compared to normoxic conditions. Treatment of Hypoxia+IL-1β-treated PTECs with either a senolytic drug combination, quercetin+dasatinib, or a type I IL-1 receptor (IL-1RI) neutralizing antibody attenuated senescent cell burden. Our data identify a mechanism whereby hypoxia in combination with IL-1β/IL-1RI signalling trigger PTEC senescence, providing novel therapeutic and diagnostic check-points for restoring tubular regeneration in human CKD.

  Study EGAS00001007904

• Submitting array based metadata

  Submitting array based metadata For further information please check our Submission FAQs, submission quickguide as well as submission terms! The submission metadata required for Array-based submission must be submitted using EGA programmatic submission and by completing the Array-based format (AF) template. The guidelines for this workflow are described on this page. Please notice that all files should be encrypted and uploaded prior to the processing of your EGA Array-based-Format (AF) template. You can request a legacy EGA submission account (ega-box-XXXX) by populating this form. Please, allow two business days for our Helpdesk team to contact you after populating this form. Please notice that all files should be encrypted and uploaded prior to the processing of your EGA-Array-based-Format (AF) template. Metadata Model Registering Metadata Use the EGA programmatic submission to register your Study, Samples, Data Access Committee (DAC) and Policy. This online interface enables you to create new and edit existing submissions. Do not use the Submitter Portal to register the metadata objects for array submissions. Please, go to the EGA programmatic submission. Registering Study Go to the EGA programmatic submission Submit an study XML Take a note of your study accession number (EGASXXXXXXXXXXX) To use the study accession number in a publication, we suggest the following format: "Sequence data has been deposited at the European Genome-phenome Archive (EGA), which is hosted by the EBI and the CRG, under accession number EGASXXXXXXXXXXX. Further information about EGA can be found on https://ega-archive.org "The European Genome-phenome Archive of human data consented for biomedical research"(https://doi.org/10.1093/nar/gkab1059 ). Registering Samples Go to the EGA programmatic submission Submit a sample XML Save the list of accession numbers. These will be needed for the AF template. Registering Data Access Committee Further information on the role of your DAC. Go to the EGA programmatic submission Submit a DAC XML Take a note of the DAC accession number (EGACXXXXXXXXXXX) Registering Policy Your Data Access Policy provides the terms and conditions of data use. This is also referred to as the Data Access Agreement (DAA). Completion of a DAA by the applicant/s should form part of the application process to the Data Access Committee (DAA) Go to the EGA programmatic submission Submit a Policy XML Take a note of the Policy accession number (EGAPXXXXXXXXXXX) Complete the Array-based format (AF) spreadsheet Once you have completed the registration of your Study, DAC and Policy using the programmatix submission, you must then complete and return the AF spreadsheet The AF spreadsheet consists on four components: Do not use EGA IDs registered using the Submitter Portal. You can easily identify objects registered in the Submitter Portal by their EGA ID pattern: EGA[A-Z]5{10 more digits} (e.g. for a sample EGAN50000002506). For populating an AF spreadsheet, please exclusively use EGA IDs following this specific pattern: EGA[A-Z]0{10 more digits} (e.g. for a sample EGAN00001691542). Tab1) Webin accessions : Provide the accession numbers for your study, DAC and policy. Please, also add your ega-box number. Tab2) Sample & phenotypes: Please, leave this tab blank. Tab3) Dataset: Describe the dataset to be created Tab4) Data files: Define how your data is going to be organised into datasets and packets for distribution (linkage between samples and files). Should further assistance be required after going through the guide below; please do not hesitate to contact the EGA helpdesk Once the AF spreadsheet is populated, please send it to our EGA helpdesk for further validation. AF spreadsheet Should your submission require multiple DAC's or policies, use ' ; ' to separate the accession numbers. Accessions AF spreadsheet: Samples & phenotypes Samples and phenotypes AF spreadsheet: Datasets We suggest that each dataset consists of a common set of data. The example below consists of two datasets, grouped according to shared data type, technology and by case/control. We also like to capture the number of unique samples that make up the dataset and the Data Access Committee (DAC) responsible for providing the named dataset and their policy (EGAP). Datasets AF spreadsheet: Data files What follows is an example of how to map your samples to the array based files added to your upload account (4th tab). Data Files Please, find below some practical examples on how to register the linkage between samples-files Case 1) 1 sample or list of samples in different datasets: Data Files In case you have a list of samples that belong to different datasets, please, repeat the samples accession number/s in the first column and link the sample to the corresponding dataset each time (each row). Each row is one linkage between sample-file-dataset. Case 2) 1 sample links to several files: Data Files In order to add multiple files to one sample you MUST use “ ; “ between filenames. Example: file1.gpg;file2.gpg;file3.gpg In case that you want to add an extra file to the sample (phenotype or .Rdata), please use “Additional files” column. Important note: You MUST upload the encrypted and unencrypted md5sum values of all files uploaded to your submission account using the filename nomenclature (file.gpg, file.md5,file.md5.gpg). Your submission will not be processed without md5values supplied for all files in the CORRECT format. What happens after the submission of a dataset? All datasets affiliated to unreleased studies are automatically placed on hold until the authorised submitted or DAC contact instructs our EGA helpdesk for the study to be released. Finally, your data is archived within our databases and prepared for encrypted distribution upon the request of permitted EGA account holders. We strongly advise you NOT to delete your data until we confirm that your data has been successfully archived.

  Documentation submission/metadata/submission/array

• RNAseq samples of patients with anti-PD-1 resistant HNSCC from a non-randomized, open-label phase 1b clinical trial

  Immune checkpoint blockade (ICB) is an effective treatment for a subset of patients with head and neck squamous cell carcinoma (HNSCC); however, the majority remain refractory. In a nonrandomized, open-label Phase 1b clinical trial, participants with recurrent and/or metastatic (R/M) HNSCC who had progressed on ICB were treated with low-dose 5-azacytidine (5-aza) daily for either 5 or 10 days, in combination with durvalumab and tremelimumab. The primary objective was to determine the biologically effective dose of 5-aza. In this study, RNA sequencing (RNA-seq) was performed on baseline and on-treatment samples from eight participants, and transcriptomic changes were analyzed to assess the impact of low-dose 5-aza treatment.

  Study EGAS50000000728

• WES samples of patients with anti-PD-1 resistant HNSCC from a non-randomized, open-label phase 1b clinical trial

  Immune checkpoint blockade (ICB) is an effective treatment for a subset of patients with head and neck squamous cell carcinoma (HNSCC); however, the majority remain refractory. In a nonrandomized, open-label Phase 1b clinical trial, participants with recurrent and/or metastatic (R/M) HNSCC who had progressed on ICB were treated with low-dose 5-azacytidine (5-aza) daily for either 5 or 10 days, in combination with durvalumab and tremelimumab. The primary objective was to determine the biologically effective dose of 5-aza. In this study, whole exome sequencing (WES) was performed on baseline samples from 12 participants, and genomic alterations were analyzed to access the genetic background of these participants.

  Study EGAS50000000729

• GoNL aligned sequence data in BAM format.

  We mapped the data to the UCSC human reference genome build 37 using BWA 0.5.9-r16. We first mapped each read pair separately using bwa aln. Then we used bwa sampe to map the paired reads together to a BAM9 file. The BAM file was then sorted by genomic position and indexed using PicardTools-1.32 SortSam. To prevent PCR artifacts from influencing the downstream analysis of our data, we used Picard to mark the duplicate reads, which were ignored in downstream analysis. We used GATK IndelRealigner on our data around known indels (from 1KG Pilot). The IndelRealigner creates all possible read alignments using the source and computes the likelihood of the data containing the indel based on the read pileup. Whenever the maximum likelihood contains an indel, the reads are realigned accordingly. Each base is associated with a phred-scaled base quality score. Calibration of Phred scores is crucial as they are used in some of the downstream analysis models. We used GATK to recalibrate the base qualities with respect to (i) the base cycle, (ii) original quality score, and (iii) dinucleotide context. To minimize issues stemming from mapping problems around indels, we decided to undergo a second round of indel realignment using the GATK IndelRealigner by family rather than by individual. For this second round, we considered two sources of possible indels: 1KG Phase 1 indels and indels aligned by BWA in the GoNL data.

  Dataset EGAD00001001038

• 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

• Identification of the Global miR-130a Targetome Reveals a Novel Role for TBL1XR1 in Hematopoietic Stem Cell Self-Renewal and t(8;21) AML

  In this study, we identified miR-130a as a regulator of HSC self-renewal and differentiation. To characterize gene expression changes following enforced expression of miR-130a OE, we performed RNA-seq in CD34+ cord blood (CB) cells transduced with control and miR-130a OE lentiviruses. To capture miRNA targets in an unbiased, transcriptome-wide manner, we perfomed enhanced CLIPseq procol in 2 replicates of CD34+ CB cells and Kasumi-1 cell line, which represent a model system for t(8;21) AML. We chose this cell line, as we found miR-130a to be highly expressed in this AML subtype where it is critical for maintaining the oncogenic molecular program mediated by AML1-ETO. Chimeric Ago2 eCLIPseq in CD34+ CB cells combined with Mass Spectrometry data analysis identified TBL1XR1 as a principal target of miR-130a. To elucidate gene expression changes associated with TBL1XR1 loss of function, we performed RNA-seq in CD34+CD38- CB cells transduced with control and shRNA targeted against TBL1XR1. To determine the functional significance of high miR-130a expression levels in Kasumi-1 cells on the molecular network controlled by AML1-ETO, we performed CUT&amp;RUN assay and RNA-seq in Kasumi-1 cells following miR-130a knock-down (KD). Collectively, our findings reveal a unique role of miR-130a in regulating normal hematopoietic stem cell self-renewal and how elevated levels of miR-130a in t(8;21) AML contribute to the leukemogenesis of this AML subtype.

  Dataset EGAD00001008412

• African American Multiple Myeloma GWAS

  The case set is from a case-control study designed to identify common genetic risk factors for multiple myeloma in African Americans, the population with the highest risk for this cancer. We conducted two GWAS and combined each of these with convenience controls consisting of unaffected African American participants in cohorts with existing GWAS data. We then conducted a meta-analysis of the two sets. Cases were persons of African ancestry with smoldering or active multiple myeloma identified at participating oncology clinics or through SEER registries, as part of the African American Multiple Myeloma Study (AAMMS) diagnosed from Jan 1, 1988 through July 31, 2016. The majority of the samples were collected from incident and prevalent cases diagnosed since Jan 1, 2008 (80.9%), with a minority obtained from biobanks from cases diagnosed prior to 2008 (19.1%). Additional samples were obtained from the Multiethnic Cohort (USC and University of Hawaii) (n=40), the University of California at San Francisco Multiple Myeloma Study (n=27), and from the Multiple Myeloma Research Consortium for secondary analysis (samples originally provided to MMRC by 8 additional sites (n=84)). We have identified the phenotype (smoldering myeloma, plasma cell multiple myeloma, or myeloma not otherwise specified (myeloma NOS) when myeloma phenotype was not known), sex and age at diagnosis in this data set. The initial GWAS set consisted of 1308 (1,305 passed QC) cases with DNA samples, with a GWAS performed on the Illumina Human Core. Controls consisted of 7,078 unaffected African American subjects who were participants in the African American Prostate and Breast Consortium, with existing GWAS data from the Illumina1M Duo BeadChip. The second GWAS set consisted of 529 African American multiple myeloma patients with samples (406 from University of Arkansas, results not contained in this dataset because NCI funds were not used for the collection and genotyping) with GWAS data resulting from the Illumina Mega-BeadChip v1.1. Controls were 2,390 unaffected African American participants in the Multiethnic Cohort with existing GWAS data from the same array. After QC and removal of duplicates within sets, sex mismatches, and removal of plasmacytoma cases (ICD-0 code 9731), this deposited data set contains the typed GWAS data for the Illumina Human Core (set 1) (n=1298), and for the MegaBead Chip v1.1 (set 2) (n=123), with the University of Arkansas samples removed, for a total of 1,421 case genotypes. Note that 13 samples that overlap set 1 and set 2 were included.

  Study phs001632