Folklore

Reference Databases

Folklore integrates 45 reference databases and curated sources across variant annotation, classification, phenotype matching, screening, inheritance analysis, mitochondrial analysis, and SV/CNV interpretation. These external and curated sources are materialized into internal reference tables and derived views. Production reference data is stored locally on EU-based infrastructure in Helsinki, Finland.

Reference versions are pinned per deployment and recorded through the reference-data manifest. The table below lists selected core sources used by the nuclear germline workflow; it is not the complete inventory of all 45 integrations or of every internal reference table and derived view.

How the database counts are defined

The core Stage 4 enrichment currently loads 16 production classification and reference databases. The platform-wide figure of 45 counts all reference databases and curated sources used across nuclear classification, phenotype, inheritance, screening, mitochondrial, and SV/CNV modules. Smaller numbers in a subsystem, selected-source table, or historical changelog describe that narrower set; they are not alternative totals for the current platform.

Zero External API Calls

Core genomic processing uses locally stored reference data and a local Ensembl VEP cache. Patient variants are not submitted to public genomic databases or third-party annotation APIs during the analysis path.

Database Summary

DatabasePrimary UseACMG Criteria
gnomADPopulation frequenciesBA1, BS1, BS2, PM2
ClinVarClinical significancePS1, PP5, BP6, ClinVar override
dbNSFPFunctional predictionsPP3, BP4 (BayesDel_noAF)
SpliceAISplice impactPP3_splice, BP7 guard
gnomAD ConstraintGene-level tolerancePVS1, PP2, BP1
HPOGene-phenotype mappingPP4
ClinGenDosage sensitivityBS1, BP2
OrphanetGene-disease-inheritanceBS1 (AD/AR/XLD), PVS1 gate
VCEP SpecsGene-specific thresholdsBA1, BS1, PM2, PVS1 gate
ClinGen GDVGene-disease validityPVS1 constraint gate, disease association gate
DECIPHER G2PMolecular mechanism curationPVS1 GoF/DN guard, disease association gate
GoFCardsGain-of-function curationPVS1 GoF guard
Ensembl VEPVariant effect predictionPVS1, PM1, PM4, BP1, BP3, BP7

Annotation Pipeline

Reference data is loaded into each variant record during Stage 4 of the processing pipeline. After annotation, every variant carries all reference columns directly -- no database lookups are needed during classification or clinical review. The annotation order is:

1

gnomAD v4.1

Population allele frequencies. Positional match on chromosome, position, reference allele, and alternate allele. Loads 6 columns.

2

ClinVar

Clinical significance assertions. Same positional match. Loads 7 columns including review stars and disease associations.

3

dbNSFP 4.9c

Functional predictions from SIFT, AlphaMissense, MetaSVM, DANN, BayesDel, and conservation scores. Loads 9 columns with duplicate variant aggregation.

4

gnomAD Constraint

Gene-level tolerance metrics. Joined on gene symbol. Loads 4 columns: pLI, LOEUF, o/e LoF, and missense Z-score.

5

HPO

Gene-phenotype associations. Joined on gene symbol with deduplication and aggregation. Loads 6 columns.

6

ClinGen

Dosage sensitivity scores. Joined on gene symbol. Loads 2 columns: haploinsufficiency and triplosensitivity.

Ensembl VEP runs as a separate stage (Stage 3) before database annotation, providing consequence predictions and transcript selection that the annotation phases then build upon. SpliceAI scores are accessed from precomputed data during VEP annotation.

In This Section

For details on how these databases are combined during ACMG classification, see the Criteria Reference.