How This Explorer Is Calculated
The pipeline first builds the Mega VCF by adding VEP annotations, PGx prioritization, database enrichment, case-control statistics, HWE/QC flags, splice evidence, and CNV context as INFO fields where available.
This explorer is generated from the enriched and prioritized tables because those contain researcher-readable columns. In the browser, repeated patient-level rows with the same CHROM/POS/REF/ALT allele are compacted into expandable variant stacks. SNV/indel rows are expanded from MegaVCF genotypes so carrier patients remain visible. CNV rows are added from the consensus CNV interval table and include sample, class, interval, and length when available. Known status is assigned when an allele-aware source contributes evidence, such as dbSNP, remote Ensembl colocated variant evidence, PharmGKB variant-level evidence, PharmVar, ClinVar, gnomAD, or LOVD. For CNVs, PGx gene-drug evidence from PharmGKB, CPIC, and DPWG also marks the CNV as known.
Gene-level sources such as CPIC, DPWG, Reactome, DrugBank, OMIM, ClinGen, and ClinPGx are shown as interpretation context. For SNVs/indels they are context unless an allele-level source is also present; for CNVs, PGx gene-drug evidence is treated as known CNV context.