Skip to main content
v2026.11,986 entries · CC-BY 4.0

DECIPHER Database: Search, Scope and Data Access

Explore DECIPHER genomic and phenotype records, documented search tools, sharing contexts and the permissions required for research reuse.

Written and maintained by CASRAI Editorial Board

Published

On this page

The DECIPHER database links human genomic variants with phenotype information for rare-disease research. Researchers can search its public records, compare genomic regions and follow up with contributing centres. Public visibility, bulk access and permission to publish an individual record are separate matters.

What it is

DECIPHER is a web resource for exploring genetic variation alongside the features recorded for the people carrying those variants. The useful research object is the link between a genomic finding and a phenotype, rather than a DNA coordinate on its own. Its family information leaflet illustrates how a record brings together variant location, inheritance when known, and recorded features.

The database includes both copy-number and sequence variation. The resource team’s paper in Nucleic Acids Research describes its expansion from a copy-number database to one supporting sequence variants, including single-nucleotide variants and small insertions or deletions. That history matters when reading older descriptions that emphasize chromosomal imbalance: they describe part of the resource’s development rather than its entire scope.

For a research project, the distinction is practical. A gene, an interval, a phenotype term and an individual variant are different starting points. DECIPHER brings these perspectives together, but a matching record remains a contributed observation with its own provenance. The database is a place to investigate connections and identify potential collaboration, rather than a substitute for examining the underlying evidence.

Who runs it and what it covers

DECIPHER is hosted by EMBL’s European Bioinformatics Institute, EMBL-EBI. The Wellcome Sanger Institute states that the database and team moved there in July 2023. Older Sanger web addresses and papers therefore reflect a real institutional history, while the current platform is at deciphergenomics.org.

The official ethical framework identifies Cambridge University Hospitals NHS Foundation Trust as the study sponsor and Cambridge South Research Ethics Committee as responsible for continued study oversight. Hosting, sponsorship and ethics oversight are separate roles; a research record should distinguish them when documenting the resource.

The ethical framework traces the project’s original research ethics approval to 2004 and records a favourable opinion on the amendment supporting its transition to EMBL-EBI. This provides a documented institutional history for a research methods section without relying on an old hosting address as evidence of present responsibility.

Contributing projects retain control over their own patient data and its sharing. The Sanger resource description explains that information can remain within a project, be shared with selected collaborators, or become publicly viewable with consent. Consequently, a public search describes the material visible in that access context. It does not establish what every participating centre holds.

The family leaflet describes DECIPHER’s intended professional users as clinical geneticists, genetic scientists and molecular biologists. Its example also distinguishes the scientific description from direct identifiers: names and dates of birth are not displayed. Restricted photographs are a separate category. These distinctions help explain why a visible phenotype entry does not imply that every associated item is public.

How to search or use it

Start with the public website’s search box. Its search examples include genes, phenotypes, HPO identifiers, genomic intervals and exact variants. For a reproducible research search, record the expression you entered and the reference assembly alongside the date.

DECIPHER’s official Searching DECIPHER guide, dated June 2020, documents the following workflow and interface labels:

  1. Enter a starting term. Use the search box to type a gene name or phenotype.
  2. Select the intended suggestion. Suggested terms do not necessarily have associated patient records.
  3. Choose Search. Review the results matching the selected term.
  4. Open a DECIPHER Patient ID. The identifier links to the corresponding record.
  5. Use Refine Search. Add or remove terms, such as another phenotype or gene.
  6. Inspect the results table. The guide describes a variant-type dropdown and sortable columns.
  7. Select Browser. The documented view places results in a genome browser or, for results spread across the genome, a karyotype view.

The dated guide also distinguishes an all-numeric DECIPHER patient identifier from a project-internal reference prefixed with ref:. Internal references belong to the authenticated project context. Do not assume that an identifier from another system has the same meaning here.

Keep the reference assembly in the query

The current search examples distinguish an interval entered as GRCh38 from an interval explicitly prefixed with grch37:. They also distinguish exact-variant expressions from broader searches: exact variants cannot be combined with other terms. Keep that distinction when planning a search; a gene-plus-phenotype query and an exact-variant query are different operations.

Public, managed and private data

DECIPHER’s September 2020 data-flow diagram separates three sharing contexts. A private departmental domain holds records within the submitting centre. Managed sharing makes information visible to specified centres. Consented public sharing makes linked genomic and phenotype information visible through genome browsers.

The diagram describes phenotype capture using Human Phenotype Ontology terms. Those terms provide the feature descriptions associated with genomic findings; they are not themselves patient identifiers. A phenotype search and a record-ID search therefore ask different questions even when they eventually lead to the same record.

This architecture has an important consequence for research reporting: the scope of your search includes its access context. A statement such as “no public matches were returned” is narrower than “DECIPHER contains no matching records.” The former describes an observation; the latter would require knowledge of holdings beyond the public view. Keep the narrower statement when that is what the search supports.

Consent also remains connected to how information is shared. The family leaflet describes further contact through the responsible clinician when additional information or publication is being considered. For broader background on this distinction, see CASRAI’s definition of informed consent.

Bulk access and publication permissions

The EMBL-EBI DECIPHER General Terms of Use, revised 22 July 2026, prohibit copying patient data from the website. They direct bulk access through DECIPHER under a Data Access Agreement or Data Display Agreement and prohibit attempts to compromise patient anonymity or privacy. Public browsing is therefore not permission to assemble a downloadable patient dataset.

The same distinction applies to third-party displays. UCSC’s DECIPHER track documentation permits browser display while directing bulk-data requests back to DECIPHER. Viewing a track in another genome browser does not create a separate route around the originating resource’s restrictions.

The terms also place responsibility on people uploading content to hold the necessary authorizations, permissions and consents. They explain that community contributors remain the data owners and that hosting does not imply endorsement. For a collaborative project, access management and contribution management therefore deserve separate attention: permission to examine a resource does not establish permission to upload someone else’s material to it.

DECIPHER’s published citation instructions require explicit publication permission from the contributing centre when an individual is specifically referenced, including a pseudonymous or anonymous individual. They also require appropriate recognition, acknowledgment of DECIPHER, the requested resource citation, and a statement separating the original contributors from responsibility for subsequent interpretation. A bibliographic citation alone does not complete these requirements.

For project planning, separate the proposed activity into browsing, bulk analysis, external display and individual-level publication. The task/access dataset below brings together the corresponding official rules; it contains no patient data. CASRAI’s Data Use Agreement definition explains the general role of an agreement, while DECIPHER’s own terms govern this resource.

Strengths and limits

DECIPHER’s strength is the connection between genomic findings, recorded phenotypes and contributing projects. Its research value comes from being able to examine related observations in their genomic context and identify where a follow-up collaboration may be useful. The resource team’s paper describes integrated graphical and tabular views rather than a collection of isolated variant names.

Its own disclaimers identify several limits relevant to data interpretation. Depositing centres make assertions about variants in individual cases; those assertions are not made by the DECIPHER administrators. The collection spans changing methods over many years. Breakpoints for large structural variants can be approximate, with precision depending on the technology used to identify them.

DECIPHER also displays information obtained from other resources. Its disclaimers explain that these copies may not be current or complete. For a research evidence trail, distinguish what the submitting centre asserted from what an integrated external annotation reports. Preserve the source and date for each, rather than treating everything on a composite page as one independently confirmed conclusion.

These are data-provenance questions: where an assertion came from, which representation was examined, and what the observation actually supports. Recording those details makes a search more useful to colleagues who need to review the same evidence later.

Illustrative example: a researcher preparing a review of phenotype-linked variation starts with a gene symbol, then considers adding a phenotype. This example is a search-planning exercise, not a report of an actual patient or database result.

The notebook can preserve four separate items: the initial gene query; the additional phenotype expression; the reference assembly for any interval search; and whether the search used public or project access. If the task changes to an exact variant, record that as a separate search because the platform’s examples exclude combining exact-variant expressions with other terms.

Next, separate the observation from the planned use. Locating relevant information answers a discovery question. Downloading it in bulk or featuring an individual in a publication raises a permission question. This separation prevents a useful exploratory match from silently becoming an unsupported claim about either the whole database or the rights attached to its contents.

Alternatives and complementary resources

The following resources address different research tasks. They complement DECIPHER rather than providing interchangeable versions of its patient-linked records. Their own documentation defines the distinctions in the table.

Resource Documented focus Relationship to a DECIPHER search
Human Phenotype Ontology An ontology describing human clinical features, available in OBO and OWL formats. Provides phenotype vocabulary rather than an individual variant/phenotype record.
gnomAD Aggregation and harmonization of exome and genome sequencing, with summary data for researchers. Addresses aggregate variation rather than DECIPHER’s linked patient records.
UCSC Genome Browser DECIPHER tracks Genomic display of DECIPHER CNVs and SNVs with associated phenotype information. An alternative display context for DECIPHER information, with links back to the originating records.

Choose the resource according to the object needed for the research question: a vocabulary term, aggregate sequence variation, or a genomic display of linked observations. Keep the distinction visible in a methods description so that readers understand what was searched and what kind of evidence was obtained.

Sources

Data: DECIPHER research tasks and access routes

Original compilation distinguishing discovery, bulk analysis, external display and individual-record publication, synthesized from DECIPHER search and citation information, its July 2026 terms, and UCSC track documentation. It describes resource policies and contains no patient data.

DECIPHER research tasks and access routes
Research taskDocumented route or conditionSource
Browse public recordsPublic browsing does not require a login.DECIPHER website
Obtain bulk patient dataRequest access from DECIPHER under a Data Access Agreement or Data Display Agreement; do not copy patient data from the website.DECIPHER General Terms of Use, July 2026
View DECIPHER tracks at UCSCBrowser display is available; bulk download rights are not supplied through the track.UCSC DECIPHER track documentation
Reference an individual in a publicationObtain explicit publication permission from the contributing centre, including for an anonymous or pseudonymous individual.DECIPHER citation instructions

Sources

Compiled by CASRAI from the sources above. Free to reuse under CC BY 4.0 with attribution.

Follow CASRAI

Research-administration guidance, standards updates and independent tool reviews.

Ask CASRAI · full access

Ask about DECIPHER Database: Search, Scope and Data Access

Full access: large monthly usage, up to 10 source passages behind each answer, and MCP and API access for Claude Code, Codex and other CLIs. Cancel any time.

An AI assistant for research: funder rules, compliance, methods and publishing. It links the sources behind its answers and labels answers that come from a web search.

Answers draw on CASRAI's guides and dictionary plus the federal and funder documents we index: Federal Register, Grants.gov, Regulations.gov and UKRI.

Works on this site and inside Claude, Cursor and the AI tools you already use.

Everything CASRAI publishes — this page, the dictionary, the guides and the news — stays open to read, with no account and no card.

Referenced across the research world

University of Cambridge logoColumbia University logoCrossref logoUniversity of Edinburgh logoHarvard University logoUniversity of Oxford logoPrinceton University logoStanford School of Medicine logoUniversity College London logoORCID logoUniversity of Cambridge logoColumbia University logoCrossref logoUniversity of Edinburgh logoHarvard University logoUniversity of Oxford logoPrinceton University logoStanford School of Medicine logoUniversity College London logoORCID logo
  • University of Cambridge logo
  • Columbia University logo
  • Crossref logo
  • University of Edinburgh logo
  • Harvard University logo
  • University of Oxford logo
  • Princeton University logo
  • Stanford School of Medicine logo
  • University College London logo
  • ORCID logo

View CASRAI adoption →