Golden Helix · Clinical Genomics Guide

Tertiary Analysis in NGS
From Variant List to Clinical Diagnosis

The interpretation stage that turns a 35,000-line VCF into a defensible clinical report. Annotation, filtering, prioritization, ACMG classification, and what separates a clinical-grade pipeline from a research tool.

Variant AnnotationFiltering StrategyACMG ClassificationClinical ReportingVUS Handling

Introduction

A variant list is not
a clinical result.

Every NGS run ends the same way: a file. A VCF that lists every position where the patient's DNA differs from the reference. For a whole exome that list contains 25,000 to 40,000 entries. For a whole genome it contains 4 to 5 million.

None of those variants constitute a clinical result on their own. They are observations without meaning, coordinates and base changes with no indication of which, if any, explain why the patient is sick. Tertiary analysis is the process of turning that list into a diagnosis. It is the most complex, knowledge-intensive, and consequential stage of the NGS pipeline, and the stage that receives the least standardization, the least automation, and the most variation in quality between institutions.

~35K
Variant calls per whole exome
~4M
Variant calls per whole genome
30–50%
Typical VUS rate in WES rare disease
28
ACMG/AMP criteria for germline classification
5
Pathogenicity tiers: P, LP, VUS, LB, B
81
Genes on the ACMG secondary-findings list (SF v3.2)

Pipeline Context

Where Tertiary Analysis Sits

The NGS pipeline is divided into three stages, each building on the last. The boundary that matters most for clinical labs is between secondary and tertiary, where the work shifts from computational to interpretive.

Stage 1

Primary Analysis

Performed by the sequencer. Raw optical signals become nucleotide base calls with per-base Phred quality scores. Output: a FASTQ file.

Stage 2

Secondary Analysis

Reads aligned to the reference, duplicates removed, variants called. Output: BAM and VCF. Largely computational and deterministic given inputs and pipeline version.

Stage 3

Tertiary Analysis

Begins at the VCF. Variants are annotated, filtered, prioritized, classified, and reported. The work shifts from computational to interpretive. This is the page you are on.

The Hard Part

Why Tertiary Analysis Resists Automation

Secondary analysis has been largely solved. The tools are validated, the pipelines documented, the compute requirements understood. Tertiary analysis has not been solved in the same way, for four structural reasons.

  • 01

    Scale mismatch

    A WES run produces tens of thousands of variant calls. WGS produces millions. The clinical team must reduce that to a handful of actionable findings without discarding the diagnosis. Eliminate noise. Do not eliminate signal.

  • 02

    Knowledge dependency

    A variant that was a VUS eighteen months ago may be Pathogenic today because of new publications, functional studies, or cohort data. Tertiary analysis is only as good as the databases and literature it draws on, and those change continuously.

  • 03

    Regulatory burden

    Clinical tertiary analysis must be deterministic (same input, same output, every time), auditable (every classification documented and retrievable), and validated (performance demonstrated on characterized reference samples). These requirements eliminate many research-grade tools.

  • 04

    Expert scarcity

    Variant interpretation requires clinical genetics expertise: inheritance patterns, gene-disease relationships, phenotype-genotype correlations, and the nuances of ACMG/AMP. This expertise is in short supply globally and cannot be fully automated, even by the best platforms.

The labs with the highest diagnostic yields and shortest turnaround times invested in platforms that automate the repetitive, evidence-gathering portions of interpretation, freeing clinical geneticists to focus on genuinely ambiguous cases.

Step 1

Variant Annotation

Annotation adds biological context to each raw variant call. A position and base change conveys nothing clinically useful on its own. Annotation transforms it into a clinically evaluable entity by answering: what gene does this affect, what does the change do to the protein, has it been seen before, how common is it in the population, and is it already classified in any clinical database?

Essential annotation sources

Classifications

ClinVar

The most important clinical annotation database for germline interpretation. NCBI aggregates classifications submitted by labs and research institutions worldwide. Updated weekly. Variants with multiple submitter agreement and expert-panel review carry the highest evidential weight.

Population data

gnomAD

Population allele frequencies across hundreds of thousands of individuals. A variant present at greater than 1% frequency is almost certainly benign for rare Mendelian disease. Also provides gene constraint metrics: pLI for loss-of-function intolerance, missense Z-scores.

Gene-disease

OMIM & ClinGen

OMIM documents which genes are associated with which conditions and under which inheritance patterns. ClinGen curates the strength of evidence for each reported gene-disease relationship (Definitive to Refuted) and publishes gene-specific ACMG rule refinements through its Expert Panels.

In silico

dbNSFP

Aggregates computational prediction scores from SIFT, PolyPhen-2, CADD, REVEL, MutationTaster, and others into a single resource. In silico scores are supporting evidence in ACMG classification. Never sufficient on their own.

Splicing

SpliceAI

Deep learning prediction of variant effects on splicing, including deep intronic variants far from canonical splice sites. Has substantially improved detection of clinically significant splice variants that would otherwise be ignored as intronic.

Literature

HGMD & Mastermind

Catalog published reports of variants in human disease. Provide the literature evidence trail showing whether a specific variant has been observed in affected patients before. Literature evidence is among the strongest contributors to pathogenicity classification.

Step 2

Variant Filtering

After annotation the goal is reduction: remove the vast majority of variants that are clearly not responsible for the patient's disease, while retaining every variant that might be. The tension between sensitivity (do not miss the answer) and specificity (do not bury it in noise) defines filter chain design.

  • 01

    Quality filters

    Remove low-quality calls likely to be sequencing artifacts. Read depth ≥20x for germline, ≥50–100x for somatic. Genotype quality ≥20 PHRED. Heterozygous allele balance ~20–80%. Thresholds should come from analytical validation on your specific sequencer and library prep, not from a published default.

  • 02

    Population frequency filters

    The single most powerful filter in most germline rare-disease pipelines. Exclude autosomal dominant candidates above ~0.01% gnomAD frequency, autosomal recessive above ~1%. Use gnomAD's population-stratified frequencies for patients from underrepresented populations, or you will misclassify.

  • 03

    Functional consequence filters

    Prioritize by predicted impact: loss-of-function (nonsense, frameshift, canonical splice ±1/±2) first, then missense in constrained genes, then in-frame indels. Synonymous and intronic variants are deprioritized unless specific evidence (e.g., SpliceAI) warrants. Somatic pipelines invert this for hotspot mutations and oncogene/tumor-suppressor variants.

  • 04

    Inheritance model filters

    Trio analysis (proband plus both parents) dramatically shrinks the candidate space. De novo variants for severe early-onset disease, compound heterozygous for autosomal recessive, homozygous for consanguineous lines. Without parental data these models must be inferred from population frequency and clinical context. Far weaker.

Step 3

Variant Prioritization

Filtering removes what is clearly not the answer. Prioritization ranks what remains by how likely each variant is to explain the patient's disease.

Phenotype-driven gene ranking

The patient's clinical presentation is the most powerful prior for prioritization. HPO (Human Phenotype Ontology) terms, a standardized vocabulary for clinical features, are used to rank genes by their relevance to the patient's phenotype. A missense variant in a gene with established association to the patient's specific combination of features should surface to the top of the review queue. The same variant in a gene with no phenotypic connection should be deprioritized. Tools like PhoRank (integrated in VarSeq) compute phenotypic similarity scores between the patient's HPO terms and each gene's known phenotypic spectrum.

Gene-disease validity

Not all reported gene-disease relationships are equally supported. A variant in a gene with Definitive ClinGen classification deserves more weight than a variant in a gene with Limited or Disputed classification. Many gene-disease relationships in the literature were established before modern statistical standards. Some have been refuted or weakened.

Variant-level evidence aggregation

Before formal classification, the interpretation platform should surface all available evidence for each candidate variant: ClinVar submissions and star ratings, published case reports from HGMD or Mastermind, gnomAD frequency, in silico predictions, conservation, and the lab's own knowledgebase. This is where the quality of the tertiary analysis platform has its largest impact on turnaround time. A platform that automatically surfaces and organizes this evidence lets a clinical geneticist evaluate a candidate in minutes rather than hours.

Step 4

ACMG/AMP Variant Classification

Classification assigns a clinical pathogenicity tier to each candidate variant using standardized frameworks. Germline uses one framework. Somatic uses another. Labs running both need to handle both.

Germline: ACMG/AMP guidelines

The 2015 ACMG/AMP guidelines (Richards et al., Genetics in Medicine) define a five-tier classification system: Pathogenic, Likely Pathogenic, Variant of Uncertain Significance, Likely Benign, Benign. Classification is determined by applying 28 criteria organized by evidence type and strength, from PVS1 (null variant in a gene where loss-of-function is a known mechanism) to BP7 (silent variant with no predicted splice impact). Each criterion is weighted Very Strong, Strong, Moderate, or Supporting. The combination of met criteria determines the final tier. ClinGen Expert Panels publish gene-specific rule refinements for many clinically important genes.

Somatic: AMP/ASCO/CAP guidelines

Somatic classification (Li et al., 2017) follows a different framework. Unlike germline (focused on pathogenicity), somatic focuses on actionability: relevance to treatment, prognosis, or trial eligibility. Four tiers:

  • Tier I, Strong clinical significance: FDA-approved therapies or standard of care support use for treatment decisions in this tumor type.
  • Tier II, Potential clinical significance: Clinical relevance from trials, case reports, or evidence in the same or different tumor type.
  • Tier III, Unknown clinical significance: Not established as clinically relevant. May be a passenger mutation.
  • Tier IV, Benign or likely benign: Common variant with no established role in cancer.
DimensionGermline (ACMG)Somatic (AMP)
Clinical questionDoes this variant cause inherited disease?Does this variant affect treatment or prognosis?
Sample typeNormal tissue (blood, saliva)Tumor tissue
FrameworkACMG/AMP 5-tierAMP/ASCO/CAP 4-tier
Primary databasesClinVar, gnomAD, OMIM, ClinGenGolden Helix CancerKB, CIViC, COSMIC, FDA labels
Key evidence typesInheritance pattern, functional studies, population frequencyTherapeutic evidence, clinical trials, tumor type specificity
VUS handlingReport with uncertainty disclosureTypically Tier III, clinical team decides actionability
Inheritance modelingEssentialNot applicable
Tumor fractionNot applicableEssential for low-VAF variants

The VUS problem

A VUS is the most common outcome of diagnostic sequencing for rare disease patients. Rates of 30 to 50% are typical in WES, not because the technology is failing but because current knowledge is genuinely insufficient to classify many variants definitively.

A VUS is not a dead end. It is the beginning of an evidence-accumulation process. Functional studies, family segregation, continued absence from gnomAD as the dataset grows, new ClinVar submissions, and lab-internal observations all contribute over time. Reclassification rates of 10 to 30% over 3 to 5 years are documented across large lab cohorts. Labs have a clinical obligation to monitor VUS reclassification and notify patients when status changes. That requires a variant knowledgebase that tracks every VUS ever reported and alerts staff when its external classification shifts.

Step 5

Clinical Reporting

The clinical report is the final output of tertiary analysis. The document that reaches the ordering physician, enters the medical record, and directly influences patient care. Its content, format, and accuracy are subject to CAP/CLIA standards.

Required report elements

  • Patient and specimen identification
  • Test methodology: sequencing platform, capture kit, reference genome build, bioinformatics pipeline version, variant caller(s)
  • Analytical performance metrics: mean coverage, percentage of target bases at minimum depth
  • Reported variants with HGVS nomenclature (genomic, coding, protein)
  • Variant classification with a supporting evidence summary
  • Clinical interpretation: how the identified variant(s) explain or fail to explain the phenotype
  • Secondary findings policy: whether ACMG-recommended secondary findings were evaluated and reported
  • Limitations: known coverage gaps, variants not detectable by this assay, VUS uncertainty
  • Ordering provider information and laboratory director signature

Secondary findings

The ACMG recommends labs report secondary findings: pathogenic or likely pathogenic variants in 81 medically actionable genes (SF v3.2), when identified incidentally during exome or genome sequencing, regardless of the primary indication. Implementation is not universal. Patients should be counseled and offered the option before testing. Secondary findings reporting requires a clear lab policy, documented patient consent, and a clinical process to communicate findings to appropriate specialists.

EHR integration

Reports should be delivered through secure, trackable channels: a laboratory information system (LIS) or direct EHR integration. PDF reports via secure portal are standard. HL7 FHIR-based structured reporting for EHR integration is increasingly available and enables downstream clinical decision support.

Buying Criteria

What Separates Clinical-Grade from Research-Grade

Research-grade tools, even excellent and widely used ones, are not appropriate for clinical use without substantial additional validation and infrastructure. Seven criteria define a clinical-grade tertiary analysis platform.

  • 01

    Determinism

    The same VCF must produce the same annotated, filtered, classified output every time, on every machine, on every run. Any algorithm with random sampling, stochastic steps, or version-dependent behavior that is not explicitly version-locked fails this requirement.

  • 02

    Annotation currency and versioning

    Monthly database updates with controlled versioning. Every clinical result traceable to the exact database versions used at the time of analysis. Not optional for CAP/CLIA compliance.

  • 03

    Full variant type support

    SNVs, indels, CNVs, structural variants, and pharmacogenomic star alleles should be analyzable in a single platform. A tool that handles SNVs but requires separate software for CNVs creates analytical gaps and a fragmented audit trail.

  • 04

    ACMG/AMP automation

    Automated application of classification criteria, not just display of evidence. Systematic scoring of criteria based on annotation data, with the ability for clinical reviewers to adjust and document their reasoning. The difference between a literature-review tool and a classification engine.

  • 05

    Audit trail

    Every variant assessment, every classification decision, every filter chain applied is logged and permanently retrievable. CAP inspection requires that a laboratory can reproduce any historical result on demand.

  • 06

    Deployment flexibility

    On-premises, private cloud, or air-gapped deployment options. Clinical genomic data cannot be uploaded to a public cloud platform without a signed BAA and appropriate security controls. Many institutions require on-prem.

  • 07

    Validated QMS

    Software developed under an ISO 13485-certified Quality Management System provides the change control, release validation, and documentation practices that CAP/CLIA accreditation inspections expect from a clinical software vendor.

Common Questions

Frequently Asked Questions

What is tertiary analysis of NGS data?
Tertiary analysis is the third and final stage of the NGS pipeline. It begins at the VCF produced by secondary analysis and transforms that variant list into a clinical interpretation by annotating with biological context, filtering to remove common and low-quality calls, prioritizing by clinical relevance, classifying with ACMG (germline) or AMP/ASCO/CAP (somatic) guidelines, and synthesizing into a clinical report. While primary and secondary analysis are largely automated, tertiary analysis requires clinical genetics expertise and is the most time-intensive stage of the workflow.
What is the difference between secondary and tertiary analysis in NGS?
Secondary analysis transforms raw sequencing reads into a list of genetic variants (a VCF). It answers the question: what variants are present? Tertiary analysis begins at the VCF and transforms that list into a clinical interpretation. It answers the question: which variants explain this patient's condition? Secondary analysis is primarily computational and largely automated. Tertiary analysis requires clinical knowledge, current genomic databases, and expert judgment.
What is an example of tertiary analysis in genomics?
A clinical laboratory receives a VCF from a WES run on a child with unexplained developmental delay. Tertiary analysis annotates each of the 35,000 variants with ClinVar, gnomAD, OMIM, and in silico scores. Population frequency removes ~99% as too common to explain rare disease. Functional filters prioritize loss-of-function and missense variants. HPO-based phenotype matching ranks variants in genes associated with developmental delay. The five highest-priority candidates are reviewed against published literature. One, a de novo nonsense variant in a gene with Definitive ClinGen classification for intellectual disability, is classified as Pathogenic and reported as the likely molecular cause.
What is secondary and tertiary data in the context of NGS?
"Secondary data" refers to the processed output of secondary analysis: primarily BAM (aligned reads) and VCF (called variants) files. "Tertiary data" refers to the output of tertiary analysis: annotated VCFs, variant interpretation records, ACMG classification assessments, and the final clinical report. These terms describe pipeline stages and their outputs. The VCF is the handoff: secondary analysis produces it, tertiary analysis consumes it.
Should I use hg19 or hg38 for clinical NGS?
For new clinical pipelines, use GRCh38/hg38. It is the current reference standard, corrects errors present in hg19, and is the primary build for all major annotation databases (ClinVar, gnomAD, ClinGen). Germline labs still on GRCh37/hg19 should plan a migration: annotation quality on hg38 continues to improve relative to hg19. Many targeted somatic pipelines are hard-coded for hg19 and, given their focus on a fixed gene list where coordinate updates add little clinical value, are unlikely to migrate. That is acceptable as long as alignment, annotations, classification, and reporting all stay on the same build end to end.
How long does tertiary analysis take?
Turnaround varies by assay, case complexity, and degree of automation. A standard panel or WES case with a clear diagnosis takes 15 to 30 minutes of hands-on time with an automated platform that handles ACMG scoring and phenotype prioritization. Complex WGS cases with many VUS candidates, ambiguous phenotypes, or novel variants requiring literature review can take several hours. Manual, spreadsheet-based workflows average 2 to 4 hours per WES case, the bottleneck that limits laboratory throughput in most clinical settings.
How is tertiary analysis different for germline vs somatic testing?
Germline and somatic tertiary analysis share the first steps (annotation and quality filtering) but diverge fundamentally at classification. Germline uses the ACMG/AMP 5-tier framework, asking whether a variant causes inherited disease, with population frequency, inheritance pattern, and functional evidence. Somatic uses the AMP/ASCO/CAP 4-tier framework, asking whether a variant in a tumor affects treatment, with therapeutic evidence from Golden Helix CancerKB and CIViC. Different databases, different evidence hierarchies, different variant types prioritized, different clinical questions. Labs doing both need a platform that handles both frameworks in a single validated environment.
What is a VUS and what should the lab do about it?
A Variant of Uncertain Significance (VUS) means current evidence is insufficient to classify a variant as Pathogenic or Benign. VUS rates of 30 to 50% are typical for WES rare disease. A VUS is not a dead end. It is the start of an evidence-accumulation process: functional studies, family segregation, continued population data, and ClinVar growth all contribute. Labs have a clinical obligation to monitor VUS reclassification and notify patients when status changes. Reclassification rates of 10 to 30% over 3 to 5 years are documented across large lab cohorts.

Automate the Tertiary Stage

VarSeq provides automated ACMG/AMP scoring, monthly-updated annotation databases, phenotype-driven prioritization, and audit-ready clinical reporting in a deterministic, ISO 13485-certified platform deployable on-premises or in a private cloud.