Phenopackets
- Stage boundary
- No direct role is recorded for Plan, Acquire.
- Known limitation
- Flexible optionality and ontology dependence require application-specific validation; it does not replace an EHR API, consent layer, or cohort warehouse.
Decision support
Compare standards by the job they do
Place up to three profiles side by side. Focus on architectural role, evidence, and the first limitation to test—not on finding a single all-purpose standard.
Working set
Choose profiles
1 of 3 selected
PhenopacketsData model / schema
Decision lens
Compare roles before you compare maturity.
The useful question is not “Which standard wins?” It is “Which job must this part of the architecture perform, and what remains uncovered?”
- Start with the job
Decide whether you need guidance, a domain payload, exchange, semantics, governance, or a reusable release.
- Map lifecycle reach
Use the matrix to see where each profile has a direct role. A filled cell is coverage, not a quality score.
- Test the boundary
Read what each option leaves unresolved before judging maturity, confidence, or implementation fit.
Three-part assessment
See the reach, the gaps, and the evidence.
Read left to right. Lifecycle reach comes first; maturity remains an editorial roll-up, not certification.
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.
| Profile | Plan | Acquire | Harmonize | Exchange | Learn + reuse |
|---|---|---|---|---|---|
| PhenopacketsData model / schema | GA4GH Phenopackets has no direct role recorded in Plan. | GA4GH Phenopackets has no direct role recorded in Acquire. | GA4GH Phenopackets has a direct role in Harmonize. | GA4GH Phenopackets has a direct role in Exchange. | GA4GH Phenopackets has a direct role in Learn + reuse. |
Direct role recordedNo direct role recorded
02 · Boundaries
What each option does not cover
These are design boundaries, not faults. Use them to identify the companion layers your architecture still needs.
03 · Detailed assessment
Check the fit and evidence behind the map
Use the source, status, and limitation together. A higher maturity label does not erase a scope mismatch.
| Assessment | PhenopacketsGA4GH Phenopackets |
|---|---|
| Purpose & coverage | Human- and machine-readable case-level phenotypic, clinical, diagnosis, measurement, biosample, and genomic interpretation data. Best fitPortable phenotype/genotype exchange for rare disease, cancer, registries, diagnostics, and computational analysis. |
| Readiness stages | HarmonizeExchangeLearn + reuse |
| AI-ready contribution | Provides computable phenotype features and temporal context, while cohort construction, missingness, bias, and leakage controls remain external. |
| First limitation to test | Flexible optionality and ontology dependence require application-specific validation; it does not replace an EHR API, consent layer, or cohort warehouse. |
| Evidence | E1 + E2 High confidence Formal statusGA4GH current maintained v2.0 ReviewSource-checked |
| Maturity | Scaling Current standard with named implementations |
| Sources & links | GA4GH Phenopackets (opens in a new tab)Read full profile |