01
Where it fits and where it does not
Use these four checks before committing implementation time.
- Use it when
- Clinical reporting, variant databases, publications, laboratory systems, and exchange workflows that must communicate sequence-level variation unambiguously.
- Limits
- One biological variant can have several valid descriptions against different references or transcripts. HGVS does not encode pathogenicity, evidence strength, observed genotype, or cohort frequency, and syntax validity alone does not establish biological correctness.
- Best for
- Omics and Clinical and Laboratory teams working across Harmonize → Exchange → Learn + reuse.
- Maturity
- EstablishedSuitable for production assessment. Pin the exact release and any implementation profile.
02
See it in the workflow
This view shows the input, the change the standard introduces, and the resulting output.
- InputWhat starts
Omics and Clinical and Laboratory source data, metadata, and local mappings
- HGVSWhat changes
Use HGVS as a pinned standard across Harmonize → Exchange → Learn + reuse
- OutputWhat becomes possible
A handoff the next system or team can validate against the same release
03
A concrete example
Pin HGVS 21.1.4, require accession.version reference identifiers, validate syntax and reference alleles, normalize supported expressions, and retain the submitted expression with the parsed representation.
Why it matters: Provides precise variant-language features and auditable labels, while model joins still require reference normalization, transcript policy, and separately governed clinical interpretation.
04
What it fits with
Complements GA4GH VRS computable variant objects, refget reference-sequence identity, and VCF or BCF record exchange. The original HGVS expression should remain traceable after normalization.
- Data model / schemaGA4GH VRS
Both support Omics and Clinical and Laboratory work and meet around Harmonize, Exchange, Learn + reuse. Compare their roles before treating them as interchangeable.
Explore relationship - Ontology ecosystemOBO Foundry
Both support Laboratory and Clinical and Omics work and meet around Harmonize, Learn + reuse. Compare their roles before treating them as interchangeable.
Explore relationship - Data model / schemaPhenopackets
Both support Clinical and Omics work and meet around Harmonize, Exchange, Learn + reuse. Compare their roles before treating them as interchangeable.
Explore relationship - Metadata profileSDRF-Proteomics
Both support Omics and Laboratory work and meet around Harmonize, Exchange, Learn + reuse. Compare their roles before treating them as interchangeable.
Explore relationship
05
Implementation starter
Start with one bounded handoff. Pin, test, and review it before scaling.
Define one handoff, its accountable owner, and the decision HGVS must support.
Pin the exact version and companion artifacts: 21.1.4 · 2026-05-11.
Map one representative input to the required standard artifacts.
Test the result against the canonical source and record every exception.
Preserve the source data, mappings, and review evidence before scaling.
06
Test the main limitation
One biological variant can have several valid descriptions against different references or transcripts. HGVS does not encode pathogenicity, evidence strength, observed genotype, or cohort frequency, and syntax validity alone does not establish biological correctness.
Run one representative end-to-end pilot and record exactly where HGVS loses context, needs an extension, or depends on another standard.
Machine-readable output may still be unfit for analysis or ML.
Test the output for missing context, provenance, terminology alignment, time leakage, and the intended downstream decision. Provides precise variant-language features and auditable labels, while model joins still require reference normalization, transcript policy, and separately governed clinical interpretation.
07
Official resources
Specifications, diagrams, examples, and guides from the organizations that maintain them.
HGVS Nomenclature 21.1.4
Official publisher or steward guidance for this standard profile.
- Publisher
- HGVS Variant Nomenclature Committee · Human Genome Organisation