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
DUOOntology / data model
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.
Readiness-stage coverage for GA4GH Data Use Ontology
No direct role is recorded for Acquire, Harmonize.
Known limitation
Ontology matching cannot resolve jurisdiction, contract, consent nuance, expiry, or downstream duties without authoritative policy and human governance.
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.
Standardized biomedical data-use permission terms for matching controlled-access datasets to research purposes.
Best fitConsent-aware discovery, data access review, and machine-readable permitted-use conditions in genomics and health research.
Readiness stages
PlanExchangeLearn + reuse
AI-ready contribution
Helps agents screen permitted uses, but does not establish lawful access, fairness, privacy protection, or security by itself.
First limitation to test
Ontology matching cannot resolve jurisdiction, contract, consent nuance, expiry, or downstream duties without authoritative policy and human governance.
Maturity
Established
Production-status product with named implementations