Translate HGVS, rsIDs & ClinVar IDs | Preserve Genomic Variant Identity

To translate HGVS variant descriptions, dbSNP rsIDs and ClinVar Variation IDs accurately, a translator must separate genomic notation from the human-language explanation around it. Genetics papers, molecular reports, research databases and educational resources often place gene names, reference sequences, HGVS expressions, rs identifiers and ClinVar identifiers in the same sentence. The prose may need translation; the variant notation and database identifiers generally must remain exact. One missing character, version number or prefix can point to a different sequence position or another database record.

This guide explains how to translate genomic variant information without changing HGVS expressions, reference-sequence accessions, dbSNP rsIDs, ClinVar Variation IDs or ClinVar Allele IDs. It solves one specific search intent: what does each notation or identifier represent, what may be translated around it, why reference sequence and genome build matter, how HGVS descriptions differ from database IDs, and how multilingual scientific documents can preserve the same variant identity after translation.

The working rule is translate the explanation, preserve the governed variant notation and identifiers, record the reference context, and verify the relationship between every string. HGVS recommendations require variant descriptions to be tied to an accepted reference sequence and use defined prefixes such as c., g., p. and r.; dbSNP rsIDs identify RefSNP records; ClinVar assigns Variation IDs and Allele IDs to its own records. These systems are related but not interchangeable, and this article is about notation and data integrity rather than clinical interpretation. It connects to Master Art of Translation, the protected Vocabulary Learning Hub, and How English Works without creating a competing medical or genomics hub.

One variant can have several representations

The same biological change can be described by HGVS notation, an rsID, a ClinVar Variation ID, an Allele ID and genomic coordinates. Calling all of them the variant number hides different database and notation roles. Map every representation before translating prose. Treat the human-readable explanation as translatable, the variant expression or database ID as protected, and the reference sequence or namespace as required context. This prevents a valid-looking target string from referring to another coordinate system or record.

Before release, ask whether the target preserves both variant identity and reference context. Another reader should be able to reproduce the same database lookup or sequence-relative description without inferring missing transcript, build or namespace information.

HGVS is a notation system

HGVS provides recommendations for describing sequence variants relative to an accepted reference sequence. Treating an HGVS expression as ordinary text invites punctuation and capitalization errors. Protect the entire expression as structured scientific notation. Verification must test more than characters. Confirm the reference sequence, version, genome build, molecular level and database namespace. A correct rsID beside the wrong HGVS expression is still a broken scientific relationship.

Reference sequence is mandatory context

HGVS descriptions are defined relative to a specific reference sequence. Removing the accession can make a position ambiguous or wrong. Preserve accession and version with the variant description. For files and pipelines, store notation and identifiers as text and exclude them from locale formatting, spell-checking and machine-generated rewriting. Translation should operate around these tokens while the machine-readable genomic layer remains stable.

Reference-sequence version matters

NM_, NC_, NG_ and other accessions can have version suffixes. Dropping .1, .2 or another version can change coordinate interpretation. Keep accession.version exactly when supplied. A strong reviewer checks identity in both directions: start with the target explanation and recover the code, then start from the code and confirm the same sequence context and record. Bidirectional checking catches plausible but contextually false mappings.

Genome build matters

Genomic coordinates can differ between GRCh37, GRCh38 and other assemblies. A coordinate translated without build context may point to another genomic position. Keep assembly metadata visible. Treat the human-readable explanation as translatable, the variant expression or database ID as protected, and the reference sequence or namespace as required context. This prevents a valid-looking target string from referring to another coordinate system or record.

Gene symbol is supporting context

HGVS descriptions can be presented beside HGNC-approved gene symbols. Changing the symbol can disconnect the variant from the intended gene. Preserve approved nomenclature and species context. Verification must test more than characters. Confirm the reference sequence, version, genome build, molecular level and database namespace. A correct rsID beside the wrong HGVS expression is still a broken scientific relationship.

c. prefix means coding DNA reference

HGVS uses c. for positions described relative to a coding DNA reference sequence. Translating the letter c or removing the period breaks the notation. Preserve the prefix exactly. For files and pipelines, store notation and identifiers as text and exclude them from locale formatting, spell-checking and machine-generated rewriting. Translation should operate around these tokens while the machine-readable genomic layer remains stable.

g. prefix means linear genomic reference

HGVS uses g. for a linear genomic reference sequence. A translator can mistake g for an abbreviation that should be localized. Treat g. as governed notation. A strong reviewer checks identity in both directions: start with the target explanation and recover the code, then start from the code and confirm the same sequence context and record. Bidirectional checking catches plausible but contextually false mappings.

m. prefix marks mitochondrial DNA reference

HGVS uses m. for mitochondrial DNA reference sequence descriptions. Changing case or punctuation can invalidate the expression. Preserve notation and explain it outside the code. Treat the human-readable explanation as translatable, the variant expression or database ID as protected, and the reference sequence or namespace as required context. This prevents a valid-looking target string from referring to another coordinate system or record.

n. prefix marks non-coding DNA reference

HGVS uses n. for non-coding DNA reference sequence numbering. It is not interchangeable with c. even when the same locus is discussed. Keep the prefix tied to the correct reference sequence. Verification must test more than characters. Confirm the reference sequence, version, genome build, molecular level and database namespace. A correct rsID beside the wrong HGVS expression is still a broken scientific relationship.

p. prefix marks protein-level consequence

Protein-level HGVS uses p. and amino-acid notation. Replacing p. with a translated abbreviation breaks parser expectations. Translate the explanatory consequence, not the HGVS string. For files and pipelines, store notation and identifiers as text and exclude them from locale formatting, spell-checking and machine-generated rewriting. Translation should operate around these tokens while the machine-readable genomic layer remains stable.

r. prefix marks RNA-level description

HGVS uses r. for RNA reference descriptions. Case and residue notation differ from DNA conventions. Preserve the complete expression exactly. A strong reviewer checks identity in both directions: start with the target explanation and recover the code, then start from the code and confirm the same sequence context and record. Bidirectional checking catches plausible but contextually false mappings.

o. prefix can describe circular genomic reference

HGVS recommendations include o. for circular genomic reference sequences. Rare notation can look like a typo to editors. Verify against HGVS rather than normalizing unfamiliar prefixes. Treat the human-readable explanation as translatable, the variant expression or database ID as protected, and the reference sequence or namespace as required context. This prevents a valid-looking target string from referring to another coordinate system or record.

Colon separates reference from variant description

HGVS uses a colon between accession.version and the actual variant expression. Replacing the colon with target-language punctuation can break automated parsing. Protect punctuation inside the expression. Verification must test more than characters. Confirm the reference sequence, version, genome build, molecular level and database namespace. A correct rsID beside the wrong HGVS expression is still a broken scientific relationship.

No spaces inside HGVS descriptions

HGVS states that spaces are not permitted within variant descriptions. Typography or line-wrapping tools can insert spaces for readability. Keep the machine expression continuous. For files and pipelines, store notation and identifiers as text and exclude them from locale formatting, spell-checking and machine-generated rewriting. Translation should operate around these tokens while the machine-readable genomic layer remains stable.

Greater-than sign has defined meaning

The > character indicates substitutions at DNA or RNA level. Replacing it with an arrow symbol changes the notation. Use typographic explanation outside the HGVS field. A strong reviewer checks identity in both directions: start with the target explanation and recover the code, then start from the code and confirm the same sequence context and record. Bidirectional checking catches plausible but contextually false mappings.

Underscore marks ranges

HGVS uses underscore to express ranges in relevant descriptions. Editors sometimes replace it with a hyphen because that looks more natural. Preserve the underscore because hyphen can mean something else. Treat the human-readable explanation as translatable, the variant expression or database ID as protected, and the reference sequence or namespace as required context. This prevents a valid-looking target string from referring to another coordinate system or record.

del, dup, ins and inv are notation tokens

HGVS uses standardized abbreviations for deletion, duplication, insertion and inversion. Expanding or translating these tokens inside the variant string creates nonstandard notation. Translate their meanings only in prose. Verification must test more than characters. Confirm the reference sequence, version, genome build, molecular level and database namespace. A correct rsID beside the wrong HGVS expression is still a broken scientific relationship.

fs and ext are structured protein notation

Frameshift and extension descriptions use standardized tokens. A spell-checker can flag them as errors and expand them. Protect notation from linguistic correction. For files and pipelines, store notation and identifiers as text and exclude them from locale formatting, spell-checking and machine-generated rewriting. Translation should operate around these tokens while the machine-readable genomic layer remains stable.

Parentheses can signal predicted consequences or uncertainty

HGVS uses parentheses for defined interpretive states. Removing them for cleaner typography can change the scientific meaning. Preserve parentheses exactly. A strong reviewer checks identity in both directions: start with the target explanation and recover the code, then start from the code and confirm the same sequence context and record. Bidirectional checking catches plausible but contextually false mappings.

Question mark signals unknown position

The question mark can have a formal meaning inside HGVS notation. Copy editors may treat it as sentence punctuation. Keep it inside the protected expression. Treat the human-readable explanation as translatable, the variant expression or database ID as protected, and the reference sequence or namespace as required context. This prevents a valid-looking target string from referring to another coordinate system or record.

Equals sign can indicate no sequence change at a level

HGVS uses = in specific descriptions. Replacing it with a word such as unchanged destroys standard syntax. Explain outside the code and retain =. Verification must test more than characters. Confirm the reference sequence, version, genome build, molecular level and database namespace. A correct rsID beside the wrong HGVS expression is still a broken scientific relationship.

Reference direction and 3-prime rule matter

HGVS applies positional rules to standardize descriptions. Two visually similar expressions can represent different normalized descriptions. Do not rewrite coordinates without a variant-normalization workflow. For files and pipelines, store notation and identifiers as text and exclude them from locale formatting, spell-checking and machine-generated rewriting. Translation should operate around these tokens while the machine-readable genomic layer remains stable.

Gene-level and protein-level descriptions are not interchangeable

A DNA change and predicted protein consequence describe different biological levels. Copying one into the other’s field can create a false record. Label DNA, RNA and protein layers separately. A strong reviewer checks identity in both directions: start with the target explanation and recover the code, then start from the code and confirm the same sequence context and record. Bidirectional checking catches plausible but contextually false mappings.

Predicted and observed consequences differ

HGVS uses conventions that can distinguish predicted from experimentally determined consequences. Dropping parentheses can overstate certainty. Preserve the notation and translate the explanatory status carefully. Treat the human-readable explanation as translatable, the variant expression or database ID as protected, and the reference sequence or namespace as required context. This prevents a valid-looking target string from referring to another coordinate system or record.

One-letter versus three-letter amino-acid notation

HGVS permits defined protein notation and recommends clear amino-acid representation. Translating amino-acid codes into target-language abbreviations breaks international conventions. Keep standard biochemical codes. Verification must test more than characters. Confirm the reference sequence, version, genome build, molecular level and database namespace. A correct rsID beside the wrong HGVS expression is still a broken scientific relationship.

Transcript choice changes c. coordinates

The same genomic variant can have different c. descriptions on different transcripts. Removing transcript accession makes the notation hard to reproduce. Keep transcript and version together. For files and pipelines, store notation and identifiers as text and exclude them from locale formatting, spell-checking and machine-generated rewriting. Translation should operate around these tokens while the machine-readable genomic layer remains stable.

MANE and preferred transcript context

Modern clinical and research workflows may use MANE reference transcripts for consistency. A translator should not substitute another transcript because the gene symbol matches. Preserve the reference chosen by the source. A strong reviewer checks identity in both directions: start with the target explanation and recover the code, then start from the code and confirm the same sequence context and record. Bidirectional checking catches plausible but contextually false mappings.

Genomic coordinate alone is not HGVS context

A chromosome position without assembly and reference can be incomplete. Converting it to an HGVS expression requires more than language translation. Do not synthesize notation unless the project explicitly includes variant normalization. Treat the human-readable explanation as translatable, the variant expression or database ID as protected, and the reference sequence or namespace as required context. This prevents a valid-looking target string from referring to another coordinate system or record.

dbSNP rsID identifies a RefSNP record

An rs identifier points to a dbSNP RefSNP record. It is not the same object as an HGVS description or ClinVar Variation ID. Preserve the rs prefix and digits. Verification must test more than characters. Confirm the reference sequence, version, genome build, molecular level and database namespace. A correct rsID beside the wrong HGVS expression is still a broken scientific relationship.

rs prefix is not translatable

The letters rs are part of the database identifier. Replacing them with target-language initials makes the ID unusable. Keep rsID strings unchanged. For files and pipelines, store notation and identifiers as text and exclude them from locale formatting, spell-checking and machine-generated rewriting. Translation should operate around these tokens while the machine-readable genomic layer remains stable.

An rsID can represent a database locus record

dbSNP identifiers are database records that can aggregate submitted observations. Assuming one rsID equals one simple HGVS string can oversimplify the data. Use the database record for mapping. A strong reviewer checks identity in both directions: start with the target explanation and recover the code, then start from the code and confirm the same sequence context and record. Bidirectional checking catches plausible but contextually false mappings.

Merged rsIDs require history awareness

dbSNP records can be merged or updated over time. Replacing a historical rsID silently can make an old paper hard to reproduce. Preserve source-period ID and add current cross-reference separately. Treat the human-readable explanation as translatable, the variant expression or database ID as protected, and the reference sequence or namespace as required context. This prevents a valid-looking target string from referring to another coordinate system or record.

ClinVar Variation ID is its own namespace

ClinVar assigns a unique integer Variation ID to variant sets represented in submitted records. A bare integer without the label can be confused with other database IDs. Keep the ClinVar namespace visible. Verification must test more than characters. Confirm the reference sequence, version, genome build, molecular level and database namespace. A correct rsID beside the wrong HGVS expression is still a broken scientific relationship.

ClinVar Allele ID is different from Variation ID

ClinVar also assigns Allele IDs to individual variants. The two numeric namespaces overlap, so context matters. Label Variation ID and Allele ID explicitly. For files and pipelines, store notation and identifiers as text and exclude them from locale formatting, spell-checking and machine-generated rewriting. Translation should operate around these tokens while the machine-readable genomic layer remains stable.

VCV and RCV accessions are another ClinVar layer

ClinVar exposes accessions for aggregate variation and condition-related records. These accessions are not interchangeable with integer Variation IDs. Preserve accession type and version. A strong reviewer checks identity in both directions: start with the target explanation and recover the code, then start from the code and confirm the same sequence context and record. Bidirectional checking catches plausible but contextually false mappings.

Clinical significance is not part of the identifier

ClinVar records can contain interpretations such as pathogenic or uncertain significance. The interpretation can change while the variant identity remains. Translate interpretation separately from the ID and preserve source date. Treat the human-readable explanation as translatable, the variant expression or database ID as protected, and the reference sequence or namespace as required context. This prevents a valid-looking target string from referring to another coordinate system or record.

Variant identity is not clinical meaning

A correct rsID or HGVS expression does not by itself establish diagnosis, prognosis or treatment. Readers may overread a precise identifier as a clinical conclusion. Keep this article focused on notation and data integrity. Verification must test more than characters. Confirm the reference sequence, version, genome build, molecular level and database namespace. A correct rsID beside the wrong HGVS expression is still a broken scientific relationship.

Condition names are another terminology layer

ClinVar records link variants to conditions with their own names and identifiers. Translating the condition name does not change the variant ID. Preserve each ontology or database namespace separately. For files and pipelines, store notation and identifiers as text and exclude them from locale formatting, spell-checking and machine-generated rewriting. Translation should operate around these tokens while the machine-readable genomic layer remains stable.

Chromosome labels can be structured data

chr1, chrX and related labels can appear in variant files. Replacing them with localized words can break software. Translate explanatory headings, not the coordinate labels. A strong reviewer checks identity in both directions: start with the target explanation and recover the code, then start from the code and confirm the same sequence context and record. Bidirectional checking catches plausible but contextually false mappings.

VCF fields are machine-readable syntax

Variant Call Format contains fixed columns and structured INFO fields. Translating keys or separators corrupts the data file. Keep machine fields unchanged and localize documentation around them. Treat the human-readable explanation as translatable, the variant expression or database ID as protected, and the reference sequence or namespace as required context. This prevents a valid-looking target string from referring to another coordinate system or record.

REF and ALT alleles are sequence data

VCF REF and ALT columns contain biological sequence representations. They are not words or abbreviations. Never translate nucleotide strings. Verification must test more than characters. Confirm the reference sequence, version, genome build, molecular level and database namespace. A correct rsID beside the wrong HGVS expression is still a broken scientific relationship.

Nucleotide letters follow biochemical conventions

A, C, G, T and other IUPAC nucleotide symbols are international sequence notation. Replacing them with target-script letters creates different data. Preserve sequence symbols. For files and pipelines, store notation and identifiers as text and exclude them from locale formatting, spell-checking and machine-generated rewriting. Translation should operate around these tokens while the machine-readable genomic layer remains stable.

Case can matter by notation level

HGVS DNA and RNA conventions use case deliberately. Global case conversion can corrupt standard form. Exclude variant strings from title-case or sentence-case rules. A strong reviewer checks identity in both directions: start with the target explanation and recover the code, then start from the code and confirm the same sequence context and record. Bidirectional checking catches plausible but contextually false mappings.

Smart punctuation is dangerous

Editors can replace hyphens, apostrophes or greater-than signs with typographic forms. Visually similar Unicode characters may break parsers. Protect raw variant notation. Treat the human-readable explanation as translatable, the variant expression or database ID as protected, and the reference sequence or namespace as required context. This prevents a valid-looking target string from referring to another coordinate system or record.

Spreadsheets can alter identifiers

Long ClinVar or coordinate values can be reformatted and rsIDs can be split or autocorrected. Data corruption may occur before translation begins. Import variant fields as text. Verification must test more than characters. Confirm the reference sequence, version, genome build, molecular level and database namespace. A correct rsID beside the wrong HGVS expression is still a broken scientific relationship.

CSV needs an explicit schema

CSV does not retain strong field types. Applications may infer numbers, dates or formulas from scientific strings. Define code and notation columns as strings. For files and pipelines, store notation and identifiers as text and exclude them from locale formatting, spell-checking and machine-generated rewriting. Translation should operate around these tokens while the machine-readable genomic layer remains stable.

OCR can corrupt variants

Scanned reports can misread punctuation, digits and amino-acid letters. A one-character OCR error can create another plausible variant. Verify against the structured source or database. A strong reviewer checks identity in both directions: start with the target explanation and recover the code, then start from the code and confirm the same sequence context and record. Bidirectional checking catches plausible but contextually false mappings.

Machine translation can expand notation tokens

MT may interpret del, dup or fs as abbreviations needing translation. The result becomes nonstandard HGVS. Lock variant strings before automated translation. Treat the human-readable explanation as translatable, the variant expression or database ID as protected, and the reference sequence or namespace as required context. This prevents a valid-looking target string from referring to another coordinate system or record.

Translation memory can preserve outdated reference versions

Old projects may reuse older transcript versions or nomenclature. A high TM match can silently carry obsolete context into a new record. Take reference accessions from the current source. Verification must test more than characters. Confirm the reference sequence, version, genome build, molecular level and database namespace. A correct rsID beside the wrong HGVS expression is still a broken scientific relationship.

Search-and-replace can damage many variants at once

Bulk punctuation or case changes can affect every HGVS string in a corpus. One global rule can create thousands of invalid descriptions. Restrict find-and-replace to translatable fields. For files and pipelines, store notation and identifiers as text and exclude them from locale formatting, spell-checking and machine-generated rewriting. Translation should operate around these tokens while the machine-readable genomic layer remains stable.

Historical papers need source fidelity

Older literature may use noncurrent nomenclature or variant descriptions. Modernizing everything silently changes the quoted scientific record. Add normalized current forms as annotations, not replacements. A strong reviewer checks identity in both directions: start with the target explanation and recover the code, then start from the code and confirm the same sequence context and record. Bidirectional checking catches plausible but contextually false mappings.

Worked example: one variant, several IDs

A fictional report gives one HGVS expression, one rsID and one ClinVar Variation ID. Each string identifies or describes the variant through a different system. Preserve all three and label their roles. Treat the human-readable explanation as translatable, the variant expression or database ID as protected, and the reference sequence or namespace as required context. This prevents a valid-looking target string from referring to another coordinate system or record.

Worked example: transcript change

A fictional genomic change has different c. coordinates on two transcripts. Choosing the wrong transcript can make both HGVS strings individually valid but contextually wrong. Keep reference accession and version with each expression. Verification must test more than characters. Confirm the reference sequence, version, genome build, molecular level and database namespace. A correct rsID beside the wrong HGVS expression is still a broken scientific relationship.

Worked example: ClinVar ID ambiguity

A report lists a bare integer from ClinVar without saying Variation ID or Allele ID. The numbering systems can overlap. Restore the field label from the structured source before translating. For files and pipelines, store notation and identifiers as text and exclude them from locale formatting, spell-checking and machine-generated rewriting. Translation should operate around these tokens while the machine-readable genomic layer remains stable.

Error clinic

Common failures include changing prefixes, spaces, punctuation, reference versions, rs prefixes and ClinVar namespaces. These errors can survive fluent scientific prose review. Run a dedicated variant-notation QA pass. A strong reviewer checks identity in both directions: start with the target explanation and recover the code, then start from the code and confirm the same sequence context and record. Bidirectional checking catches plausible but contextually false mappings.

Release checklist

HGVS string, reference accession, version, genome build, gene symbol, rsID and ClinVar namespace all need verification. Checking only the translated explanation is insufficient. Validate both token integrity and context. Treat the human-readable explanation as translatable, the variant expression or database ID as protected, and the reference sequence or namespace as required context. This prevents a valid-looking target string from referring to another coordinate system or record.

Frequently asked questions

HGVS strings, rsIDs and ClinVar IDs should not be translated. Users often ask whether an rsID is the same as an HGVS description. Explain that notation and database identifiers serve different functions. Verification must test more than characters. Confirm the reference sequence, version, genome build, molecular level and database namespace. A correct rsID beside the wrong HGVS expression is still a broken scientific relationship.

Connection to eduKateSG architecture

This specialist owner protects genomic notation and identifier integrity. A broad genomics hub would overlap existing biotechnology owners. Use this page for variant strings and IDs, and existing owners for domain-wide translation. For files and pipelines, store notation and identifiers as text and exclude them from locale formatting, spell-checking and machine-generated rewriting. Translation should operate around these tokens while the machine-readable genomic layer remains stable.

Authoritative sources

HGVS, NCBI dbSNP and ClinVar publish the governing notation and identifier guidance. Third-party variant tools may normalize or display data differently. Verify identity against authoritative resources. A strong reviewer checks identity in both directions: start with the target explanation and recover the code, then start from the code and confirm the same sequence context and record. Bidirectional checking catches plausible but contextually false mappings.

Reference verification route

For sequence-variant notation, use the current HGVS Nomenclature recommendations. For RefSNP identifiers, use NCBI dbSNP. For ClinVar identifier semantics, use NCBI’s ClinVar identifiers documentation and ClinVar records. These resources define different layers of variant description and should remain distinct in translation.

Translate | HGVS Variant Descriptions, dbSNP rsIDs and ClinVar Variation IDs — Preserve Genomic Variant Identity Across Languages