The field guide / Human Genome Database

Find your bearings in genome data.

Genome databases help organize a vast research landscape. Learn which kind of resource fits your question and what to check before interpreting a record.

There is more than one kind of genome database.

Some resources describe genes and genomic locations. Others collect sequences, population observations, or interpretations of variants. A browser may display several kinds of data as separate tracks. The phrase “human genome database” therefore covers resources with different purposes.

Start by writing down what you need: the location of a gene, the definition of a variant, the evidence attached to a classification, or the frequency of an observation in a study. Choosing a resource around a specific question is more useful than treating any search result as an answer.

Three starting points

  • NCBI Gene: gene-centered information and connections to other biological resources.
  • Ensembl: genome browsing and annotation, including genes, transcripts, and comparative information.
  • ClinVar: submitted classifications of variants in relation to conditions and other contexts.

Use the official NCBI Gene, Ensembl, and ClinVar introduction as entry points. These are independent resources; Geneomix does not operate them or provide access to private genomic datasets.

A location needs a reference.

Coordinates only make sense relative to a particular reference assembly and naming system. Before comparing two records, check the assembly, chromosome, position, and sequence change. For transcript-based descriptions, the transcript identifier and version can also matter.

A useful analogy is a page number in a revised book: the number may point somewhere different in another edition. Do not discard apparently conflicting records before checking whether they use the same reference framework. Our genome database reading guide walks through this habit in more detail.

A record is a collection of evidence.

Look beyond the first label. Ask who submitted the interpretation, which condition it addresses, when the evidence was evaluated, and whether submissions agree. Review status and supporting details help explain how a classification should be read.

A database record cannot independently tell you what a finding means for a particular person. A reported variant may require careful matching to the original laboratory result and a professional interpretation of the relevant context.

Keep a short reading record.

  1. Save the stable record identifier and the date you accessed it.
  2. Record the reference assembly or transcript version.
  3. Note the exact question you were trying to answer.
  4. Separate what the record states from your own inference.
  5. Write down unresolved differences before comparing another resource.

For background, explore genomic DNA basics. If your question begins with a personal report, start with our guide to interpreting report language and seek qualified support for a health-related decision.

Good questions move understanding forward.

Have a topic suggestion or a correction? We’d like to hear it.

Get in touch