Data Readiness
Knowledge BaseLife-sciences R&D
93 profiles ·
practical standards guide

Decision support

Compare standards by the job they do

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

PhenopacketsData model / schema

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?”

  1. Start with the job

    Decide whether you need guidance, a domain payload, exchange, semantics, governance, or a reusable release.

  2. Map lifecycle reach

    Use the matrix to see where each profile has a direct role. A filled cell is coverage, not a quality score.

  3. 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.

Readiness-stage coverage for GA4GH Phenopackets
ProfilePlanAcquireHarmonizeExchangeLearn + reuse
PhenopacketsData model / schemaGA4GH 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.

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.

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.

Detailed comparison of GA4GH Phenopackets
AssessmentPhenopacketsGA4GH 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 contributionProvides computable phenotype features and temporal context, while cohort construction, missingness, bias, and leakage controls remain external.
First limitation to testFlexible optionality and ontology dependence require application-specific validation; it does not replace an EHR API, consent layer, or cohort warehouse.
Maturity

Scaling

Current standard with named implementations

Sources & linksGA4GH Phenopackets (opens in a new tab)Read full profile