eduKateSG · Why Science?
Give each human gene a unique approved symbol and stable identity—without confusing the gene with its protein, transcript, variant, phenotype or clinical interpretation
Choose the closest route, then return to the full index whenever you need the wider evidence chain.
Science learning becomes powerful when students can tell a measured pattern from a model, a statistical decision from a mechanism, and a useful lead from a finished conclusion. The HUGO Gene Nomenclature Committee approves unique symbols and descriptive names for human loci, including protein-coding genes, non-coding RNA genes and pseudogenes. HGNC states that each gene receives one approved symbol and a stable unique HGNC ID; the ID remains linked to the gene even if nomenclature is updated. Current guidelines say symbols use uppercase Latin letters and Arabic numerals, generally avoid punctuation and should not duplicate common abbreviations that obstruct retrieval. HGNC does not routinely name transcript or splice isoforms separately. An approved symbol makes communication and data retrieval clearer, but it does not identify a particular transcript, protein isoform, variant, disease mechanism or clinical diagnosis. This guide supports Primary Science, PSLE Science, Secondary Science, O-Level Science and STEM education as a longform evidence-reading route; it is not medical advice, a laboratory protocol, an admission promise or a career guarantee.
Related eduKate reading: ClinGen gene–disease validity and evidence curation; ClinVar classifications, evidence and conflicts; Mondo Disease Ontology and harmonised disease concepts; careers by subject capability; Science Learning Hub; Education Hub; STEM Education; Careers by Subject Capability.
Primary and official sources checked on 13 October 2026: HUGO Gene Nomenclature Committee official About page, checked 13 October 2026; HGNC current guidelines for naming human genes, checked 13 October 2026; HGNC symbol report help, checked 13 October 2026; HGNC recommended nomenclature instructions to authors, checked 13 October 2026; 2026 Singapore–Cambridge O-Level Biology syllabus; MOE G2/G3 Lower Secondary Science teaching and learning syllabus; 2026 MOE G2 Computing syllabus. Standards, terminologies, classifications and recommendations can change, so preserve dated documentation, exact source data and software versions.
A deeper reading route
Gene names look simple until several laboratories use the same abbreviation for different genes or several aliases for one gene. HGNC provides a community-governed solution for human loci: one approved symbol, one descriptive name and a stable identifier for each named gene. Standard naming lets papers, databases and software refer to the same locus more reliably.
The symbol and HGNC ID play different roles. A symbol is a concise human-facing label designed for communication. An HGNC ID is the stable database identifier in the form HGNC:#. Symbols may occasionally change to improve accuracy or avoid harm, while the ID provides continuity across the update.
HGNC’s current guidelines give symbols a disciplined form. They use uppercase Latin letters and Arabic numerals, generally avoid punctuation, exclude species references or a generic “G” for gene and should not duplicate commonly used abbreviations. The rules support retrieval as well as readability: a memorable but ambiguous symbol can pollute thousands of searches.
Naming aims to reflect a gene product’s key normal function when evidence supports it. Without functional evidence, names can use recognised domains, homology or open-reading-frame location. This hierarchy of evidence keeps a temporary or descriptive name from claiming a biological role that has not yet been demonstrated.
Gene families benefit from parallel construction. Related symbols can share a root when sequence homology, function or complex membership supports the grouping. Family structure makes patterns visible, but researchers should not infer identical function from a shared root alone.
A gene is not identical to its transcripts or protein products. HGNC explicitly does not routinely assign separate gene symbols to isoforms. Transcript accessions, protein accessions and versioned sequence identifiers carry the detail needed for isoform-specific experiments. Writing only the gene symbol can be insufficient for a reproducible assay.
Aliases and previous symbols are essential for historical search. An older paper can use a name that is no longer approved, and automated text mining can otherwise split one evidence trail into several apparent genes. Databases should retain aliases for discovery while displaying the current approved symbol and stable ID.
Gene symbols are species-specific conventions. Human symbols use uppercase, while other organisms follow their own committees and styles. Orthologous genes can have related symbols without being the same record. Cross-species analysis should use species, taxon and stable database identifiers rather than typography alone.
Nomenclature does not establish disease validity. ClinGen evaluates gene–disease relationships, ClinVar curates assertions about variants, and Mondo organises disease concepts. A clear HGNC identity helps join those evidence systems, but each claim retains its own method, date and level of certainty.
For students, HGNC shows that scientific vocabulary is infrastructure. Naming is not cosmetic: it influences search, data joins, reproducibility and safety. The hopeful habit is simple—use the approved symbol, cite the stable ID when precision matters and preserve aliases so older knowledge remains findable.
Spreadsheet software has historically transformed some gene-like strings into dates. Data pipelines should import symbols as text, validate them against current HGNC records and retain stable IDs. Visual correctness in one worksheet is not proof that stored values survived.
Case changes are not trivial. Human gene symbols are written in uppercase italics in many scientific contexts, while proteins commonly use non-italic uppercase styling. Databases should store the identifier separately from typographic presentation.
Provisional symbols can change as biology becomes clearer. A pipeline that treats the symbol as an immutable primary key will fragment history. Use HGNC IDs internally and refresh display symbols through a versioned process.
Withdrawn or previous nomenclature should not be silently deleted from search indexes. It can be labelled clearly and redirected to the current record, with the decision date and reason available for audit.
Gene panels must pin the symbol set, HGNC IDs, transcript choices and genome assembly. A panel name alone does not define what regions or variants were analysed.
Text-mining systems should detect ambiguous aliases, surrounding species and whether a mention concerns gene, protein, phenotype or an unrelated abbreviation. Precision is more valuable than forcing every uppercase token into a gene record.
Publishing variant findings requires a separate variant nomenclature such as HGVS plus a reference sequence, coordinate system and allele context. The gene symbol helps orientation but cannot identify the variant.
Individual genetic information is sensitive. Stable identifiers improve interoperability and can increase linkability, so research and clinical systems need consent, access control, minimisation and responsible disclosure.
| Stage | Question | Evidence | Responsible output |
|---|---|---|---|
| Name | Which human locus is being discussed? | Approved symbol, descriptive name and HGNC ID | A stable gene identity |
| Qualify | Which molecular object is measured? | Transcript, protein, sequence version, species and assembly | A reproducible experimental target |
| Connect | Which evidence concerns the gene? | Aliases, database links, variants and disease assertions | A traceable evidence network |
| Validate | Can another team resolve the same locus? | Current record, history, identifiers and methods | Clear scientific communication |
Inside this guide
1–12 · Foundations and design
- 1. Start with the biological object
- 2. Use the approved human symbol
- 3. Store the stable HGNC ID
- 4. Keep the descriptive name
- 5. Follow the character rules
- 6. Avoid common abbreviations
- 7. Name from supported function
- 8. Use structural evidence cautiously
- 9. Use family roots consistently
- 10. Separate gene from transcript
- 11. Separate gene from protein
- 12. Separate gene from variant
13–24 · Models and estimation
- 13. Separate gene from phenotype
- 14. Preserve aliases
- 15. Preserve previous symbols
- 16. Handle symbol updates
- 17. Keep species explicit
- 18. Protect formatting in spreadsheets
- 19. Use typography as presentation
- 20. Validate literature searches
- 21. Build gene panels reproducibly
- 22. Connect to ClinGen
- 23. Connect to ClinVar
- 24. Connect to disease ontologies
25–36 · Diagnostics and interpretation
- 25. Validate automated entity linking
- 26. Protect genetic privacy
- 27. Preserve provenance
- 28. Connect to Primary Science
- 29. Connect to Secondary Science
- 30. Connect to mathematics
- 31. Connect to computing
- 32. Connect to pathways
- 33. Did you know?
- 34. Write a reader-ready methods note
- 35. Build a validation ladder
- 36. Finish with a reproducible bundle
Section 1 of 36
1. Start with the biological object
Decide whether the statement concerns a gene locus, transcript, RNA product, protein, variant or phenotype.
Working checkpoint — HGNC: Name the object before selecting an identifier. Keep HGNC ID, approved symbol, descriptive name, aliases, history, species, transcript or protein identifiers and access decision together.
For a classroom model, update fictional display names while keeping stable card numbers.
Section 2 of 36
2. Use the approved human symbol
HGNC approves one unique symbol for each named human gene.
Working checkpoint — human gene symbol: Resolve the symbol in the current HGNC database. Read every gene mention beside molecular object, assembly, sequence version, assay, variant and evidence source.
For future study, connect genetics to data curation and publishing while checking pathways separately.
Section 3 of 36
3. Store the stable HGNC ID
Every named gene receives an HGNC ID that stays linked to the gene even if nomenclature changes.
Working checkpoint — HGNC ID: Use HGNC:# as the durable internal key. Preserve previous symbols and validation receipts; nomenclature updates are not silent identity changes.
For writing, cite HGNC ID, current symbol, molecular object, sequence version and evidence source.
Section 4 of 36
4. Keep the descriptive name
The full approved name adds readable context to the shorter symbol.
Working checkpoint — gene nomenclature: Display symbol and name together where ambiguity matters. Separate naming authority from gene function, disease validity, variant effect and clinical diagnosis.
For students, ask why a short gene label and a stable database ID do different jobs.
Section 5 of 36
5. Follow the character rules
Current symbols use uppercase Latin letters and Arabic numerals, with punctuation generally avoided except in defined groups.
Working checkpoint — alias symbol: Validate form but rely on the official record. Treat species, symbol history and molecular object as scientific inputs: one omission can misjoin evidence.
For parents, ask whether a genetic claim identifies the exact gene, variant and evidence level.
Section 6 of 36
6. Avoid common abbreviations
HGNC aims to avoid symbols identical to widely used abbreviations because they obstruct literature retrieval.
Working checkpoint — gene family: Test candidate names in scientific search. Keep HGNC ID, approved symbol, descriptive name, aliases, history, species, transcript or protein identifiers and access decision together.
For a classroom model, update fictional display names while keeping stable card numbers.
Section 7 of 36
7. Name from supported function
Protein-coding genes are preferably named for a key normal function of the gene product when evidence is adequate.
Working checkpoint — HGNC: Do not turn a speculative role into an approved-looking label. Read every gene mention beside molecular object, assembly, sequence version, assay, variant and evidence source.
For future study, connect genetics to data curation and publishing while checking pathways separately.
Section 8 of 36
8. Use structural evidence cautiously
Without functional evidence, naming may use domains, motifs, homology or open-reading-frame context.
Working checkpoint — human gene symbol: Preserve the evidence basis for the name. Preserve previous symbols and validation receipts; nomenclature updates are not silent identity changes.
For writing, cite HGNC ID, current symbol, molecular object, sequence version and evidence source.
Section 9 of 36
9. Use family roots consistently
Related genes can share a root symbol that supports grouping by homology, function or complex membership.
Working checkpoint — HGNC ID: Do not infer identical activity from the root alone. Separate naming authority from gene function, disease validity, variant effect and clinical diagnosis.
For students, ask why a short gene label and a stable database ID do different jobs.
Section 10 of 36
10. Separate gene from transcript
HGNC does not routinely give distinct symbols to splice or transcript isoforms.
Working checkpoint — gene nomenclature: Add a versioned transcript accession for isoform-specific work. Treat species, symbol history and molecular object as scientific inputs: one omission can misjoin evidence.
For parents, ask whether a genetic claim identifies the exact gene, variant and evidence level.
Section 11 of 36
11. Separate gene from protein
A gene symbol or ID does not identify one protein sequence or post-translational state.
Working checkpoint — alias symbol: Add a protein accession and version when required. Keep HGNC ID, approved symbol, descriptive name, aliases, history, species, transcript or protein identifiers and access decision together.
For a classroom model, update fictional display names while keeping stable card numbers.
Section 12 of 36
12. Separate gene from variant
Variants need their own precise nomenclature, reference and allele context.
Working checkpoint — gene family: Use the gene identity only as one layer. Read every gene mention beside molecular object, assembly, sequence version, assay, variant and evidence source.
For future study, connect genetics to data curation and publishing while checking pathways separately.
Section 13 of 36
13. Separate gene from phenotype
HGNC no longer assigns nomenclature to phenotypes where the associated gene is unidentified.
Working checkpoint — HGNC: Use an appropriate phenotype or disease identifier. Preserve previous symbols and validation receipts; nomenclature updates are not silent identity changes.
For writing, cite HGNC ID, current symbol, molecular object, sequence version and evidence source.
Section 14 of 36
14. Preserve aliases
Alias symbols and names help retrieve historical literature and external data.
Working checkpoint — human gene symbol: Store aliases as search terms, not current display identity. Separate naming authority from gene function, disease validity, variant effect and clinical diagnosis.
For students, ask why a short gene label and a stable database ID do different jobs.
Section 15 of 36
15. Preserve previous symbols
Previous approved symbols document genuine nomenclature history.
Working checkpoint — HGNC ID: Keep change dates and redirect to the current record. Treat species, symbol history and molecular object as scientific inputs: one omission can misjoin evidence.
For parents, ask whether a genetic claim identifies the exact gene, variant and evidence level.
Section 16 of 36
16. Handle symbol updates
HGNC seeks stability but can update nomenclature in exceptional circumstances or replace provisional naming.
Working checkpoint — gene nomenclature: Refresh displays without changing the stable ID. Keep HGNC ID, approved symbol, descriptive name, aliases, history, species, transcript or protein identifiers and access decision together.
For a classroom model, update fictional display names while keeping stable card numbers.
Section 17 of 36
17. Keep species explicit
Human nomenclature differs from mouse and other organism conventions. Similar symbols can represent orthologues, not the same record.
Working checkpoint — alias symbol: Store taxon and species with every gene ID. Read every gene mention beside molecular object, assembly, sequence version, assay, variant and evidence source.
For future study, connect genetics to data curation and publishing while checking pathways separately.
Section 18 of 36
18. Protect formatting in spreadsheets
Automatic date conversion, lost italics and case changes can corrupt symbols.
Working checkpoint — gene family: Import as text and validate after export. Preserve previous symbols and validation receipts; nomenclature updates are not silent identity changes.
For writing, cite HGNC ID, current symbol, molecular object, sequence version and evidence source.
Section 19 of 36
19. Use typography as presentation
Italic gene symbols and non-italic protein labels can aid human reading but do not supply database identity.
Working checkpoint — HGNC: Store semantics separately from styling. Separate naming authority from gene function, disease validity, variant effect and clinical diagnosis.
For students, ask why a short gene label and a stable database ID do different jobs.
Section 20 of 36
20. Validate literature searches
A current symbol plus aliases, previous symbols and stable IDs improves recall without merging unrelated abbreviations.
Working checkpoint — human gene symbol: Publish the exact query and search date. Treat species, symbol history and molecular object as scientific inputs: one omission can misjoin evidence.
For parents, ask whether a genetic claim identifies the exact gene, variant and evidence level.
Section 21 of 36
21. Build gene panels reproducibly
A panel needs HGNC IDs, current symbols, inclusion rationale, version, transcripts and target regions.
Working checkpoint — HGNC ID: Archive the complete panel definition. Keep HGNC ID, approved symbol, descriptive name, aliases, history, species, transcript or protein identifiers and access decision together.
For a classroom model, update fictional display names while keeping stable card numbers.
Section 22 of 36
22. Connect to ClinGen
ClinGen evaluates gene–disease validity; HGNC identifies the gene being evaluated.
Working checkpoint — gene nomenclature: Keep identity and evidence classification separate. Read every gene mention beside molecular object, assembly, sequence version, assay, variant and evidence source.
For future study, connect genetics to data curation and publishing while checking pathways separately.
Section 23 of 36
23. Connect to ClinVar
ClinVar records assertions about variants and conditions; a gene symbol is only one navigation field.
Working checkpoint — alias symbol: Preserve variation ID, allele and review status. Preserve previous symbols and validation receipts; nomenclature updates are not silent identity changes.
For writing, cite HGNC ID, current symbol, molecular object, sequence version and evidence source.
Section 24 of 36
24. Connect to disease ontologies
Mondo and other resources identify disease concepts linked to genes in evidence systems.
Working checkpoint — gene family: Do not treat a database link as causal proof. Separate naming authority from gene function, disease validity, variant effect and clinical diagnosis.
For students, ask why a short gene label and a stable database ID do different jobs.
Section 25 of 36
25. Validate automated entity linking
Text-mining tools can confuse aliases with ordinary abbreviations or other species.
Working checkpoint — HGNC: Review ambiguous mentions and report precision. Treat species, symbol history and molecular object as scientific inputs: one omission can misjoin evidence.
For parents, ask whether a genetic claim identifies the exact gene, variant and evidence level.
Section 26 of 36
26. Protect genetic privacy
Gene panels, variants and rare conditions can reveal sensitive information or family relationships.
Working checkpoint — human gene symbol: Apply consent, access control and minimisation. Keep HGNC ID, approved symbol, descriptive name, aliases, history, species, transcript or protein identifiers and access decision together.
For a classroom model, update fictional display names while keeping stable card numbers.
Section 27 of 36
27. Preserve provenance
A reusable record links HGNC ID, symbol, name, aliases, history, species, molecular object and release date.
Working checkpoint — HGNC ID: Make every gene mention resolvable. Read every gene mention beside molecular object, assembly, sequence version, assay, variant and evidence source.
For future study, connect genetics to data curation and publishing while checking pathways separately.
Section 28 of 36
28. Connect to Primary Science
A fictional fictional gene-name card set helps pupils separate an observation from the standardised name or code used to organise it.
Working checkpoint — gene nomenclature: Use invented examples and never use personal health information. Preserve previous symbols and validation receipts; nomenclature updates are not silent identity changes.
For writing, cite HGNC ID, current symbol, molecular object, sequence version and evidence source.
Section 29 of 36
29. Connect to Secondary Science
HGNC supports lessons about classification, evidence, systems, uncertainty and responsible comparison.
Working checkpoint — alias symbol: Trace one coded statement back to its observable evidence. Separate naming authority from gene function, disease validity, variant effect and clinical diagnosis.
For students, ask why a short gene label and a stable database ID do different jobs.
Section 30 of 36
30. Connect to mathematics
Sets, hierarchies, identifiers, denominators and versioned mappings show why definitions must be fixed before quantities are compared.
Working checkpoint — gene family: Work through one small boundary case by hand. Treat species, symbol history and molecular object as scientific inputs: one omission can misjoin evidence.
For parents, ask whether a genetic claim identifies the exact gene, variant and evidence level.
Section 31 of 36
31. Connect to computing
Curated databases, stable identifiers, APIs, symbol checkers, history tables and validators show how software protects biological communication.
Working checkpoint — HGNC: Break one identifier, release, relationship or mapping, then validate and repair it transparently. Keep HGNC ID, approved symbol, descriptive name, aliases, history, species, transcript or protein identifiers and access decision together.
For a classroom model, update fictional display names while keeping stable card numbers.
Section 32 of 36
32. Connect to pathways
HGNC connects genetics, molecular biology, bioinformatics, publishing, data curation and clinical research and can illuminate STEM education and career pathways.
Working checkpoint — human gene symbol: Check current official education and qualification routes separately from this conceptual guide. Read every gene mention beside molecular object, assembly, sequence version, assay, variant and evidence source.
For future study, connect genetics to data curation and publishing while checking pathways separately.
Section 33 of 36
33. Did you know?
An HGNC ID stays linked to the gene even if the approved symbol is updated, which is why the ID is safer than the symbol as a database key.
Working checkpoint — HGNC ID: Explain the fact in plain language, then name what it does not prove. Preserve previous symbols and validation receipts; nomenclature updates are not silent identity changes.
For writing, cite HGNC ID, current symbol, molecular object, sequence version and evidence source.
Section 34 of 36
34. Write a reader-ready methods note
State the standard and release, source data, coding or mapping method, validation, privacy controls and supported claim.
Working checkpoint — gene nomenclature: Keep the note beside the machine-readable record. Separate naming authority from gene function, disease validity, variant effect and clinical diagnosis.
For students, ask why a short gene label and a stable database ID do different jobs.
Section 35 of 36
35. Build a validation ladder
Check identifiers, release, syntax, hierarchy, source fidelity, scientific plausibility, privacy and known fixtures in sequence.
Working checkpoint — alias symbol: Stop at the earliest unresolved layer. Treat species, symbol history and molecular object as scientific inputs: one omission can misjoin evidence.
For parents, ask whether a genetic claim identifies the exact gene, variant and evidence level.
Section 36 of 36
36. Finish with a reproducible bundle
Deliver source receipts, releases, mappings, software versions, tests, hashes and limitations without exposing governed health data.
Working checkpoint — gene family: Make every published claim traceable. Keep HGNC ID, approved symbol, descriptive name, aliases, history, species, transcript or protein identifiers and access decision together.
For a classroom model, update fictional display names while keeping stable card numbers.
Contents · Previous section · Continue to the Science Learning Hub