Place up to three profiles side by side. Compare their architectural role, lifecycle reach, and first limitation to test. No single standard covers every layer.
Working set
Choose profiles
1 of 3 selected
01
HGVSStandard
Decision lens
Compare roles before choosing an implementation.
The useful question is not “Which standard wins?” It is “Which job must this part of the architecture perform, and what remains uncovered?”
01
Start with the job
Decide whether you need guidance, a domain payload, exchange, semantics, governance, or a reusable release.
02
Map lifecycle reach
Use the matrix to see where each profile has a direct role. A filled cell is coverage, not a quality score.
03
Test the boundary
Read what each option leaves unresolved before judging maturity or implementation fit.
Assessment
Review lifecycle coverage and practical fit.
Read left to right. Lifecycle reach comes first; a maturity label never overrides a scope mismatch.
01 · Lifecycle reach
Where each profile contributes directly
Coverage shows a recorded role at that readiness stage. It does not imply end-to-end implementation.
One biological variant can have several valid descriptions against different references or transcripts. HGVS does not encode pathogenicity, evidence strength, observed genotype, or cohort frequency, and syntax validity alone does not establish biological correctness.
03 · Detailed assessment
Check the fit and source behind the map
Use the official source, version, and limitation together. A higher maturity label does not erase a scope mismatch.
Uniform descriptions of DNA, RNA, and protein sequence variants using explicit reference sequences, coordinate systems, variant classes, and syntax.
Best fitClinical reporting, variant databases, publications, laboratory systems, and exchange workflows that must communicate sequence-level variation unambiguously.
Readiness stages
HarmonizeExchangeLearn + reuse
AI-ready contribution
Provides precise variant-language features and auditable labels, while model joins still require reference normalization, transcript policy, and separately governed clinical interpretation.
First limitation to test
One biological variant can have several valid descriptions against different references or transcripts. HGVS does not encode pathogenicity, evidence strength, observed genotype, or cohort frequency, and syntax validity alone does not establish biological correctness.
Maturity
Established
Internationally recognized, semantic-versioned nomenclature used in clinical reports, publications, and variant databases