17524 results for "free coins in fc 26 Visit Buyfc26coins.com for latest FC 26 coins news..Y2KA"

in 30.65 milliseconds.

• POISED (Peanut Oral Immunotherapy: Safety, Efficacy, and Discovery)

  Phase 2 POISED (Peanut Oral Immunotherapy: Safety, Efficacy, Discovery) Study In this randomized, double-blind, placebo-controlled (DBPC) clinical trial, blinded placebo group received oat flour, whereas in active participants, dosage was built-up for over ~ 52 weeks and subsequently maintained on 4000 mg peanut protein, daily for next 52 weeks. 80 (98.77%) per-protocol active participants passed the food challenge at week 104. Subsequently, for 12 weeks, peanut ingestion was avoided in a randomized group of 51 blinded active participants (i.e., peanut avoidance group). 21 (41.2%) participants in the peanut avoidance group passed the 4000 mg double-blind, placebo-controlled food challenge (DBPCFC) without any allergic reaction at week 117, thus demonstrating sustained unresponsiveness. These 21 participants continued oral immunotherapy (OIT) for every three months and afterwards were allowed to continue peanut OIT discontinuation if they passed. 8 participants passed the DBPCFCs, 12 months after peanut discontinuation (week 156), i.e. they achieved long-term sustained unresponsiveness with no allergic reaction in response to food challenge. For detailed description, please refer to Chinthrajah et al., PMID: 31522849.

  Study phs003071

• Epigenome and transcriptome profiling of chronic lymphocytic leukemia patients

  Chronic lymphocytic leukemia (CLL) is characterized by substantial clinical heterogeneity, despite relatively few genetic alterations. To provide a basis for studying epigenome deregulation in CLL, we established genome-wide chromatin accessibility maps for 88 CLL samples from 55 patients using the ATAC-seq assay, and we also performed ChIPmentation and RNA-seq profiling for ten representative samples. Based on the resulting dataset, we devised and applied a bioinformatic method that links chromatin profiles to clinical annotations. Our analysis identified sample-specific variation on top of a shared core of CLL regulatory regions. IGHV mutation status – which distinguishes the two major subtypes of CLL – was accurately predicted by the chromatin profiles, and gene regulatory networks inferred for IGHV-mutated vs. IGHV-unmutated samples identified characteristic differences between these two disease subtypes. In summary, we discovered widespread heterogeneity in the chromatin landscape of CLL, established a community resource for studying epigenome deregulation in leukemia, and demonstrated the feasibility of chromatin accessibility mapping in cancer cohorts and clinical research.

  Study EGAS00001001821

• Ultrasensitive detection of minor allele fractions in maternal samples based on microhaplotype analysis

  Background: Tools for quantifying and studying genetic variation in heterogeneous cell populations have a limited sensitivity. However, many biological problems require ultrasensitive genetic deconvolution of cell mixtures. The detection of fetal cells in cervical samples from pregnant women presents such a challenge. Methods: Using deep sequencing of microhaplotype loci and analysis of the error profiles in genetically pure and mixed samples, we increase the sensitivity for minor allele detection and demonstrate the potential for paternal allele detection in cervical samples from pregnant women. Results: Using artificial DNA mixtures, we show that unique alleles can be readily identified in mixtures with a ratio of 1 in 10,000 (0.01%). By applying this method on ten non-invasive cervical samples from pregnant women we could identify the presence of paternal alleles in half of the samples. Unexpectedly, we demonstrate those alleles not to be of fetal origin but of sperm. Conclusions: We developed a novel method that can deconvolute genetic mixtures to at least 0.01%, which can be applied to study minor allele fractions in genetic mixtures and, for example, could aid in trophoblast cell detection in maternal blood or cervix. Our results demonstrate the importance of discriminating fetal and paternal alleles when analyzing cervical fetal cells and may pinpoint a potential cause of erroneous results in previous trophoblast isolation studies.

  Study EGAS00001007057

• Sporadic autism exomes reveal a highly interconnected protein network of de novo mutations

  It is well established that autism spectrum disorders (ASD) have a strong genetic component; however, for at least 70% of cases, the underlying genetic cause is unknown. Under the hypothesis that de novo mutations underlie a substantial fraction of the risk for developing ASD in families with no previous history of ASD or related phenotypes-so-called sporadic or simplex families-we sequenced all coding regions of the genome (the exome) for parent-child trios exhibiting sporadic ASD, including 189 new trios and 20 that were previously reported. Additionally, we also sequenced the exomes of 50 unaffected siblings corresponding to these new (n = 31) and previously reported trios (n = 19), for a total of 617 individual exomes from 209 families deposited in dbGaP. Here we show that de novo point mutations are overwhelmingly paternal in origin (4:1 bias) and positively correlated with paternal age, consistent with the modest increased risk for children of older fathers to develop ASD. Moreover, 39% (49 of 126) of the most severe or disruptive de novo mutations map to a highly interconnected beta-catenin/chromatin remodelling protein network ranked significantly for autism candidate genes. In proband exomes, recurrent protein-altering mutations were observed in two genes: CHD8 and NTNG1. Mutation screening of six candidate genes in 1,703 ASD probands identified additional de novo, protein-altering mutations in GRIN2B, LAMC3 and SCN1A. Combined with copy number variant (CNV) data, these results indicate extreme locus heterogeneity but also provide a target for future discovery, diagnostics and therapeutics.

  Study phs000482

• 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

• The African American Breast Cancer Epidemiology and Risk (AMBER) Consortium Study

  The AMBER Consortium Study was formed to pool interview data, questionnaire data, and biological samples from epidemiological studies of breast cancer in African-American women to discover the potential causes of early-onset and aggressive breast cancer in African-American women. AMBER is funded through a Program Project grant from the National Cancer Institute. Genetic data submitted to dbGaP come from participants in the Carolina Breast Cancer Study, Women's Circle of Health Study, and Black Women's Health Study. The P01 consists of four scientific projects; the aims include follow-up on previous GWAS findings for breast cancer susceptibility in AA women as well as investigation of SNPs in candidate genes in biologically plausible pathways. These SNPs were genotyped using DNA from 3130 African-American women with breast cancer and 3700 controls. Descriptions of the original studies that provided the data and samples for this collaborative study are given below. The Carolina Breast Cancer Study (CBCS): a North Carolina population-based case-control study of breast cancer, conducted in three phases. The current study phase, phase 3 (years 2008-2014), includes women residents in 44 counties. CBCS phases 1 and 2 were conducted in 24 counties. Breast cancer cases are identified using Rapid Case Ascertainment in cooperation with the NC Central Cancer Registry. Controls were identified for phases 1 and 2 only (1993-1996 and 1996-2001), using Division of Motor Vehicles lists for women under age 65 and Health Care Financing Administration lists for women 65 and older. Randomized recruitment was used to oversample AA women and women under age 50. In-depth interviews are conducted by study nurses in participants' homes to obtain information on potential risk factors for breast cancer. DNA samples have been obtained from most participants. Overall response rates for Phases 1 and 2 were 74% for AA cases and 54% for AA controls. Phase 3, conducted in 44 counties from 2008-2014, includes cases only. The response rate for AA cases in Phase 3 was 70.5%. The Women's Circle of Health Study (WCHS): a multi-site case-control study in New York City (NYC) and New Jersey (NJ) aimed at evaluating risk factors for early and aggressive breast cancer in women of AA and EA ancestry. Recruitment in NYC took place between January 2002 and December 2008 and involved hospital-based ascertainment of cases, while controls were identified through random digit dialing (RDD). Recruitment at the NJ site started in March 2006 and is ongoing. Phase I of the study ended in April 2012 and covered seven counties in NJ. WCHS2 includes two additional counties. Cases in NJ were identified from 2006 to 2012 by the NJ State Cancer Registry using rapid case ascertainment. Controls were initially recruited though RDD (2006 to 2010) and later through community-based efforts (2009-2012). In-person interviews ascertained data on established and suspected risk factors for breast cancer. DNA samples were obtained. Among eligible AA women, 75% in NY and 54% in NJ completed an interview and provided a biologic specimen. Black Women's Health Study (BWHS): an ongoing prospective cohort study of health and illness among U.S. black women, with a focus on cancer. The study began in 1995 when 59,000 AA women 21-69 years of age from across the United States completed a 14-page postal health questionnaire. The median age at entry was 38, and participants were residents of 17 states in mainland U.S.: Northeast, 28%; South, 30%; Midwest, 23%; West, 19%. The baseline questionnaire elicited information on a wide range of variables, including demographic factors, use of medical care, family history of breast cancer, reproductive and medical history, cigarette and alcohol use, weight, height, waist and hip circumference, medication use, diet, and exercise. Biennial follow-up questionnaires ascertain new cases of breast cancer and other illnesses and update covariate information. Medical record and cancer registry data are sought for all participants who report a diagnosis of breast cancer. As of 2014, approximately 80% of the baseline cohort have completed follow-up. DNA samples were obtained from about 50% of participants. BWHS data for the AMBER consortium were prepared as a nested case-control study, with controls frequency-matched to cases on year of birth, geographic region, and most recent questionnaire completed prior to the end of the at-risk period.

  Study phs000669

• DHODH is a synthetic-lethal vulnerability in BCOR-deficient acute myeloid leukemia

  Acute Myeloid Leukemia (AML) remains challenging to treat, especially in cases with mutations in the BCL-6 co- repressor (BCOR), which are associated with poor prognosis and chemo-resistance. In this study, we reveal a synthetic lethal interaction between BCOR and dihydroorotate dehydrogenase (DHODH). We demonstrate that BCOR-deficient cells have a heightened sensitivity to DHODH inhibitors such as brequinar and leflunomide, that are already in clinical use. We confirm that DHODH inhibition selectively induces cell death in BCOR-mutant cells in multiple cellular models, in malignant and non-malignant cells, through chemical and genetic manipulation. Interestingly, we find that the dependency on DHODH does not stem from its role in de novo pyrimidine biosynthesis disruption. Rather, DHODH’s role in the electron transport chain, essential for mitigating reactive oxygen species, may be the physiological vulnerability that pushes BCOR-mutant cells toward cell death when DHODH is inhibited. DHODH inhibitors could be repurposed as targeted therapies for BCOR-mutant tumors, offering a promising strategy for precision medicine in AML and other cancers.

  Study EGAS50000001060

• DHODH is a synthetic-lethal vulnerability in BCOR-deficient acute myeloid leukemia

  Acute Myeloid Leukemia (AML) remains challenging to treat, especially in cases with mutations in the BCL-6 co- repressor (BCOR), which are associated with poor prognosis and chemo-resistance. In this study, we reveal a synthetic lethal interaction between BCOR and dihydroorotate dehydrogenase (DHODH). We demonstrate that BCOR-deficient cells have a heightened sensitivity to DHODH inhibitors such as brequinar and leflunomide, that are already in clinical use. We confirm that DHODH inhibition selectively induces cell death in BCOR-mutant cells in multiple cellular models, in malignant and non-malignant cells, through chemical and genetic manipulation. Interestingly, we find that the dependency on DHODH does not stem from its role in de novo pyrimidine biosynthesis disruption. Rather, DHODH’s role in the electron transport chain, essential for mitigating reactive oxygen species, may be the physiological vulnerability that pushes BCOR-mutant cells toward cell death when DHODH is inhibited. DHODH inhibitors could be repurposed as targeted therapies for BCOR-mutant tumors, offering a promising strategy for precision medicine in AML and other cancers.

  Study EGAS50000001108

• NHLBI TOPMed: Heart and Vascular Health Study (HVH)

  Objectives The Heart and Vascular Health Study (HVH) is a case-control study of risk factors for the development of myocardial infarction (MI), stroke, venous thrombosis (VT), and atrial fibrillation (AF). The study setting is Group Health, an integrated health care delivery system in Washington State. Only VT cases and early-onset AF cases are included as part of TOPMed. Background The HVH study originated in 1988 with the examination of risk factors for MI. Over the ensuing years, the study has been funded by a series of grants which have added case subjects with stroke, VT, and AF. Study aims focused on the associations of medication use with cardiovascular events, and starting in 1997, the study aims expanded to include genetic associations with cardiovascular disease. Participants recruited in 2009 or later who provided blood samples for genetic analysis were asked for consent to deposit genetic and phenotypic data in dbGaP. Design As part of the HVH study, case subjects were identified by searching for ICD-9 codes consistent with MI, stroke, VT, or AF, and medical records were reviewed to confirm the diagnosis. Control subjects were identified at random from the Group Health enrollment and were matched to MI cases. All subjects have an index date. For cases, the index date was assigned as the date that the cardiovascular event (MI, stroke, VT, or AF) came to clinical attention. For controls, the index date was a random date within the range of the case index dates. For both cases and controls, information was collected from the inpatient and outpatient medical record, by telephone interview with consenting survivors, and from the Group Health pharmacy and laboratory databases. Consenting participants provided a blood specimen. Subjects Only VT and early-onset AF cases from HVH are included in TOPMed. Within the HVH study, VT and AF cases were diagnosed in both inpatient and outpatient settings, and only incident cases are eligible for inclusion in TOPMed. Genetic Research Genetic factors underlying cardiovascular disease are studied using DNA isolated from the blood samples. Phenotype data for HVH study participants are available through dbGaP phs001013.

  Study phs000993

• Genome-wide Association Study for Non-syndromic Clefts in the African Population: CIDR

  The focus of this project is to identify genetic variants that are associated with orofacial clefts in African populations in sub-Saharan Africa. Most genetic studies of CLP (including the vast majority of GWAS) have been conducted in populations of European origin with only a few focused on Asian or African populations. We choose to study the genetics of these complex traits in African populations because, African populations have the greatest genetic variation amongst the various populations in the world by virtue of being the primary ancestral population to modern humans (Cavalli-Sforza and Feldman, 2003; Ramsay et al., 2011). Therefore, the potential for finding novel loci for CLP is quite high. To date 6 genome wide association studies (GWAS) for cleft lip with or without cleft palate (CL/P) have been conducted and 18 risk loci identified (Birnbaum et al., 2009; Grant et al., 2009 ; Beaty et al., 2010; Mangold et al., 2010; Ludwig et al., 2012; Sun et al., 2015). All these studies have either been conducted in European populations, Asian populations or both. There is currently no published GWAS for clefts in African populations. African populations represent a novel and richly productive populations for genetic and environmental exposure studies for CL/P. Investigating the presence of genetic variants in diverse population groups can identify novel variants and candidate genes that are population specific. Environmental factors may also increase the risks in certain population groups due to genetic susceptibility and/or specific exposures. Understanding the role these susceptibility genes play in the effects of environmental risk factors can inform strategies designed towards reducing the outcome of these complex traits, e.g. through the modification of the environmental influences. The study population comprises a large number of individuals (3205 individuals) from Africa (Ghana, Ethiopia and Nigeria). There are cases, case triads (nuclear families), as well as controls with no history of OFC nor other developmental defects.

  Study phs001090