Summary statistics are the compiled, per-variant results of a genome-wide association study (GWAS), capturing the estimated effect of each single nucleotide polymorphism on a phenotype. A standard file includes the effect allele, its corresponding beta coefficient (effect size), standard error, and p-value, providing a complete statistical snapshot of the genotype-phenotype association for millions of variants in a single, shareable format.
Glossary
Summary Statistics

What is Summary Statistics?
The aggregated, variant-level output from a genome-wide association study that serves as the foundational input for constructing polygenic risk scores without requiring access to individual-level genotype data.
These aggregated files are the essential base data for polygenic risk score (PRS) construction, enabling methods like LDpred2 and PRS-CS to model genetic architecture without handling sensitive raw genotypes. By combining effect sizes with an external linkage disequilibrium (LD) reference panel, researchers can correct for confounding, apply winner's curse correction, and compute an individual's cumulative genetic susceptibility across diverse populations.
Core Components of a GWAS Summary Statistics File
A GWAS summary statistics file is a structured, tabular dataset containing the aggregated association results for millions of genetic variants tested against a phenotype. These files serve as the foundational input for polygenic risk score construction without requiring access to individual-level genotypes.
Variant Identification & Annotation
Each row must uniquely identify a genetic variant using standardized fields:
- rsID (dbSNP identifier): The reference SNP cluster ID, providing a universal label for the variant.
- Chromosome & Base-Pair Position: Genomic coordinates mapped to a specific reference genome build, such as GRCh37 (hg19) or GRCh38.
- Effect Allele (A1): The allele to which the reported effect size applies, also called the coded allele or reference allele in some software packages.
- Non-Effect Allele (A2): The alternative allele at the same locus, sometimes labeled as the other allele.
Consistent allele coding across cohorts is critical; strand flips or allele mismatches during meta-analysis or PRS calculation can reverse the direction of effect and destroy predictive accuracy.
Effect Size & Direction
The magnitude and direction of a variant's association with the trait are captured by the beta coefficient (β) and the odds ratio (OR).
- Beta (β): Represents the change in the quantitative trait per copy of the effect allele. For a binary trait, it is the log-odds ratio from logistic regression.
- Odds Ratio (OR): An exponentiated beta (OR = e^β) used in case-control studies. An OR > 1 indicates the effect allele increases disease risk.
- Standard Error (SE): Quantifies the uncertainty around the beta estimate, reflecting sample size and allele frequency. A smaller SE indicates a more precise estimate.
These fields are the direct inputs for the weighted allele scoring that defines a polygenic risk score.
Statistical Significance
The probability that the observed association is due to chance is reported as a p-value, often on a -log10 scale.
- P-value: Derived from the beta and its standard error, typically using a Wald test or score test. The genome-wide significance threshold is conventionally set at p < 5 × 10⁻⁸ to correct for multiple testing of ~1 million independent variants.
- -log10(p): A transformed metric where a value of 7.3 corresponds to the genome-wide threshold. This scale is used for visualization in Manhattan plots.
- Z-score: Calculated as β / SE, indicating the direction and strength of association in units of standard deviation.
P-values are the primary metric for the clumping and thresholding (C+T) method, where only variants below a user-defined significance threshold are retained for PRS calculation.
Allele Frequency & Imputation Quality
Quality control fields ensure that only well-measured variants are included in downstream analyses:
- Effect Allele Frequency (EAF): The frequency of the effect allele in the study population. This is essential for identifying rare variants and for harmonizing allele coding across datasets.
- Imputation INFO Score: A metric ranging from 0 to 1 that quantifies the confidence in statistically inferred genotypes. An INFO > 0.8 is a common filter to exclude poorly imputed variants.
- Minor Allele Frequency (MAF): The frequency of the less common allele. PRS analyses often filter out variants with MAF < 1% due to unstable effect size estimates.
Filtering on these metrics removes noisy variants that degrade PRS predictive performance.
Sample Size & Cohort Information
Metadata fields describe the study population and statistical power:
- N (Sample Size): The total number of individuals included in the analysis for that variant. Larger sample sizes yield smaller standard errors and more robust p-values.
- N Cases / N Controls: For binary traits, the breakdown of affected and unaffected individuals. This ratio impacts the power to detect associations.
- Cohort / Study Identifier: In a meta-analysis file, a column indicating the originating study for each variant, enabling leave-one-out analyses.
Sample size directly determines the statistical power of the GWAS and, consequently, the maximum predictive ceiling of any PRS derived from it.
Frequently Asked Questions
Clear, technically precise answers to the most common questions about GWAS summary statistics and their role in polygenic risk score modeling.
GWAS summary statistics are aggregated, non-individual-level results from a genome-wide association study that report, for each genetic variant tested, the effect allele, beta coefficient, standard error, p-value, sample size, and often the effect allele frequency. These files serve as the foundational input for most modern polygenic risk score (PRS) methods—such as LDpred2, PRS-CS, and SBayesR—because they contain all the information needed to model the genetic architecture of a trait without requiring access to sensitive individual-level genotype and phenotype data. The beta coefficient represents the estimated additive effect of one copy of the effect allele on the trait, while the standard error quantifies the precision of that estimate. The p-value tests the null hypothesis of no association. Together, these statistics allow PRS algorithms to re-weight variant effects using external linkage disequilibrium (LD) reference panels, apply Bayesian shrinkage priors, and compute polygenic scores in target cohorts. The widespread availability of public summary statistics from consortia like the GWAS Catalog and Pan-UK Biobank has democratized PRS research, enabling predictive models to be built without the logistical and privacy burdens of individual-level data sharing.
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
The Role of Summary Statistics in PRS Construction
Summary statistics are the aggregated, variant-level association results from a Genome-Wide Association Study (GWAS) that serve as the foundational input data for constructing a Polygenic Risk Score (PRS) without requiring access to individual-level genotypes.
Summary statistics are the aggregated, variant-level association results from a Genome-Wide Association Study (GWAS) that serve as the foundational input data for constructing a Polygenic Risk Score (PRS) without requiring access to individual-level genotypes. For each single nucleotide polymorphism (SNP), these files typically contain the effect allele, its corresponding beta coefficient (or odds ratio), the standard error of that effect, and the p-value from the association test. This compact data format enables large-scale meta-analysis and downstream modeling while preserving participant privacy.
Modern PRS methods like LDpred2 and PRS-CS use these summary statistics as the sole input, applying Bayesian priors to correct for linkage disequilibrium and Winner's Curse overestimation bias. The reliability of the resulting score is entirely dependent on the quality of the input statistics, making rigorous quality control—including filtering on imputation accuracy and minor allele frequency—a critical prerequisite for accurate polygenic prediction.
Related Terms
Understanding summary statistics requires familiarity with the foundational metrics and quality control measures that underpin polygenic risk score construction.
Effect Allele & Beta Coefficient
The effect allele is the specific nucleotide base to which the estimated effect size is assigned. The beta coefficient represents the log-odds change in disease risk (for binary traits) or the unit change in a quantitative trait per additional copy of the effect allele. Together, they form the core directional signal extracted from GWAS. A positive beta indicates risk-increasing, while a negative beta indicates a protective effect. Accurate allele alignment between the summary statistics and the target genotype data is critical; strand flips or allele mismatches will invert the direction of effect and catastrophically degrade PRS performance.
Standard Error & P-Value
The standard error quantifies the precision of the estimated beta coefficient, reflecting sampling variability. It is inversely proportional to the square root of the sample size. The p-value is derived from the ratio of beta to its standard error (the Z-score) and tests the null hypothesis that the variant has no effect. Key considerations:
- Larger sample sizes shrink standard errors, yielding more significant p-values
- P-values are often reported on a -log10 scale in Manhattan plots
- Winner's Curse: selecting variants by p-value threshold systematically inflates effect estimates, requiring correction
Allele Frequency & INFO Score
The effect allele frequency (EAF) reports how common the effect allele is in the GWAS cohort. This is essential for downstream quality control because:
- Rare variants (MAF < 1%) have unstable effect estimates with large standard errors
- Mismatches between EAF in the base data and the target population can indicate allele coding errors
- The INFO score (imputation quality metric) ranges from 0 to 1 and measures confidence in statistically inferred genotypes. Filtering on INFO > 0.8 is standard practice to remove poorly imputed variants that introduce noise into PRS calculations.
Genomic Inflation Factor (λ)
The genomic inflation factor (λ) is a global quality control metric computed as the ratio of the median observed chi-squared test statistic to the expected median under the null distribution. A λ value of 1.0 indicates no systemic bias. Values substantially above 1.0 suggest:
- Population stratification: systematic allele frequency differences between cases and controls due to ancestry
- Cryptic relatedness: unrecognized familial relationships inflating test statistics
- Polygenic signal: for highly polygenic traits with large sample sizes, moderate inflation (λ < 1.1) is expected and does not indicate confounding. LD score regression can distinguish true polygenicity from bias.
Sample Size & Effective N
Statistical power in GWAS is primarily driven by sample size. The effective sample size (Neff) accounts for imbalanced case-control ratios and is calculated as Neff = 4 / (1/Ncases + 1/Ncontrols). For meta-analyses combining multiple cohorts, Neff approximates the equivalent sample size of a balanced study. Key implications:
- Larger Neff yields smaller standard errors and more precise beta estimates
- PRS predictive accuracy scales with the discovery GWAS sample size
- Meta-analysis summary statistics should report per-variant sample sizes, as not all variants are measured in every contributing cohort
Strand Ambiguity & Allele Harmonization
Strand ambiguity occurs when A/T or C/G SNPs cannot be resolved by allele matching alone, as the forward-strand allele is identical to the reverse-strand complement. This creates a critical data integration challenge when aligning summary statistics to a target genotype panel. Allele harmonization is the systematic process of:
- Matching alleles by identity, then by complement
- Removing ambiguous SNPs where allele frequency cannot disambiguate orientation
- Flipping beta signs when the effect allele in the summary statistics matches the reference panel's non-effect allele Failure to harmonize properly introduces sign errors that destroy PRS predictive power.

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us