MetabDB Guide

Entities, evidence, fields and website use.

1. Entities in MetabDB

MetabDB organizes source data into five main entity groups.

EntityMeaningExample
Variants / genomic contextsVariants, representative variants, genomic position groups and genetic evidence sets.rs560887
GenesGene identities linked to genetic or gene-level evidence.GCK
Protein targetsProtein targets represented in molecular QTL evidence.APOA5 protein
Metabolic measuresSource-defined compounds, lipids, lipoprotein measures, ratios and derived measurements.Glucose, GlycA
Diseases / GWAS traitsDiseases, clinical outcomes and other genome-wide association study (GWAS) traits.Type 2 diabetes, BMI

These entity groups provide the common structure used for search and navigation, while original source labels and definitions remain available in the underlying records.

3. Association evidence

Association evidence describes observed relationships between a metabolic measure and a clinical outcome or trait.

Endpoint contextTypical effectMeaning
IncidentHR; sometimes RR or ORNew-onset disease.
PrevalentOR; other effects as reportedExisting disease.
MortalityHR or RRDeath or cause-specific mortality.
Other / source-specificHR, OR, RR, beta or P-onlyOther source-defined clinical or analytical contexts.

HR, OR, RR, beta and P-only results remain separate. Estimates retain their model, endpoint and exposure scale and are not automatically pooled.

A disease page can contain several source endpoint definitions. Incident, prevalent and mortality contexts are not assigned to purely genetic evidence.

4. Genetic evidence

Evidence layerWhat it showsMain entities
GWAS / metQTLVariant association with a metabolic measure; metQTL means metabolic quantitative trait locus.Variant ↔ measure
Fine-mappingPosterior inclusion probability (PIP) for variants within a source-defined signal; displayed records use PIP ≥ 0.8 where documented GRCh38 coordinates are available.Variant / evidence set ↔ measure
Rare variant / burdenGene-level association from rare variants or aggregate tests.Gene ↔ measure
ColocalisationSupport for a shared genetic signal; curated PP.H4 (posterior probability of hypothesis H4) records are displayed at ≥ 0.8.Measure ↔ disease / trait / molecular QTL target
MR / cis-MRMendelian randomisation (MR) results using source methods and instruments; cis-MR is labelled separately.Measure ↔ disease / trait

Metabolic measure–disease relationships

Evidence classEvidence typeEndpoint / direction
AssociationDirect associationIncident / prevalent / mortality / other
GeneticColocalisationNo inferred direction
GeneticForward MRMetabolic measure → disease
GeneticReverse MRDisease → metabolic measure
Geneticcis-MRSource-defined direction

Forward, reverse and cis-MR remain separate. MR-A/B/C describe linked support: A, sensitivity analyses and colocalisation; B, one of these; C, neither. Analyses without linked sensitivity or colocalisation support are retained as reported and should not be interpreted as failed analyses.

5. Key fields

FieldMeaning
HRHazard ratio.
OROdds ratio.
RRRisk or rate ratio, as reported by the source.
BetaSource-reported regression coefficient.
SEStandard error.
PSource-reported P value.
FDR / qFalse discovery rate adjusted value, reported by the source or derived from a documented complete test family.
PP.H4Posterior probability of a shared genetic signal under the source colocalisation model.
PIPPosterior inclusion probability for a variant under the source fine-mapping model; credible-set membership is a separate field.
CLPPColocalisation posterior probability; in eCAVIAR, support for a variant being causal in both traits, distinct from PP.H4.
Variant / SNPVariant is the general term; SNP means single-nucleotide polymorphism when that variant class is established.
Lead variantA representative variant designated as a lead by the source analysis.
Genomic position / locusA position is a chromosome/base-pair coordinate; a locus is a source-defined genomic region with its own boundaries and model context.
NSample size for the source analysis.
EventsNumber of outcome events, when reported.
StudiesNumber of contributing MetabDB source studies.
Source recordsRetained source-level analytical rows, within the labelled scope.
Position groupsCoordinate-based genomic groups in a stated genome build.
DirectionPositive or negative source effect when the exposure orientation is known; the null is 1 for ratios and 0 for beta.

FDR and adjusted P

Source-reported FDR and BH-FDR derived from complete original P-value families are labelled separately. Displays use FDR when available, otherwise adjusted P with its correction method. A dash means neither value is available. Bonferroni-adjusted P is not FDR.

FDR-supported direction counts require q ≤ 0.05 and known exposure orientation. Nominal P alone does not establish FDR support; corrections remain specific to each evidence layer.

Statistical display

HR, OR, RR and their confidence intervals use two decimal places; beta and SE use three significant digits. PP.H4 and PIP use three decimals. P, FDR and q use three significant digits, with scientific notation below 0.001. Unrecoverable source zeros display “Below reporting limit”; a dash indicates missing information. Downloads retain source precision. Adjustment badges distinguish source-reported values, MetabDB BH and other documented methods.

Exposure scale

Measurement unit and exposure scale are separate. Equal “per SD” labels do not guarantee the same concentration increment across studies. Numerical ranges describe source values; compare effect magnitudes only within compatible models and exposure scales.

6. What counts mean

CountMeaning
EntityOne standardized entity in the named public registry; a metabolic measurement is not necessarily a unique chemical compound.
Source record / source rowOne retained source-reported analytical result after within-source deduplication.
Canonical pairOne deduplicated entity pair for a specified stored-link type.
Support blockA source/study/result-type summary supporting one canonical pair; several source rows may contribute.
Evidence cardAn interface summary of a scoped entity pair or genomic context.
Endpoint contextA source-defined clinical outcome or analytical context; several definitions can map to one disease.
StudyOne MetabDB source study; studies may share cohorts or upstream data.

These counts use different denominators and should not be added together unless explicitly stated. Evidence layers can overlap.

7. Using MetabDB

PagePurpose
SearchFind an entity and its linked evidence.
BrowseExplore standardized entities by category.
ColocalisationExplore curated shared-signal evidence.
FeaturesView disease-association profiles, case studies and gene evidence breadth.
StudiesReview source cohorts, assays, coverage and overlap.
SummaryView overall entity, relationship and study-coverage statistics.
Download & APIAccess source-level and standardized data.
HelpRead definitions, fields and interpretation guidance.

Search

Search typeExample
Metabolic measureGlucose
Disease / traitType 2 diabetes
GeneGCK
Variantrs560887

Use the search-type selector when a name is ambiguous.

Browse

  • Metabolic measures — assay, measurement type and biochemical class.
  • Diseases / traits — diseases/outcomes and other GWAS traits are separate.
  • Molecular QTL targets — gene/protein targets by QTL type.

Source collections are separate from entity counts. Assay filters can overlap; NMR (nuclear magnetic resonance) and MS (mass spectrometry) are methods, not biochemical classes.

Colocalisation

  • Metabolic measure → diseases, traits or molecular QTL targets.
  • Disease / trait → metabolic measures.
  • Molecular QTL target → metabolic measures.

Partner entities, studies, position groups and source records are counted as labelled.

Features

  • Disease-association profiles — clustering, PCA, stability and sensitivity analyses.
  • Case studies — selected source-level disease and genetic evidence.
  • Gene evidence breadth — linked measures and supporting evidence layers across genes.

Feature analyses are descriptive and exploratory; evidence layers are not combined into a single score.

Studies

  • Cohort and ancestry
  • Assay and biospecimen
  • Measurement coverage
  • Evidence contribution

Measurement and evidence overlap are reported separately from participant overlap.

8. Source definitions and mapping

Standardisation is applied to entity identities so that records can be searched and compared across studies. Original source labels, definitions and analytical results remain accessible.

How identities are standardised

  1. Start from the source record. Use its source key, study-specific code or complete original label, retaining the publication, supplementary-table or assay-documentation locator.
  2. Match to reference identifiers. Validate external identifiers against versioned reference dictionaries. New or revised mappings require a complete-label or exact-synonym match, or an explicit official equivalence with source support. Similar names and ordinary cross-references alone do not establish identity.
  3. Confirm entity type and scope. Keep diseases, other traits, genes, proteins and metabolic measurements distinct. Clinical endpoint contexts are stored separately; ambiguous candidates and conflicting definitions remain pending.
  4. Record the final mapping. Accepted existing mappings and audited revisions are recorded in the versioned entity registry, with the source identity and mapping provenance preserved.
Public stateMeaning
MappedA reliable external identity mapping has been accepted.
Source-defined validatedIdentity and entity type are supported by the original publication, supplementary material or assay documentation, without a safe external canonical mapping. Some views shorten this label to “Source-defined”.
Unresolved / pendingIdentity or type is insufficiently resolved for the public catalogue and entity counts; original records remain in provenance.

Mapped and Source-defined validated entities are both displayed and counted. Mapping status and review status are separate. Standardisation does not make source case definitions, cohorts, assays or exposure scales equivalent.

Release 1 mapping coverage

These counts reflect the current public views, with splicing QTL evidence excluded from results and statistics. Original source records are retained.

Public entity groupMappedSource-defined validatedTotal
Diseases / outcomes7712,7533,524
Other GWAS traits923,2903,382
Molecular QTL targets1,7982272,025
Metabolic measures02,6632,663

The 863 mapped disease/trait entities use MONDO, EFO or MeSH; the remaining 6,043 retain validated source identities. Mapped molecular QTL targets include 110 UniProt protein targets.

All 2,663 metabolic measures retain source-defined measurement identities. Accepted ChEBI/RefMet concept annotations do not by themselves establish a unique chemical structure, resolve isomers or justify merging measurements across platforms.

Gene and variant reference identifiers

In the broader gene-evidence collection, 6,536 gene records are linked to reference identifiers: 6,535 to HGNC and one to NCBI Gene. All 110 protein targets map to UniProt. These protein targets are already included in the molecular QTL counts above.

Of 2,553,037 variant source contexts, 2,073,433 (81.21%) have accepted rsID mappings after coordinate and allele checks against dbSNP build 154 / GRCh38. These are source contexts, not distinct variants. The unordered allele check does not establish effect-allele orientation.

Entity mapping preserves source estimates, P/FDR values, model descriptions, measurement units and exposure scales. Gene records and variant source contexts have separate denominators and are not added to public catalogue entity totals.

9. Interpretation notes

  • Association is not causality.
  • Colocalisation indicates a shared genetic signal, not mediation or causality.
  • MR remains source- and method-specific; support classes do not grade causal certainty.
  • Fine-mapping probabilities depend on the source model and priors.
  • Studies may share cohorts, assays or upstream GWAS; shared UK Biobank samples are not independent replication.
  • Equal effect labels do not guarantee comparable exposure scales.
  • Coordinate groups are not assumed to be independent loci or allele-resolved variants.