11947 results for "division 2 coins fc 26 Visit Buyfc26coins.com Kupiłem(a) duży pakiet monet FC 26 i dostałem(a) dodatkowy rabat. Świetnie!.fXzt"

in 23.62 milliseconds.

• Type 2 Diabetes Data access committee (DAC)

  Dac EGAC00001001293

• Genetic Determinants of Viral Clearance in HCV-Infected Populations

  The World Health Organization estimates there are 170 million persons with HCV infection worldwide, and an estimated 4 million persons are infected in the United States. Persistent HCV infection can cause cirrhosis and hepatocellular cancer. Long term disease consequences do not occur in persons who spontaneously recover. It is not known why 10-40% recover from hepatitis C (and are not at increased risk of cirrhosis and cancer), but that knowledge would contribute to efforts to treat and/or prevent HCV infection. The overall purpose of this study is to investigate the host genetic basis for recovery from hepatitis C virus (HCV) infection. There is strong evidence that host genetic differences determine HCV recovery. After accidental exposure to the same HCV inoculum, some persons recover while others develop persistent infection. Recovery from HCV infection is an outstanding phenotype for genetic studies since both viral exposure and viral recovery can be ascertained with high sensitivity and specificity and since there are no known viral or environmental determinants. The study group is comprised of an ethnically and geographically diverse international population. All cohorts comprising this study group of 3350 individuals are well characterized. This case-control study is comprised of approximately 40% clearance individuals who are matched by age and HIV status within their respective cohorts at a ratio of 1:1 or 1:2 with HCV chronically infected individuals.

  Study phs000248

• BrainCloud: Data from human postmortem brain procurement for the neuropathology section

  This study explores the temporal dynamics and genetic control of transcription and DNA methylation in the human dorsolateral prefrontal cortex in postmortem tissue. This study examines 269 subjects for gene expression (version 1) and 108 subjects for DNA methylation (version 2). The subjects are normal controls without neuropathological and neuropsychiatric diagnosis and range in age from fetal weeks 14-20 through old age (>80). We discover fast changes in gene expression occurring during early brain development. Later in life, the changes are considerably slower. Many genes reverse pattern of expression between fetal and early postnatal development. We identify thousands of strong associations of SNPs with gene expression. We examine DNA methylation in ~14,500 genes at ~27,000 CpG loci focused on 5' promoter regions. The fastest changes in DNA methylation also occur during the prenatal period, slow down markedly after birth and continue to slow further with aging. DNA methylation is strongly associated with genotypic variants and correlates with expression of a subset of genes. DNA for genotyping was obtained from the cerebella and applied to either Illumina 650K or 1 million BeadArrays - only genotypes common to both platforms are analyzed here. Genotypes were called using BeadExpress software. Doi: 10.1038/nature10524 Nature, 478:519-524, 2011; doi:10.1016/j.ajhg.2011.12.020, AJHG 90, 1-13, Feb 10, 2012. The methylation data can be downloaded at: BrainCloud.

  Study phs000417

• Genetic insights into the biological mechanisms governing human ovarian ageing

  Reproductive longevity is critical for fertility and impacts healthy ageing in women, yet insights into the underlying biological mechanisms and treatments to preserve it are limited. Here, we identify 290 genetic determinants of ovarian ageing, assessed using normal variation in age at natural menopause (ANM) in ~200,000 women of European ancestry. These common alleles influence clinical extremes of ANM; women in the top 1% of genetic susceptibility have an equivalent risk of premature ovarian insufficiency to those carrying monogenic FMR1 premutations. Identified loci implicate a broad range of DNA damage response (DDR) processes and include loss-of-function variants in key DDR genes. Integration with experimental models demonstrates that these DDR processes act across the life-course to shape the ovarian reserve and its rate of depletion. Furthermore, we demonstrate that experimental manipulation of DDR pathways highlighted by human genetics increase fertility and extend reproductive life in mice. Causal inference analyses using the identified genetic variants indicates that extending reproductive life in women improves bone health and reduces risk of type 2 diabetes, but increases risks of hormone-sensitive cancers. These findings provide insight into the mechanisms governing ovarian ageing, when they act across the life-course, and how they might be targeted by therapeutic approaches to extend fertility and prevent disease.

  Study EGAS00001004947

• Deep intronic homozygous variation in PSMC3 causes a syndromic neurosensory disorder combining deafness and cataract

  The association of congenital deafness and early-onset cataracts inherited as a recessive trait is a rare combination described in only a few syndromes with very few genes identified to date. We propose that the PSMC3 proteasome subunit dysfunction leads to a novel human syndrome that includes early-onset cataracts and deafness and suggest that Rpt5 plays a major role in inner ear and lens development.

  Study EGAS00001003942

• Fecal microbiome of T2D patients undergoing semaglutide or empagliflozin treatment

  The gut microbiome has been shown to be affected by the use of many human-targeted medications, and the interaction can be bidirectional. This has been clearly demonstrated for type 2 diabetes medications that have been in clinical use for several decades. However, the bidirectional effects of novel type 2 diabetes drugs semaglutide, empagliflozin, and the gut microbiome have yet to be clearly described. We investigated the effect of semaglutide and empagliflozin initiation on the gut microbiome of type 2 diabetes patients. In addition, we analyzed whether the pre-treatment gut microbiome can predict the treatment efficacy. Twenty subjects (10 women and 10 men) were enrolled in the study between November 2019 and January 2023 from the University of Tartu Hospital, Tartu, Estonia. All participants had been diagnosed with type 2 diabetes. The study group taking semaglutide included 6 women and 4 men, and the group prescribed empagliflozin included 4 women and 6 men. Gut microbiome fecal samples donated at four timepoints (Baseline, Month 1, Month 3; Month 12) were studied using 16S ribosomal RNA gene sequencing and analysis.

  Dataset EGAD50000000756

• Transcriptome

  Transcriptome array dataset

  Dataset EGAD00010001280

• Hi-C on the OCIAML-2 Cell Line

  Study EGAS00001004743

• MET amplification in gastric cancer

  WES sequencing of two cases of MET amplified gastric cancer. Six unfixed fresh frozen samples were obtained from the primary tumors (three samples from each) and three samples from corresponding non-neoplastic mucosa. In addition, formalin-fixed and paraffin-embedded (FFPE) samples were obtained from the primary tumors (n=2), lymph node metastases (n=7) and non-neoplastic mucosa (n=2).

  Dataset EGAD50000001099

• Chlamydia trachomatis exploits sphingolipid metabolic pathways during infection of phagocytes

  This study looks at the response of M2 macrophages stimulated with GM-CSF and IL4 for 7 days and 2 days respectively to C. trachomatis infection on an Illumina platform.

  Study EGAS50000000960

• RNA sequencing of intestinal metaplasia

  We perform bulk RNA-seq of 10 and single cell RNAseq of 2 intestinal metaplasia samples. We also perform stereoseq spatial transcriptomic analysis of 4 gastric cancer samples. The dataset contain cram files from 10 bulk RNAseq samples, and raw fastq files from 2 single cell RNAseq and 4 stereo-seq samples.

  Dataset EGAD50000002010

• WholeGenomeSeq-EGAS00001001306

  Whole Genome sequencing. 2 μg of genomic DNA from each sample was used for the construction of two short-insert paired-end sequencing libraries. Both types of libraries were sequenced in paired-end mode on Illumina GAIIx (2 × 151 bp) using Sequencing kit v4 or Illumina HiSeq2000 (2x101 bp) using TruSeq SBS Kit v3.

  Dataset EGAD00001001466

• Employing_single_cell_sequencing_for_detection_of_mutational_signatures_reflecting_on_going_mutagenesis_

  12 single cells will be sequenced from a previously single-cell derived clone of a JSC-1 cell line. Additional 12 single cells are likely to be sequenced from a previously single-cell derived clone of a SW756 line. Both belong to CGP’s panel of approximately 1000 human cancer cell lines.

  Study EGAS00001002679

• 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

• Genomewide detection of cytosine methylation by single molecule real-time sequencing

  5-methylcytosine (5mC) is an important type of epigenetic modification. In this study, we enhanced 5mC detection using SMRT sequencing by holistically analyzing kinetic signals of a DNA polymerase and sequence context for every base within a measurement window. We employed a convolutional neural network to train a methylation classification model. This methodology has provided a system for simultaneous genome-wide genetic and epigenetic analyses. 

  Study EGAS00001004642

• A GWAS meta-analysis on severe acne on a European population of 26,722 individuals

  Acne vulgaris is a highly heritable common, chronic inflammatory disease of the skin. We performed a genome-wide association study of 3,823 cases and 16,144 controls followed by meta-analysis with summary statistics from a previous study, with a total sample size of 26,722. We identified 20 independent association signals at 15 risk loci, 12 of which have not been previously implicated in the disease.

  Study EGAS00001003278

• Multi-regional tumour biopsies of a RET fusion patient

  Identifying modes of resistance to a new experimental drug for a patient resistant to other therapies

  Study EGAS00001004023

• CIDR: Discovery, Biology, and Risk of Inherited Variants in Glioma

  This is a gliogene brain tumor family study. This study includes glioma cases with a family history of glioma in a first, second, or third degree relative. 

  Study phs002250

• Cabozantinib Response in ETV6-NTRK3 G623R Positive Carcinoma HIPO-021

  We report a case of marked response to cabozantinib in a secondary entrectinib-resistant tumor harboring the ETV6-NTRK3 fusion with a G623R solvent-front mutation.

  Study EGAS00001004494

• Whole-genome analysis of a healthy man with common trichromatic vision

  Humans have a diversity of color vision that cannot be divided into normal and abnormal. As a first step to elucidate the genetic basis that contributes to the diversity of human color vision, we conducted a whole-genome analysis using DNA extracted from the saliva of a healthy man with common trichromatic vision. Further comparison with the genomes of people with various types of color vision may provide a model study of human nature that cannot be divided into normal and abnormal.

  Study JGAS000348

• The evolutionary trajectory of a highly recurrent paediatric high grade neuroepithelial tumour with MN1:BEND2 fusion

  Astroblastomas are rare brain tumours which predominate in children and young adults, and have a controversial claim as a distinct entity, with no established WHO grade. Reports suggest a better outcome than high grade gliomas, though they frequently recur. Recently, they have been described to overlap with a newly-discovered group of tumours described as ’high grade neuroepithelial tumour with MN1 alteration’ (CNS HGNET-MN1), defined by global methylation patterns and strongly associated with gene fusions targeting MN1. We have studied a unique case of astroblastoma arising in a 6 year old girl, with multiple recurrences over a period of 10 years, with the pathognomonic MN1:BEND2 fusion. Exome sequencing allowed for a phylogenetic reconstruction of tumour evolution, which when integrated with clinical, pathological and radiological data provide for a thorough understanding of disease progression, with initial treatment driving tumour dissemination along four distinct trajectories. Infiltration of distant sites was associated with a later genome doubling, whilst there was evidence of convergent evolution of different lesions acquiring distinct alterations targeting NF-κB. These data represent an usual opportunity to understand the evolutionary history of a highly recurrent childhood brain tumour, and provide novel therapeutic targets for astroblastoma / CNS HGNET-MN1.

  Study EGAS00001002432

• Genome-Wide Association Study of Leprosy and Dapsone Hypersensitivity Syndrome (DHS) in Chinese population

  Leprosy GWAS (1) Leprosy is a chronic infectious disease caused by Mycobacterium leprae (M. leprae). Due to M. leprae's narrow host range and an inability to be cultured in vitro, the biological investigation of this disease has been difficult. Host genetic factors have been suggested to play an important role in disease development, but few have been identified. In this study, we attempted to identify the host genetic factors by performing a two-stage genome-wide association study (GWAS) in Chinese population. The initial genome-wide scan was done by genotyping 706 patients and 1225 controls using the Illumina HumanHap610 BeadChip, and the follow-up study was performed by genotyping 93 SNPs in three independent samples consisting of 3254 cases and 5955 controls. We identified significant association (P < 10-10) within six genes CCDC122 (13q14), C13orf31 (13q14), NOD2(16q12), TNFSF15 (9q32), HLA-DR (6p21) and RIPK2 (8q21), and suggestive association (P = 5.68x10-6) within LRRK2 (12q12). We also revealed suggestive evidence for C13orf31, LRRK2, NOD2 and RIPK2 to show stronger association in the multibacillary form than the paucibacillary form of leprosy. Our findings highlight the importance of the innate immune response, particularly NOD2-mediated signaling, in leprosy and suggests a new therapeutic target for leprosy. DHS GWAS Dapsone (DDS), as both an antibiotic and an anti-inflammatory agent, has been widely used for preventing and treating pathogen-caused infectious diseases and chronic inflammatory diseases. Currently, about 0.5-3.6% of individuals treated with DDS develop severe dapsone hypersensitivity syndrome (DHS) and the mortality rate is up to about 11-13%. However, until now, no tests are available to predict the risk of DHS. To identify the genetic risk factors of DHS, we performed a two-stage GWAS in Chinese population. In this study, the initial genome-wide scan was done by genotyping 39 DHS cases and 833 controls using Illumina Human 660W-Quad Beadchips and imputed human leukocyte antigen (HLA) molecules. Validation was performed by genotyping 24 SNPs using the Sequenom MassARRAY platform in additional 31 DHS cases and 1,089 controls through genotyping and 32 four-digit HLA-B alleles in an independent series of 37 DHS cases and 201 controls through Roche 454 sequencing. We identified significant association (OR =6.18, P = 3.84x10-13) with SNP rs2844573, which located between the HLA-B and MICA loci. HLA-B*13:01 was confirmed to be a strong risk factor for DHS (OR = 20.53, P = 6.84x10-25) and responsible for the association at rs2844573. The presence of HLA-B*13:01 had a sensitivity of 85.5% and specificity of 85.7% as a predictor for DHS, and its absence can reduce the risk by 7 fold (from 1.4% to 0.2%). HLA-B*13:01 is strongly associated with the development of DHS and can be used as a risk predictor of DHS in the individuals of Chinese and other Asian populations. Leprosy GWAS (2) This is a three-stage GWAS of leprosy in the Chinese population. The genome-wide discovery analysis involved two independent data sets: the new unpublished data set by genotyping 842 leprosy patients and 925 controls from northern and southern China using the Human660w-quad beadchips and a previously published GWAS data set of 706 leprosy cases, 1,225 healthy controls and 4,362 individuals with immune-related diseases as population controls from northern China of Chinese Han descent. Further validation studies were performed in two stages in a total of 6,765 cases and 9,505 controls from Chinese Han and minority descent in multiple areas of China, similar to the discovery stage. From this study, we discovered six new susceptibility loci with a combined P-value from discovery and validation stage surpassing genome-wide significance, including BATF3 at 1q32.3, CDH18 at 5p14.3, DEC1 at 9q32, EGR2 at 10q21.3, CCDC88B at 11q13.1 and CIITA at 16p13.13. Our current study has advanced the genetic understanding of leprosy by substantially increasing the number of confirmed genetic susceptibility loci. Leprosy GWAS (3) To discover additional leprosy susceptibility loci, we carried out a large-scale three-stage GWAS analysis of leprosy in Chinese population. The genome-wide discovery analysis (Stage 1) involved a new GWAS data set of 1,197 leprosy cases and 1,426 controls from northern and southern China conducted by using Illumina Omni Zhonghua chips with 900,015 single-nucleotide polymorphisms (SNPs), two published GWAS dataset (GWAS2 data set including 706 leprosy cases, 1,225 healthy controls genotyped by Illumina HumanHap610 beadchips, GWAS3 data set including 842 leprosy patients and 925 controls from northern and southern China genotyped by the Human660w-quad beadchips). Further validation studies were performed in two stages in a total of 5,413 cases and 9,771 controls from Chinese Han descent in multiple areas of China. In this study, we identified four novel associations at genome-wide significance (P < 5 x 10-8), all of which can indicate candidate genes within the susceptibility loci, SYN2 (3p25.2), BBS9 (7p14.3), CTSB (8p23.1) and MED30 (8q24.11), through a differential gene expression and eQTL analysis. Altogether, these findings have provided new insight and significantly expanded our understanding of the genetic basis of leprosy. Leprosy GWAS (4) In this study, we attempted to systematically investigate the contribution of protein-coding variants to leprosy susceptibility by performing a three-stage genome-wide association study (GWAS) of protein-coding variants in Chinese population. The initial genome-wide scan was done by genotyping 1,670 persons affected by leprosy and 2,321 controls using the Illumina Infinium Human Exome Beadchips (v1.0).The validation study was performed by genotyping 39 SNPs in an additional 3,169 leprosy patients and 9,814 healthy controls from the northern region of China, and the replication study was performed by genotyping eight SNPs in three independent samples from the southern regions of China consisting of 2,231 cases and 2,266 controls. We identified significant association (P < 1.23 x 10-6) within seven genes FLG (Gene ID: 2312), IL23R (Gene ID: 149233), CARD9 (Gene ID: 64170), NCKIPSD (Gene ID: 51517), TYK2 (Gene ID: 7297), SLC29A3 (Gene ID: 55315), IL27 (Gene ID: 246778). Our findings discover novel involvement of skin barrier and endocytosis/phagocytosis/autophagy, besides known innate and adaptive immunity, in the pathogenesis of leprosy, highlight the merits of protein coding variant studies for complex diseases. Here, the summary statistics from the five genome-wide association analyses were published.

  Study phs000217

• Sequencing of two human samples

  Dataset EGAD00001001001

• HUMANOMNI1QUAD_Genotyping

  samples using Illumina HUMANOMNI1QUAD

  Dataset EGAD00010000919

• RAGE engagement by SARS-CoV-2 Data Access Commitee

  Dac EGAC00001003405