1244 results for "get free coins fc 26 Visit Buyfc26coins.com Bardzo pod wrażeniem jakości usług..VZcl"

in 11.20 milliseconds.

• STAMPEED: Northern Finland Birth Cohort 1966 (NFBC1966)

  The Northern Finland Birth Cohorts program (NFBC) was initiated in the 1960s in the two northernmost provinces of Finland to study risk factors involved in pre-term birth and intrauterine growth retardation, and the consequences of these early adverse events on subsequent morbidity and mortality. The uniqueness of NBFCs is that the data of the cohorts were obtained from early fetal life (including maternal health during pregnancy) to adulthood. The NFBC1966 includes 12,058 live births to mothers in the two northern-most provinces of Finland. Two decades later, a second cohort of 9432 births was obtained (NFBC1986). In NFBC1966 pregnancies were followed prospectively from the first antenatal contact (10-16th week). After birth, the offspring were examined and then again underwent clinical evaluation at ages 1y, 7y, 14-16y and 31y. At each visit, a wide range of phenotypic, lifestyle and demographic data were gathered by questionnaires and clinical examinations. For the most part, NFBC1986 has undergone similar evaluations to NFBC1966. Linkage to national registries includes hospitalization, deaths, education, medication, pensions, and provides up-to-date demographic and clinical information for members of both cohorts. DNA samples were obtained from 5,923 subjects from NFBC1966 and 6688 subjects from NFBC1986. Data coverage, 96% of all births in 1966 and 99% in 1986, is highly representative for the whole population. The NFBC program comprises more than 20 different projects coordinated by the Center of Lifecourse Disease studies in Northern Finland (COLD) at Oulu University. The prospective data collected from the NFBCs form a unique resource, allowing the study of disease emergence, and of the importance of genetic, biological, social and behavioral risk factors. The genome-wide association (GWA) study sponsored through the STAMPEED program of NHLBI employed genomic DNA samples previously collected by the NFBC1966 study and stored in the DNA repository of the National Institute for Health and Welfare, Finland. This NHLBI sponsored RO1 project aimed to identify genetic variants contributing to metabolic and cardiovascular diseases (CVD). In addition to de-identified genome wide genotypic data, a selected list of phenotypic data related to CVD including weight, height, BMI, HDL, LDL, total cholesterol, triglyceride, glucose, insulin and fasting status, are also available in dbGaP. A summary of the GWAS for the NFBC1966 cardiovascular risk traits can be found in Sabatti et al., Nature Genetics 41: 35-46, 2009, PMID: 19060910. The version 2 release of this study contains sequence data from seventeen loci associated with levels of triglyceride, HDL-C, LDL-C, total cholesterol, fasting plasma glucose, and fasting plasma insulin (Kathiresan et al. 2008, Willer et al. 2008, Sabatti et al. 2009, Dupuis et al. 2010, Teslovich et al. 2010). At each locus, protein-coding regions and 5' and 3' untranslated regions of genes nearest to single nucleotide polymorphisms showing genome-wide significant association with metabolic syndrome-related traits, were sequenced. Targeted Illumina sequencing of 78 genes (~270kb) using 150bp probes was performed on 4943 subjects of the Northern Finland Birth Cohort 1966 (NFBC1966). Whole exome sequencing on the Illumina platform was carried out on 586 of those participants. The sequencing study is part of a larger project that is funded by the National Human Genome Research Institute's Allelic Spectrum in Common Disease Initiative, and comprises sequence data from more than 7000 individuals in two Finnish cohorts: NFBC1966 and the Finland-United States Investigation of NIDDM Genetics (FUSION) study.

  Study phs000276

• Heart Failure Network - Nitrate's Effect on Activity Tolerance in Heart Failure with Preserved Ejection Fraction (HFN NEAT-BioLINCC)

  Data Access NOTE: Please refer to the "Authorized Access" section below for information about how access to the data from this accession differs from many other dbGaP accessions. Related StudiesEcho images are available with HFN-NEAT Imaging.ObjectivesTo determine the effect of isosorbide mononitrate on daily activity in patients with heart failure and preserved ejection fraction.Background Nitrates are commonly prescribed for symptom relief in patients with heart failure. Early studies in patients with heart failure with a reduced ejection fraction concluded that long-acting nitrates improve activity tolerance; however, approximately half of heart failure patients have preserved ejection fraction. The effects of nitrates in patients with heart failure and a preserved ejection fraction have not been extensively studied and the overall effect of nitrates on activity tolerance in such patients is uncertain. ParticipantsThere were a total of 110 participants enrolled with 51 participants assigned to receive isosorbide mono-nitrate first and placebo second, and 59 participants assigned to receive placebo first and isosorbide mononitrate second. Design Enrolled participants underwent baseline assessments, including echocardiography, quality-of-life scores, 6-minute walk test distance, and NT-proBNP levels. participants were also supplied with two kinetic activity monitors containing high-sensitivity triaxis accelerometers, to be worn 24 hours per day. The accelerometer measurements were expressed as arbitrary accelerometer units and stored every 15 minutes equaling 96 data points per day. The 15-minute cumulative accelerometer units were totaled over a 24-hour period to provide daily accelerometer units. Participants were assigned to one of two treatment groups: 6 weeks of placebo first with crossover to 6 weeks of isosorbide mononitrate, or 6 weeks of isosorbide mononitrate first with crossover to 6 weeks of placebo. The study drugs were prepared as 30-mg tablets of isosorbide mononitrate and matching placebo. During each 6-week period, participants were instructed to take no study drug for the first 2 weeks followed by one tablet (30 mg daily) for 1 week, two tablets (60 mg once daily) for 1 week, and four tablets (120 mg once daily) until the next study visit, for a treatment duration of at least 2 weeks and up to 4 weeks. After each 6-week period, participants returned to the study center to repeat end-point assessments. The primary outcome for the study was the comparison of average daily accelerometer units during the period in which participants were receiving the 120-mg dose of isosorbide mononitrate compared to the period in which participants received the placebo. Other secondary end points included the 6-minute walk distance and the post-walk Borg dyspnea score, scores on the Kansas City Cardiomyopathy Questionnaire and the Minnesota Living with Heart Failure Questionnaire, and NT-proBNP levels. In addition, participants completed a questionnaire indicating in which period (first, second, no preference) they felt better. Conclusions Participants were active for fewer hours of the day during the 120-mg phase of receipt of isosorbide mononitrate as compared with placebo. Furthermore, during all study-drug regimens combined (30 mg to 120 mg), participants were less active during receipt of isosorbide mononitrate as compared with placebo. There was no significant effect of isosorbide mononitrate on secondary outcomes.

  Study phs003548

• Prevention and Early Treatment of Acute Lung Injury (PETAL) Network - Functional, Imaging, and Respiratory Evaluation in CORAL (PETAL FIRE CORAL-BioLINCC)

  Data Access NOTE: Please refer to the “Authorized Access” section below for information about how access to the data from this accession differs from many other dbGaP accessions.Biospecimens: Access to Biospecimens is through the NHLBI Biologic Specimen and Data Repository Information Coordinating Center (BioLINCC). Biospecimens from PETAL FIRE CORAL include plasma and whole blood. Please note that use of biospecimens in genetic research is subject to a tiered consent and biospecimens may not be used to produce commercial products.Objectives: To examine the recovery from COVID-19 disease following acute hospitalization with an emphasis on functional, imaging, and respiratory evaluation, and assess the feasibility of conducting a larger study to evaluate variables associated with differential recovery.Background: The BLUE CORAL study, dbGaP phs003419, was intended to address the knowledge gaps and provide critical data to help guide clinical care, public health, and scientific efforts regarding SARS-CoV-2 (COVID-19) recovery. The understanding and treatment of long-term sequelae of COVID-19, referred to variously as post-acute sequelae of COVID-19 (PASC), post-acute COVID, long COVID, or long-haul COVID, is fundamental to patient recovery. These long-term consequences are common and increasingly recognized, although heterogeneous in manifestation, and can result in a failure to return to baseline level of health. At the time of the FIRE CORAL study, there were limited studies that collected objective assessments following hospital discharge for a wide spectrum of patients surviving COVID-19.Participants: FIRE CORAL enrolled adult participants as a subset of those enrolled in the BLUE CORAL study with a recent COVID-19 hospitalization and that completed the 1- or 3-month post-hospital telephone long-term outcomes assessment. The target enrollment for this pilot study cohort was 80 participants.Design: FIRE CORAL was a multicenter prospective cohort study of participants recovering from COVID-19 disease with in-person follow-up, as an extension of the BLUE CORAL study. The study consisted of a battery of assessments objectively measuring pulmonary function, abnormalities on lung imaging, and functional status. Participants were to attend and perform initial in-person testing at 3 to 9 months after hospital discharge. Participants with abnormal findings on pulmonary function testing or chest imaging during their initial assessment or those with persistent respiratory symptoms were eligible to repeat study procedures 3 months later with a subsequent visit at 12 months. All participants were invited to return for in-person follow up at 12 months after hospital discharge. Assessments included high-resolution chest CT scan without contrast, spirometry, lung volume assessment, diffusing capacity measured by single breath measurement, Six Minute Walk Test, Short Physical Performance Battery, St. George's Respiratory Questionnaire, and Functional Assessment of Chronic Illness Therapy-Fatigue scale. Demographic and hospitalization data are available as part of the BLUE CORAL study.The primary aim of the FIRE CORAL study was to examine the feasibility of conducting rigorous in-person follow-up testing of participants discharged from the hospital following COVID-19 illness to assist with planning for a larger study to evaluate variables associated with differential recovery. The secondary aim was to describe the pulmonary, imaging, and functional recovery following COVID-19 hospitalization in a diverse population of patients.

  Study phs004130

• Heart Failure Network - Imaging from Nitrate's Effect on Activity Tolerance in Heart Failure with Preserved Ejection Fraction (HFN NEAT-Imaging)

  Data Access NOTE: Please refer to the “Authorized Access” section below for information about how access to the data from this accession differs from many other dbGaP accessions.Objectives: To determine the effect of isosorbide mononitrate on daily activity in patients with heart failure and preserved ejection fraction.Background: Nitrates are commonly prescribed for symptom relief in patients with heart failure. Early studies in patients with heart failure with a reduced ejection fraction concluded that long-acting nitrates improves activity tolerance; however, approximately half of heart failure patients have preserved ejection fraction. The effects of nitrates in patients with heart failure and a preserved ejection fraction have not been extensively studied and the overall effect of nitrates on activity tolerance in such patients is uncertain.Subjects: There were a total of 110 patients enrolled with 51 patients assigned to receive isosorbide mono-nitrate first and placebo second, and 59 patients assigned to receive placebo first and isosorbide mononitrate second.Design: Enrolled subjects underwent baseline assessments, including echocardiography, quality-of-life scores, 6-minute walk test distance, and NT-proBNP levels. Subjects were also supplied with two kinetic activity monitors containing high-sensitivity triaxis accelerometers, to be worn 24 hours per day. The accelerometer measurements were expressed as arbitrary accelerometer units and stored every 15 minutes equaling 96 data points per day. The 15-minute cumulative accelerometer units were totaled over a 24-hour period to provide daily accelerometer units.Subjects were assigned to one of two treatment groups: 6 weeks of placebo first with crossover to 6 weeks of isosorbide mononitrate, or 6 weeks of isosorbide mononitrate first with crossover to 6 weeks of placebo. The study drugs were prepared as 30-mg tablets of isosorbide mononitrate and matching placebo. During each 6-week period, patients were instructed to take no study drug for the first 2 weeks followed by one tablet (30 mg daily) for 1 week, two tablets (60 mg once daily) for 1 week, and four tablets (120 mg once daily) until the next study visit, for a treatment duration of at least 2 weeks and up to 4 weeks. After each 6-week period, patients returned to the study center to repeat end-point assessments. The primary outcome for the study was the comparison of average daily accelerometer units during the period in which patients were receiving the 120-mg dose of isosorbide mononitrate compared to the period in which patients received the placebo. Other secondary end points included the 6-minute walk distance and the post-walk Borg dyspnea score, scores on the Kansas City Cardiomyopathy Questionnaire and the Minnesota Living with Heart Failure Questionnaire, and NT-proBNP levels. In addition, subjects completed a questionnaire indicating in which period (first, second, no preference) they felt better. Conclusions: Patients were active for fewer hours of the day during the 120-mg phase of receipt of isosorbide mononitrate as compared with placebo. Furthermore, during all study-drug regimens combined (30 mg to 120 mg), patients were less active during receipt of isosorbide mononitrate as compared with placebo. There was no significant effect of isosorbide mononitrate on secondary outcomes.

  Study phs004254

• 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

• A proof-of-concept study of sequential treatment with the HDAC inhibitor vorinostat following BRAF and MEK inhibitors in BRAFV600 mutated melanoma

  "Purpose: Development of resistance limits the clinical benefit of BRAF and MEK inhibitors (BRAFi/MEKi) in BRAFV600 mutated melanoma. It has been shown that short-term treatment (14 days) with vorinostat was able to initiate apoptosis of the resistant tumor cells. We aimed to assess the anti-tumor activity of sequential treatment with vorinostat following BRAFi/MEKi in patients with BRAFV600 melanoma who progressed after initial response to BRAFi/MEKi. Patients and Methods: Patients with BRAFi/MEKi resistant BRAFV600 melanoma were treated with vorinostat 360 mg QD for 14 days followed by BRAFi/MEKi. The primary endpoint was an objective response rate of progressive lesions of at least 30% according to RECIST 1.1. Secondary endpoints included progression-free survival (PFS), overall survival (OS), safety, pharmacokinetics of vorinostat and translational molecular analyses using ctDNA and tumor biopsies. Results: Twenty-six patients with progressive BRAFi/MEKi resistant BRAFV600 mutated melanoma received treatment with vorinostat. Twenty-two patients were evaluable for response. The ORR was 9% (one complete response for 31.2 months and one partial response for 14.9 months. Median PFS and OS were 1.4 and 5.4 months, respectively. Common adverse events were fatigue (23%) and nausea (19%). ctDNA analysis showed emerging secondary mutations in NRAS and MEK in eight patients at time of BRAFi/MEKi resistance. Elimination of these mutations by vorinostat treatment was observed in three patients. Conclusions: Intermittent treatment with vorinostat in patients with resistant BRAFV600 mutated melanoma is well tolerated. Although the primary endpoint of this study was not met, durable anti-tumor responses were observed in a minority of patients (9%). "

  Study EGAS00001007709

• Whole Transcriptome Sequencing of Resectable Stage III/IV Melanoma Evaluated After Starting Hu14.18-IL2 Predicts Outcome

  Background: We analyzed whole transcriptome sequencing in tumors from 23 patients with stage III or IV melanoma from a pilot trial of the anti-GD2 immunocytokine, hu14.18-IL2, to identify predictive immune and/or tumor biomarkers in melanoma patients at high risk for recurrence. Methods: Patients were randomized to receive the first of 3 monthly-courses of hu14.18-IL2 immunotherapy either before (Group A) or after (Group B) complete surgical resection of all known disease. Tumors were evaluated by histology and whole transcriptome sequencing. Results: We report here that tumor infiltrating lymphocyte (TIL) levels directly associate with relapse-free survival (RFS) and overall survival (OS) in resected tumors from Group A, where early responses to the immunotherapy agent could be assessed. TIL levels directly associated with a previously reported immune signature which associated with RFS and OS, particularly in Group A tumors. In Group A tumors there were decreased cell cycling gene RNA transcripts, but increased RNA transcripts for repair and growth genes. We found that outcome (RFS and OS) was directly associated with several immune signatures and immune-related RNA transcripts and inversely associated with several tumor growth-associated transcripts, particularly in Group A tumors. Most of these associations were not seen in Group B tumors. Conclusion: We interpret these data to signify that both immunologic and tumoral cell processes, as measured by RNAseq analyses detected shortly after initiation of hu14.18-IL2 therapy are associated with long term survival and could potentially be used as prognostic biomarkers in tumor resection specimens obtained after initiating neoadjuvant immunotherapy. Note: RNA sequences and expression data can be found at NCBI GEO GSE133713

  Study phs001947

• Germ Cell Tumor Molecular Heterogeneity Revealed through Analysis of Primary and Metastasis Pairs

  Purpose: While primary germ cell tumors (GCTs) have been extensively characterized, molecular analysis of metastatic sites has been limited. We performed whole-exome sequencing and targeted next-generation sequencing on paired primary and metastatic GCT samples in a patient cohort enriched for cisplatin-resistant disease. Experimental Design: Tissue sequencing was performed on 100 tumor specimens from 50 patients with metastatic GCT, and sequencing of plasma cell-free DNA (cfDNA) was performed for a subset of patients. Data is being provided for a subset of 10 patients whose samples were analyzed using whole-exome sequencing. Results: The mutational landscape of primary and metastatic pairs from GCT patients was highly discordant (68% of all somatic mutations were discordant). Whereas genome duplication was common and highly concordant between primary and metastatic samples, only 25% of primary-metastasis pairs had =50% concordance at the level of DNA copy number alterations (CNAs). Evolutionary-based analyses revealed that most mutations arose after CNAs at the respective loci in both primary and metastatic samples, with oncogenic mutations enriched in the set of early occurring mutations versus variants of unknown significance (VUS). TP53 pathway alterations were identified in nine cisplatin-resistant cases and had the highest degree of concordance in primary and metastatic specimens, consistent with their association with this treatment-resistant phenotype. Conclusions: Analysis of paired primary and metastatic GCT specimens revealed significant molecular heterogeneity for both CNAs and somatic mutations. Among loci demonstrating serial genetic evolution, most somatic mutations arose after CNAs but oncogenic mutations were enriched in the set of early occurring mutations as compared to VUS. Alterations in TP53 were clonal when present and shared among primary-metastasis pairs. Reprinted from pending publication, with permission from JCO Precision Oncology.

  Study phs002229

• Genomic Analyses of Germline and Somatic Variation in High-Grade Serous Ovarian Cancer

  The goal of this study was to identify and characterize germline and somatic genetic variation in women with high grade serous ovarian cancers treated at a single cancer center and their associations with relapse-free and overall survival. We conducted paired tumor/normal targeted next-generation sequencing of 577 genes in pathways of DNA repair, response to DNA damage, cell-cycle regulation, programmed cell death, MAPK, and P13K/AKT/MTOR signaling in 114 tumors from 71 women. In addition, we investigated single copy number alterations (SCNAs) and loss of heterozygosity in a subset of 61 tumors. We validated our results with data from ovarian tumors in TCGA. Our results were similar to other studies of high-grade serous carcinomas. As an example, we found that approximately one third of the tumors harbored loss of function variants in homologous recombination genes and that >90% had TP53 somatic mutations. Through GISTIC analysis of the OncoScan data on tumor DNA from 61 cases, we identified several regions of high copy number alterations including including NOTCH3 and PIK3R2 that were significantly associated with an increase in cancer recurrence and a reduction in overall survival. We identified few changes in mutation profiles where we had multiple tissues, either from multiple surgeries or from the primary site to metastatic sites within the same surgery. However, we did not investigate copy number alterations in multiple tissues from the same individuals, and so it may be that copy number alterations are more important. Data available through dbGAP will be the BAM files and the phenotypic data on the tumor samples, the age, race, ethnicity of the participants and their outcomes, and the Oncoscan OSCHP files.

  Study phs003198

• Chromothripsis in Patient WHIM-09

  We are studying the natural history, pathogenesis and treatment of patients with WHIM syndrome, an immunodeficiency disorder characterized by warts, hypogammaglobulinemia, recurrent infections and neutropenia usually due to autosomal dominant gain-of-function mutations in chemokine receptor CXCR4. We have identified a patient born with WHIM syndrome and the WHIM mutation CXCR4R334X who has been disease-free for 20 years and who lacks CXCR4R334X in myeloid cells, the cells that drive disease manifestations. She is a genetic and hematopoietic mosaic, since she still has the mutation in lymphoid cells and non-hematopoietic cells. Cytogenetics and microarray analysis revealed that the mechanism of loss of the mutation was deletion of the mutant allele from one copy of chromosome 2. Whole genome sequencing of patient neutrophil and skin fibroblast genomic DNA revealed that the mechanism of deletion was chromothripsis, a process of chromosome shattering resulting in deletions and rearrangements of the non-deleted chromosomal segments. In the patient, this process evidently occurred in a single hematopoietic stem cell (HSC), resulting in deletion of the disease allele CXCR4R334X and one copy of 163 other genes on chromosome 2. This HSC evidently acquired a growth advantage and repopulated the HSC population and the myeloid lineage. Consistent with this, studies using gene targeted mice in competitive bone marrow transplantation experiments revealed that selective Cxcr4 haploinsufficiency (inactivation of one copy of Cxcr4 and not of any other genes) was sufficient to confer a strong engraftment advantage over bone marrow cells from wild type mice as well as bone marrow cells from a mouse model of WHIM syndrome. These results suggest that CXCR4 knockdown may be a useful strategy to enhance bone marrow engraftment in the absence of toxic bone marrow conditioning regimens.

  Study phs000856