01
Where it fits and where it does not
Use these four checks before committing implementation time.
- Use it when
- Portable phenotype/genotype exchange for rare disease, cancer, registries, diagnostics, and computational analysis.
- Limits
- Flexible optionality and ontology dependence require application-specific validation; it does not replace an EHR API, consent layer, or cohort warehouse.
- Best for
- Clinical and Omics and Rare disease teams working across Harmonize → Exchange → Learn + reuse.
- Maturity
- ScalingUsable now, but adoption or tooling is still developing. Pilot the exact stack first.
02
See it in the workflow
This view shows the input, the change the standard introduces, and the resulting output.
- InputWhat starts
Clinical and Omics and Rare disease source data, metadata, and local mappings
- PhenopacketsWhat changes
Use Phenopackets as a pinned data model / schema across Harmonize → Exchange → Learn + reuse
- OutputWhat becomes possible
A handoff the next system or team can validate against the same release
03
A concrete example
A rare-disease program validates a v2 Phenopacket with pinned ontology versions, measurements, disease course, biosamples, and variant interpretations.
Why it matters: Provides computable phenotype features and temporal context, while cohort construction, missingness, bias, and leakage controls remain external.
04
What it fits with
Works with GA4GH variation standards and community ontologies, and is designed to interoperate with FHIR; it is not a longitudinal warehouse.
- Metadata vocabularyDPV
Both support Clinical and Omics work and meet around Harmonize, Exchange, Learn + reuse. Compare their roles before treating them as interchangeable.
Explore relationship - Data model / schemaGA4GH VRS
Both support Omics and Clinical work and meet around Harmonize, Exchange, Learn + reuse. Compare their roles before treating them as interchangeable.
Explore relationship - StandardHGVS
Both support Omics and Clinical work and meet around Harmonize, Exchange, Learn + reuse. Compare their roles before treating them as interchangeable.
Explore relationship - StandardBeacon
Both support Omics and Clinical and Rare disease work and meet around Exchange, Learn + reuse. Compare their roles before treating them as interchangeable.
Explore relationship
05
Implementation starter
Start with one bounded handoff. Pin, test, and review it before scaling.
Define one handoff, its accountable owner, and the decision Phenopackets must support.
Pin the exact version and companion artifacts: 2.0 · current maintained version.
Map one representative input to the required data model / schema artifacts.
Test the result against the canonical source and record every exception.
Preserve the source data, mappings, and review evidence before scaling.
06
Test the main limitation
Flexible optionality and ontology dependence require application-specific validation; it does not replace an EHR API, consent layer, or cohort warehouse.
Run one representative end-to-end pilot and record exactly where Phenopackets loses context, needs an extension, or depends on another standard.
Machine-readable output may still be unfit for analysis or ML.
Test the output for missing context, provenance, terminology alignment, time leakage, and the intended downstream decision. Provides computable phenotype features and temporal context, while cohort construction, missingness, bias, and leakage controls remain external.
07
Official resources
Specifications, diagrams, examples, and guides from the organizations that maintain them.
GA4GH Phenopackets
Official publisher or steward guidance for this data model / schema profile.
- Publisher
- GA4GH