Standard HGVS nomenclature is defined by prefix identifiers—c. for coding DNA, g. for genomic DNA, r. for RNA, and p. for protein—paired with a numbering system that starts at the A of the ATG start codon (position +1). Variants are then described with precise operators: substitutions like c.7C>T, deletions like c.6_7del, insertions like c.5_6insTA, duplications like c.4_5dupCG, and frameshifts like p.H3fs. These rules, always anchored to a specific reference sequence accession number, are the universal language for molecular diagnostic reports and the informatic engines that generate them.
The core of HGVS is disciplined consistency: every variant must be mapped to a defined reference sequence, described with a dictated coordinate scheme, and formatted using strict operators. Without this framework, the ambiguity that plagues legacy disease names invades your clinical reports and software pipelines—making database cross-referencing unreliable and regulatory alignment nearly impossible.
Core Formatting Rules for DNA Variants (c. and g.)
Numbering Starts at the ATG Initiation Codon
For coding DNA (c.), position 1 is the first nucleotide of the ATG translation start codon.
There is no position 0.
The 5' untranslated region is numbered with negative integers, e.g., c.-64C>T.
Intronic positions are given relative to the nearest exon boundary, such as c.141+12T>C (12 bases into the intron after coding nucleotide 141).
Describing Substitutions, Deletions, and Insertions
A single nucleotide substitution is written as the position, the reference base, >, and the alternate base: c.125C>G.
Deletions are marked with del and the range, e.g., c.6_7del.
Insertions use ins followed by the inserted sequence: c.5_6insTA.
Duplications use dup: c.4_5dupCG.
Deletion–insertions (indels) combine the descriptors, such as c.112_117delinsTG.
Compound Heterozygous and Allelic Phasing
When two variants exist on different alleles, they are enclosed in brackets separated by a plus sign: c.[2357C>T];[2378CdelA].
This phasing notation is critical for clinical reports because it explicitly states the cis/trans relationship that underpins an autosomal recessive diagnosis.
Formatting Protein Variants (p.)
Amino Acid Changes: Substitutions, Nonsense, and Frameshifts
Protein changes use the one‑letter or three‑letter amino acid code.
A substitution is written as wild‑type residue, position, and mutant residue: p.R2S or p.Gln7Val.
A nonsense mutation is marked with X: p.E4X.
Frameshifts are indicated by fs after the first affected amino acid: p.H3fs (or p.His3fs).
The “fs” notation automatically communicates that the new reading frame leads to a premature stop codon—no need to artificially append “Ter” or a stop position.
One‑Letter vs Three‑Letter Codes
Both codes are acceptable under HGVS, but consistency within a report or software output is mandatory.
Three‑letter codes (e.g., p.Arg2Ser) reduce visual ambiguity for reviewers, while one‑letter codes (p.R2S) are more compact for large‑scale database entries.
All variants must be predictable by your informatic pipeline, so choose the convention that matches your primary data store.
The Importance of Reference Sequences and Gene Annotation
Anchoring to Accession Numbers
An HGVS description is incomplete without the reference sequence accession and version.
Examples include NM_000123.3:c.7C>T for a RefSeq transcript or LRG_199t1:c.7C>T for a Locus Reference Genomic transcript.
In molecular assay reporting software, this anchor ensures that the coordinate system is unambiguous across different genome builds and transcript isoforms.
Italicization and Gene Symbol Rules
Human gene symbols must be italicized in formal documentation (e.g., KRAS), while protein symbols are not (K-Ras).
This distinction prevents the dangerous misannotation that occurs when a variant is reported against the wrong molecule.
Enforcing these typographic rules inside reporting modules directly reduces misinterpretation during clinical sign‑out.
Understanding the Trade‑offs of HGVS Compliance
Abandoning Legacy Names for Precision
Traditional names like “Hb S” or “Factor V Leiden” are deeply embedded in medical practice but fail to distinguish between homologous genes (e.g., HBB vs. HBA2) and often reference outdated amino acid numbering.
Adopting HGVS forces your team to retire these shortcuts, which can initially slow report reading but pays back in zero‑ambiguity database lookup (ClinVar, gnomAD) and safer variant classification.
Implementation Burden in Legacy Systems
Older laboratory information systems and in‑house scripts may hardcode custom nomenclature.
Retrofitting them to produce fully compliant HGVS strings—including correct intronic offsets and protein fs notation—demands a non‑trivial engineering investment.
However, failing to do so makes your output incompatible with modern variant interpretation pipelines and can delay regulatory review.
Regulatory and Database Interoperability
Regulatory bodies increasingly expect HGVS conformity in diagnostic kit submissions and clinical reports.
Variant allele frequencies in population databases are keyed to HGVS strings; a non‑standard name can silently break your classification evidence.
The trade‑off is short‑term conversion effort versus long‑term audit readiness and interoperability.
How to Apply This to Your Project
The best path to HGVS compliance depends on your primary role and immediate constraints.
- If your primary focus is clinical diagnostic reporting: Anchor every variant to an approved RefSeq or LRG transcript (e.g.,
NM_000123.3) and train sign‑out teams to never strip the accession. This single step eliminates the most common source of ambiguity. - If your primary focus is genomic software development: Enforce HGVS syntax validation at the point of data ingestion and build automated converters for legacy names. Use the sequence‑ontology‑aligned grammar to guarantee that your output strings will parse correctly in downstream tools like VEP or Alamut.
- If your primary focus is IVD kit manufacturing: Embed the exact HGVS coordinates in your product specifications, primer design documentation, and synthetic positive control certificates. This ensures that every user of your kit aligns their validation data against the same unambiguous target.
Every hour you invest in rigorous, reference‑anchored HGVS formatting today eliminates days of debugging, reclassification, and clinical confusion tomorrow.
Summary Table:
| Variant Type / Domain | HGVS Prefix / Syntax | Formatting Example | Key Guidelines |
|---|---|---|---|
| Coding DNA | c. |
c.125C>G, c.6_7del |
ATG codon = +1; no position 0; use relative intronic offsets (e.g., c.141+12T>C) |
| Protein | p. |
p.R2S, p.Gln7Val, p.H3fs |
Use 1- or 3-letter codes consistently; X for nonsense, fs for frameshifts |
| Reference Sequence | Accession.Version: |
NM_000123.3:c.7C>T |
Mandatory anchor to ensure coordinate stability across builds and transcript isoforms |
| Phasing / Alleles | [var1];[var2] |
c.[2357C>T];[2378CdelA] |
Enclose phased variants in brackets to define compound heterozygous (cis/trans) status |
Accelerate Your Molecular Assay Success with CamelBio
Ensuring precision from sequence formatting to clinical reporting requires reliable technical foundations. CamelBio provides diagnostic manufacturers, labs, and research institutes with one-stop access to IVD raw materials, technical services, and consulting—covering every stage from concept to clinic.
Whether you are designing molecular assays, standardizing target specifications, or scaling diagnostic pipelines, our expert team is here to help you achieve seamless compliance and accuracy.