12030 results for "cheap reliable fc 26 coins Visit Buyfc26coins.com for latest FC 26 coins news..H1Kx"

in 30.48 milliseconds.

• Dissociation of solid tumour tissues with cold active protease for single-cell RNA-seq minimizes conserved collagenase-associated stress responses

  Background Single-cell RNA sequencing (scRNAseq) is a powerful tool for studying complex biological systems, such as tumour heterogeneity and tissue microenvironments. However, the sources of technical and biological variation in primary solid tumour tissues and patient-derived mouse xenografts for scRNAseq, are not well understood. Here, we used low temperature (6°C) protease and collagenase (37°C) to identify the transcriptional signatures associated with tissue dissociation across a diverse scRNAseq dataset comprising 128,481 cells from patient cancer tissues, patient-derived breast cancer xenografts and cancer cell lines.Results We observe substantial variation in standard quality control (QC) metrics of cell viability across conditions and tissues. From FACS sorted populations gated for cell viability, we identify a sub-population of dead cells that would pass standard data filtering practices, and quantify the extent to which their transcriptomes differ from live cells. We identify a further subpopulation of transcriptomically “dying” cells that exhibit up-regulation of MHC class I transcripts, in contrast with live and fully dead cells. From the contrast between tissue protease dissociation at 37°C or 6°C, we observe that collagenase digestion results in a stress response. We derive a core gene set of 512 heat shock and stress response genes, including FOS and JUN, induced by collagenase (37°C), which are minimized by dissociation with a cold active protease (6°C). While induction of these genes was highly conserved across all cell types, cell type-specific responses to collagenase digestion were observed in patient tissues. We observe that the yield of cancer and non-cancer cell types varies between tissues and dissociation methods.Conclusions The method and conditions of tumour dissociation influence cell yield and transcriptome state and are both tissue and cell type dependent. Interpretation of stress pathway expression differences in cancer single cell studies, including components of surface immune recognition such as MHC class I, may be especially confounded. We define a core set of 512 genes that can assist with identification of such effects in dissociated scRNA-seq experiments.

  Study EGAS00001003753

• Multi-Site Collaborative Study for Genotype-Phenotype Associations in Alzheimer's disease and Longitudinal follow-up of Genotype-Phenotype Associations in Alzheimer's disease and Neuroimaging component of Genotype-Phenotype Associations in Alzheimer's disease

  GenADA is a multi-site collaborative study, involving GlaxoSmithKline Inc and nine medical centres in Canada, to develop a dataset containing 1000 Alzheimer's disease patients and 1000 ethnically-matched controls in order to associate DNA sequence (allelic) variations in candidate genes with Alzheimer's disease phenotypes. The study consists of both retrospective and prospective components, that is, patients with an existing diagnosis of Alzheimer's disease as well as newly diagnosed patients were enrolled in the study. Thus, clinical data was retrospectively or prospectively obtained on Day 1 of entry into GenADA. Where possible, biological relatives with Alzheimer's (up to third degree relationship such as cousins) and unaffected siblings of AD cases were also recruited. Note that recruitment numbers for biological relatives were lower than expected and genotypic data has not been submitted to dbGap for these subjects. The purpose of this study is: To identify DNA sequence variations (genotype) in candidate genes that are associated with the clinical symptoms and behavioural features of Alzheimer's disease (phenotype), which differ between study participants with and without the disease. To identify other genotype-phenotype associations in cognitively impaired study participants such as age of onset, family history, rate of cognitive decline, patterns of behavioural/psychiatric non-cognitive symptoms factors, response to treatment co-morbid conditions, and risks/exposure. The final subject recruitment for this study included 875 Alzheimer's disease patients, 850 ethnically-matched controls, and 37 family members. GenADA LONG is a longitudinal assessment to the original GenADA study. Eligible subjects were recruited from five of the nine memory clinics that participated in the GenADA study. Mild to moderate AD participants, a matched subset of controls, and biological related siblings (both affected and unaffected) or other blood relatives affected with AD, were initially examined a minimum of 12 months from recruitment into the original GenADA study, then at two further intervals of 12 and 18 months after time of entry into GenADA LONG. This enables an evaluation of the disease progression in AD patients and a determination of whether controls show evidence of cognitive decline. The overall goal of this extension study is to identify genetic differences and environmental influences that modulate the age of onset of the disease, the course of the disease, and/or biomarkers for neurodegenerative processes. Three of the five memory clinics that participated in the GenADA LONG study recruited eligible patients into GenADA Imaging. A concurrent neuroimaging sub-study was conducted at three of the five memory clinics participating in GenADA LONG. Eligible AD cases with mild to moderate AD, who were recruited into the original GenADA study and participated in the GenADA LONG extension study, were enrolled. Additionally, controls that showed signs of cognitive decline, as part of the assessment in GenADA LONG, were imaged at baseline, 12 and 18 month scanning intervals. The objective of this study is to find genes that: affect changes in AD brain volume measure by magnetic resonance in order to investigate how well change in brain volume predicts other key clinical measures in AD, such as neurodegenerative scales; that correlate changes in brain volume for other genotype-phenotype associations in cognitively impaired study participants; and that correlate with other clinically applicable magnetic resonance measures of pathology that can be conducted at the same time as structural volume measures, and are complementary to the volume measures. The ultimate aim of this research is to obtain a better understanding and definition of Alzheimer's Disease in order to develop new improved medicines.

  Study phs000219

• 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

• Prematurity and Respiratory Outcomes Program (PROP) Core Database Protocol (PROP-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. Objectives: The Prematurity and Respiratory Outcomes Program (PROP) was performed to identify suitable predictors of respiratory outcomes that may serve as surrogate endpoints in future trials of prevention and therapy of respiratory diseases in preterm infants.Background: Acute and chronic respiratory morbidities are common in premature births, and can pose significant risk to the infant's health, particularly during the first two years of life. One such condition is bronchopulmonary dysplasia (BPD) where infants require oxygen therapy due to abnormal repair and impaired lung development after acute lung injury. BPD poses a high mortality risk, even in infants that survive the initial hospitalization. Regardless of BPD diagnosis, preterm infants frequently return for medical care due to symptoms of post-prematurity respiratory disease (PRD), which includes intermittent or chronic wheezing, cough without cold, poor growth, apnea and cyanosis, and lower respiratory tract infections. Impaired lung function can persist into adulthood, contributing to chronic respiratory diseases including asthma and emphysema.However, at the time of the PROP study, there were no objective measures to predict which preterm infants would have persistent respiratory problems after discharge from the hospital. Furthermore, improved survival rates of premature infants and the high prevalence of lasting respiratory morbidities highlight the need for more comprehensive strategies to address both short-term and long-term respiratory complications. Thus, the Prematurity and Respiratory Outcomes Program (PROP) was formed to investigate multiple research hypotheses on the molecular mechanisms that contribute to respiratory disease risk of premature neonates over the first year of life. Specifically, PROP investigators hypothesized that in survivors of extreme prematurity to 36 weeks postmenstrual age (PMA), specific biologic, physiologic and clinical data obtained during the initial hospitalization will predict respiratory morbidity between discharge and 1 year corrected age. Participants: A total of 835 infants were enrolled.Design: PROP was a collaboratively developed multicenter prospective cohort study of very preterm infants from birth through the time of discharge from the NICU and up to one year corrected age.Clinical data included maternal and infant demographics, co-morbidities, and daily infant respiratory, nutritional, and medication data until discharge. These were prospectively collected from birth using medical record review and family interviews. After discharge, phone interviews were conducted with the infant's main caregiver at 3, 6, 9 and 12 months corrected age to assess domains of respiratory morbidity. At 6 and 12 months corrected age, a survey of environmental respiratory irritant exposures and an assessment for gastroesophageal reflux disease were also completed. A standardized physical exam was performed at 36-40 weeks PMA and again at one year corrected age. The exam focused on anthropometrics, vital signs, and respiratory system signs. At 34-41 weeks PMA and within one week of anticipated discharge based on physiologic stability, a set of non-invasive respiratory assessments were performed to assess physiologic biomarkers in infants that were not mechanically ventilated or receiving non-invasive positive pressure ventilation. Respiratory inductance plethysmography (RIP) was performed before and after inhaled albuterol to assess potential airway reactivity. During the RIP study, continuous pulse oximetry was performed during quiet sleep in order to analyze oxygen desaturations and apneas. Standardized oxygen requirement challenge tests were performed at about 36 weeks PMA, and at about 40 weeks PMA if the infant was still hospitalized and was not eligible for, or failed, the previous challenge. Failure was defined as SpO2 20 seconds at any point in the testing. Infants breathing ambient air or that passed the 36 week challenge test underwent a hypoxia challenge consisting of a 15-minute trial of FiO2 of 0.15. Failure was defined as SpO2 The primary outcome was respiratory morbidity, as measured by the presence or absence of substantial post-prematurity respiratory disease (PRD) up to one year corrected age. PRD was classified as a positive response in at least one of four morbidity domains during at least two separate parental interviews. The domains were respiratory medications, hospitalizations for cardiopulmonary cause, respiratory symptoms, and home technology dependence (oxygen, ventilator, or CPAP/BiPAP). Mortality from a respiratory cause was also incorporated.

  Study phs004117

• All you need to know about our new DAC Portal

  With the DAC Portal, it is possible to streamline the process of managing access to sensitive data, ensuring that researchers have the necessary resources to advance scientific discovery while maintaining the highest standards of data protection and privacy. We know that, as a new tool, its first use can be complex. For this reason, in this article we will try to show all the elements of interest. Enjoy! Credentials: who needs to create a new user to access the DAC Portal and who doesn't? Only new users (since September the 12th) need to create an EGA account to access the DAC Portal. The EGA team went one step ahead by creating EGA accounts for former DAC members to login to the DAC Portal. These accounts are linked to the personal email used in the DAC structure: To check the linked email, DAC members can paste the DAC ID right after this link: https://metadata.ega-archive.org/dacs/ (e.g. https://metadata.ega-archive.org/dacs/EGAC00001002543) In case of password oblivion, it is possible to set a new one. All the process is channelled through the personal email. Some DAC members may be interested in updating the DAC email. This action can be done contacting our Helpdesk team. For the correct functioning of the DAC Portal, users must add the missing information of the DAC Profile. For a deeper dive, check out our documentation. The first step: knowing your workspace on the Portal Once logged in to the platform using the EGA User credentials, note the sections available: DACs and Policies. In the first one it is possible to check all user's registered DACs by default. It provides a comprehensive overview of each DAC, including its EGA accessions (EGAC), title, status, and the number of data access requests associated with each DAC. Whereas the Policies section is where users can manage and view all their registered policies, along with their associated EGA accessions, links, and titles. A drop-down menu is available with shortcuts to the most useful pages in the top right corner. It is possible to check DACs and policies, as well as creating new ones. In this menu, users can also contact the Helpdesk team using the “Need Help?” section to make inquiries about DACs and policies. Comprehending the DACs list & making the most of all the features Colours are crucial in the DAC's section as they will indicate the user role and the status in every committee, namely: Yellow: you are the administrator of the DAC and have full control to add other contacts, modify the content, and manage data access requests. Orange: you are a member of the DAC and have the authority to manage data access requests but cannot make any changes to the content. Blue: you have been invited to join the DAC and need to either accept or decline the invitation. Grey: the DAC is currently pending validation by the EGA Helpdesk team. Red: the DAC has been declined by the EGA Helpdesk team. Discover more information on how to view the message from Helpdesk containing the declination reason or how to validate or reject a DAC invitation by taking the tour of the DAC Portal. How to create, register and edit a DAC Creating a DAC is an easy process that only requires users to complete the necessary information. After that, the EGA Helpdesk team will review the proposal and validate the proposal. Once the DAC is validated it is possible for authorised users with admin role to edit it at any time, ensuring that all information and contacts associated with the committee is accurate and up to date. Membership management is controlled by searching for the EGA user looking for their username, email, or organisation. Please, note that for a person's details to appear in this search engine, they must have registered as a EGA user. Data Access Committee administrators manage two types of permissions that apply to contacts: Main contact and Role. Both can be modified at any time: Main contact refers to the primary person we firstly contact for any inquiry about the DAC (please, note that we can contact all DAC members, and this refers to the person we will contact first). Role defines the actions that can be taken by each contact. There are two possible status, admin and member, details of which can be found in the Take the Tour. Keep in mind that, to save the modifications, it is always necessary to click on “Update”. Moreover, it is also possible to delete any contact in a DAC whenever it is needed. The data request process: how to manage access requests The data request process is now channelled through the EGA website. Once a user sends a request access, the petition will go directly to the DAC Portal profile of the DAC members liked to the requested dataset. Whenever a request is received, a sand clock symbol will be displayed next to the DAC responsible for the dataset involved. By clicking on the DAC, it is possible to discover more information about requester(s). In this section, DAC Portal users will also be able to modify the display of the data access requests. It is possible to group requests by dataset accession or username, depending on the user preferences. Additionally, it is possible to isolate specific requests by user or dataset. To accept a request, users must slide the button to the right. Once the button turns green, it signifies that the request is accepted; the requester will be granted access to the requested dataset. To make lives easier, we have implemented a “Select all” button to easily accept or revoke multiple requests at once. To decline requests, it is necessary to slide the button to the left. A red button means the requester will not be granted access to the dataset. The DAC Portal will always ask to submit the reason why the data access was denied. Please, note that any decision, grant or denial, must be confirmed clicking the "Apply" button. This will update the status of the request and notify the requester accordingly. Taking control of the activity in the DAC Portal: checking the requests history The History button is a useful feature that allows users to access a list of all the requests that have been granted. This is especially useful for auditing purposes, as it enables to keep track of who has been granted access to the data and when. To facilitate control for those users with several requests we have included a filtering option. It allows to filter requests by user, mail, dataset, EGA ID, and date (these are combinable to boost the search). Don't forget about policies: creation, management, and update Similarly to the DACs section, in the Policies one users can manage and view all their registered policies. By clicking on any policy, it is possible to view its details as well as making any necessary updates or modifications. The sheets symbol and its adjacent number indicate the quantity of objects using a policy. By clicking in the location symbol users will go directly to the DAC page on the DAC Portal to see more information about that DAC. DAC Portal users can create new policies. The first step requires to link the policy to a registered DAC. After defining the title, users can either add a link to an external URL containing terms & conditions or write the policy content directly on the DAC Portal. Keep in mind that both options can be included. Data Use Ontology (DUO) codes can be added to new policies. These codes are used to specify the permitted and prohibited uses of the data. Please, note that some of them require a modifier to provide additional specificity. Find out more by checking out this specific content on the DAC Portal Tour. Policies can be modified at any given time by clicking on one registered policy, which will display the current information.

  Blog new-dac-portal

• Cellular Diversity of the Developing Human Cerebral Cortex

  We sought to characterize cellular heterogeneity in the human cerebral cortex at a molecular level during cortical neurogenesis. We captured single cells and generated sequencing libraries using the C1TM Single-Cell Auto Prep System (Fluidigm), the SMARTer Ultra Low RNA Kit (Clontech), and the Nextera XT DNA Sample Preparation Kit (Illumina). We performed unbiased clustering of the single cells and further examined transcriptional variation among cell groups interpreted as radial glia. Within this population, the major sources of variation related to cell cycle progression and the stem cell niche from which radial glia were captured. We found that outer subventricular zone radial glia (oRG cells) preferentially express genes related to extracellular matrix formation, migration, and stemness, including TNC, PTPRZ1, FAM107A, HOPX, and LIFR and related this transcriptional state to the position, morphology, and cell behaviors previously used to classify the cell type. Our results suggest that oRG cells maintain the subventricular niche through local production of growth factors, potentiation of growth factor signals by extracellular matrix proteins, and activation of self-renewal pathways, thereby contributing to the developmental and evolutionary expansion of the human neocortex. For study version 2, we have updated this data set to include additional primary cells that we infer to represent microglia, endothelial cells, and immature astrocytes, as well as additional cells from the developing neural retina, and from iPS-cell derived cerebral organoids. The genes distinguishing these cell populations may reveal biological processes supporting the diverse functions of these cell types as well as vulnerabilities of specific cell types in human genetic diseases and in viral infections. For study version 3, we have updated the data set to include additional primary cells, including those published in Nowakowski et al., 2017 (PMID:29217575). For study version 4, we have additionally performed parallel analyses of transcriptomes and physiological responses of 476 single cells isolated from developing human cortex. As a result, we were able to identify physiological response profiles of specific progenitor and neuronal cell types during human cortical development.For study version 5, we have additionally performed bulk RNA sequencing of organotypic primary cultures from the developing human cortex with or without exposure to SARS-CoV-2 to understand the infectability and transcriptomic effects of SARS-CoV-2 on the developing human cortex.For study version 6, we investigated the impact of LIFR signaling on neural proliferation and differentiation of human oRG cells. Specifically, we isolated oRG cells from the primary developing neocortex and cultured them for four weeks with and without LIF treatment. We then performed single-cell RNA sequencing using the Chromium Single Cell 3&#8217; Reagent Kits (v3.1, Dual index) from 10x Genomics to understand the molecular and cellular changes of oRG differentiation upon LIF treatment.

  Study phs000989

• Using Genomics to Reduce Breast Cancer Disparities in the African Diaspora

  Differences in breast cancer incidence and mortality rates between North American Caucasian and African American women are well-described and transcend socioeconomic issues. Black women are diagnosed with breast cancer at a younger median age; have more clinically aggressive disease and stage-for-stage; and have higher mortality rates than age-matched Caucasian women. Black women in West Africa, the origin of the slave trade in the US in the 19th century and thus the founder population for most African Americans, have even higher rates of early-onset, poor-prognosis breast cancer than African American women. Racial difference in the distribution of intrinsic molecular subtypes has been well characterized in the US and throughout the African Diaspora as well. Despite the large efforts on characterizing racial/ethnic differences, however, the reasons women of African ancestry are disproportionately affected by breast cancer incidence and mortality remain poorly understood - largely due to paucity of data on inherent genomic differences that contribute to the disparities in incidence and progression of breast cancer across populations. West Africa Breast Cancer Study (WABCS) is an initiative that aims to comprehensively understand the genetic architecture of breast cancer in West Africans, the founder population of a large proportion of black women in the United States. The objective of the study was to provide a better understanding of the molecular genetic factors that influence prognosis in Nigerian breast cancer patients, and determine which of these alterations may be amenable to available therapy. To that end, we examined the molecular features of breast cancers of indigenous African women using a combination of whole-genome, whole-exome, and transcriptome sequencing (WGS, WES, and RNA-seq) on 194 tumors from Nigerian patients. The goal of this project was to obtain answers to two related research questions using an unscreened population without genetic admixture in Nigeria: 1) why are women of African ancestry more likely to develop aggressive young onset breast cancer? 2) What are the associated genomic and non-genomic risk factors? We hypothesize that the genomic determinants of breast cancer molecular subtypes in women of African ancestry are also molecular drivers of tumor progression and represent targets for interventions to improve clinical outcomes and close the mortality gap. By identifying causal links between genetic variants that promote aggressive tumor progression in Nigerian women in comparison to women from different population found in TCGA and ICGC, the present dataset will have significant public health impact on millions of women in the African Diaspora. The potential to identify novel pathways for interventions to reduce the increasing mortality gap between women of African and European ancestry is huge

  Study phs001687

• Metagenomic Analysis of the Structure and Function of the Human Gut Microbiota in Crohn's Disease

  Inflammatory bowel diseases (IBD), such as Crohn&#39;s disease, are chronic, immunologically mediated disorders that have severe medical consequences. The current hypothesis is that these diseases are due to an overly aggressive immune response to a subset of commensal enteric bacteria. Studies to date on IBD have suggested that the disorder may be caused by a combination of bacteria and host susceptibility; however the etiologies of these diseases remain an enigma. In this application, we propose to develop and demonstrate the ability to profile Crohn&#39;s disease at an unprecedented molecular level by elucidation of specific biomarkers (bacterial strains, genes, or proteins) that correlate to disease symptoms. To achieve this goal, we will employ a multidisciplinary approach based on metagenomic and metaproteomic molecular tools to elucidate the composition of the commensal microbiota in monozygotic twins that are either healthy or exhibit Crohn&#39;s disease (for concordant, both are diseased; for discordant, one is healthy and one is diseased). The central hypotheses of this proposal are (1) that specific members and/or functional activities of the gastrointestinal (GI) microbiota differ in patients with Crohn&#39;s disease as compared to healthy individuals, and (2) that it will be possible to elucidate microbial signatures which correlate with the occurrence and progression of this disease by integration of data obtained from 16S rRNA-based molecular fingerprinting, metagenomics, and metaproteomics approaches. To address these hypotheses, three specific aims are proposed: 1) Obtain data on community gene content (metagenome) in a subset of healthy twins and twins with Crohn&#39;s Disease to assess potential differences in the metabolic capabilities of the gut microbiota associated with CD, 2) Obtain data on community protein content (metaproteome) in a subset of healthy twins and twins with Crohn&#39;s Disease to assess the state of expressed proteins associated with CD, 3) Apply various statistical clustering and classification methods to correlate/associate microbial community composition, gene and protein content with patient metadata, including metabolite profiles and clinical phenotype. The ultimate goal of these efforts is to identify novel biomarkers for non-invasive diagnostics of CD and to eventually identify drug targets (i.e. bacterial strains) for cure or suppression of disease symptoms. PUBLIC HEALTH RELEVANCE: This study aims to unravel the contribution of the bacteria that normally inhabit the human gastrointestinal tract to Crohn&#39;s disease by using a multidisciplinary approach to study changes in the structure and function of gut microbial communities in three sets of patient cohorts who have Crohn&#39;s disease. These results will be compared with those obtained from the study of healthy individuals and have the potential to identify new biomarkers of disease severity, location, and progression.

  Study phs000257

• Prevention and Early Treatment of Acute Lung Injury Network - Vitamin D to Improve Outcomes by Leveraging Early Treatment (PETAL VIOLET-BioLINCC)

  Data Access NOTE: Please refer to the "Authorized Access" section below regarding accessing data through the BioData Catalyst ecosystem. The data from this accession is not available for download through dbGaP. Biospecimens: Access to Biospecimens is through the NHLBI Biologic Specimen and Data Repository Information Coordinating Center (BioLINCC). Biospecimens from PETAL VIOLET include Plasma and Whole Blood. Please note that use of biospecimens in genetic research is subject to a tiered consent. Specimens may not be used to produce commercial products.Objectives: To evaluate the effect of short-term vitamin D supplementation on mortality among critically ill patients with a vitamin D deficiency.Background: Observational data indicate that vitamin D deficiency is common among critically ill patients and constitutes a potentially modifiable risk factor associated with longer lengths of stay in the hospital and intensive care unit (ICU), lung and other organ injury, prolonged mechanical ventilation, and death. In a previous phase 2 trial, vitamin D supplementation administered to vitamin D-deficient, critically ill patients was associated with lower observed mortality than placebo at 28 days and at 6 months. Because of the need for a larger, phase 3 trial, the PETAL-VIOLET study was initiated to determine if early administration of high-dose vitamin D3 would reduce all-cause mortality among critically ill patients with a vitamin D deficiency.Participants: 1360 patients underwent randomization, 690 were assigned to the vitamin D group and 668 were assigned to the placebo group. Of the 1078 patients confirmed to have a vitamin D deficiency by liquid chromatography-tandem mass spectrometry (LC-MS-MS), 538 had been assigned to the vitamin D group and 540 had been assigned to the placebo group.Design: PETAL-VIOLET was a multicenter, double-blind, placebo-controlled, phase 3 trial. Patients were enrolled within 12 hours after the clinician's decision to admit the patient to the ICU from the emergency department, hospital ward, operating room, or outside facility. Patients were tested for vitamin D deficiency, with a threshold of plasma 25-hydroxyvitamin D level of less than 20 ng per milliliter. Patients were randomly assigned in a 1:1 ratio, stratified according to site, to receive either a single enteral (administered orally or through a nasogastric or orogastric tube) dose of 540,000 IU of vitamin D3 or matched placebo, in liquid form, administered within 2 hours after randomization.Conclusions: After the first interim analysis, the data and safety monitoring board recommended that the trial be stopped for futility.A single 540,000 IU enteral dose of vitamin D3 administered early during critical illness rapidly corrected vitamin D deficiency but did not provide an advantage over placebo with respect to mortality or other clinically important end points.

  Study phs003879

• A Phase I Study of the Treatment of Recurrent Malignant Glioma with CAN-3110 (AKA rQNestin34.5v.2), a Genetically Engineered HSV-1 Virus

  This study is a "first-in-human" phase 1 trial of recurrent, IDH wild-type glioblastoma (rGBM) patients treated with CAN-3110 (aka rQNestin34.5v.2), a genetically modified oncolytic herpes simplex virus 1 (HSV-1). The study was a 3+3 dose-escalation study starting at a single intra-tumoral injection of 106 PFU CAN-3110 going up to 1010 PFU in half-log increments (cohorts 1-9). An expansion cohort (cohort 10) was treated with 109 PFU injected into up to 5 sites within a single tumor. Principal findings of the study conclude that:CAN-3110 was safe at all tested doses (no dose-limiting toxicities reached)HSV-1 seropositive patients survived significantly longer than HSV-1 seronegative patients in this study - longer than expected based on historical rGBM controlsHSV-1 seropositive patients were significantly more likely to clear CAN-3110 (HSV-1) antigen from their tumors based on immunohistochemical stainingCAN-3110 treatment-induced CD8+/CD4+ T-cell recruitment to injected tumor sites altered TCR beta diversity in both tumor infiltrating leukocytes (TILs) and PBMCs, and initiated changes in specific TCR beta clonotypes and immune gene signatures which were associated with post-treatment survival.Data provided in dbGaP for this study include:Bulk RNA-Seq data for 13 pre/post-treatment pairs of rGBM tumors corresponding to 12 unique patients (patient 28 was treated with CAN-3110 at two different timepoints). This data is provided as raw sequencing reads (.fastq), kallisto pseudoalignment transcript-level read counts (abundance.tsv files), gene-level abundance matrix (Gene_Level_Expression_Matrix.tsv), and immune gene signature scores matrix (Immune_Gene_Signatures_Matrix.tsv). Sequencing was performed as paired 150bp sequencing on NovaSeq6000 S4 Illumina flow cells. Library preparation varied by batch as described in the included RNAseq_Metadata.xlsx table.TCR beta DNA sequencing performed by Adaptive Biotechnologies for 21 pre/post-treatment pairs of rGBM tumors and PBMCs representing 20 unique patients (patient 28 was treated with CAN-3110 at two different timepoints). Note that all tumor pairs with TCR beta sequencing data also have available bulk RNA-Seq data. The TCR beta sequencing data is provided as an excel spreadsheet (TCRbeta_Sample_Overview.xslx), which provides a broad level summary of the sequencing on a per-sample basis (# of TCRbeta templates, T cell fraction, TCR beta diversity metrics, etc.) and as a large tab separated value file (Full_TCRbeta_Rearrangement_Details.tsv), which provides information per sample at the level of each unique TCR beta sequence (amino/nucleic acid sequence, VDJ gene usage, etc.).An excel table of de-identified metadata for the patients involved in this study.

  Study phs003378