Tutorial: a guide to performing polygenic risk score analyses

Shing Wan Choi, Timothy Shin Heng Mak, Paul F. O’Reilly

Research output: Contribution to journalReview articlepeer-review

901 Scopus citations

Abstract

A polygenic score (PGS) or polygenic risk score (PRS) is an estimate of an individual’s genetic liability to a trait or disease, calculated according to their genotype profile and relevant genome-wide association study (GWAS) data. While present PRSs typically explain only a small fraction of trait variance, their correlation with the single largest contributor to phenotypic variation—genetic liability—has led to the routine application of PRSs across biomedical research. Among a range of applications, PRSs are exploited to assess shared etiology between phenotypes, to evaluate the clinical utility of genetic data for complex disease and as part of experimental studies in which, for example, experiments are performed that compare outcomes (e.g., gene expression and cellular response to treatment) between individuals with low and high PRS values. As GWAS sample sizes increase and PRSs become more powerful, PRSs are set to play a key role in research and stratified medicine. However, despite the importance and growing application of PRSs, there are limited guidelines for performing PRS analyses, which can lead to inconsistency between studies and misinterpretation of results. Here, we provide detailed guidelines for performing and interpreting PRS analyses. We outline standard quality control steps, discuss different methods for the calculation of PRSs, provide an introductory online tutorial, highlight common misconceptions relating to PRS results, offer recommendations for best practice and discuss future challenges.

Original languageEnglish
Pages (from-to)2759-2772
Number of pages14
JournalNature Protocols
Volume15
Issue number9
DOIs
StatePublished - 1 Sep 2020

Fingerprint

Dive into the research topics of 'Tutorial: a guide to performing polygenic risk score analyses'. Together they form a unique fingerprint.

Cite this