DUO
- Stage boundary
- 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.
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
DUOOntology / data model
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 |
|---|---|---|---|---|---|
| DUOOntology / data model | GA4GH Data Use Ontology has a direct role in Plan. | GA4GH Data Use Ontology has no direct role recorded in Acquire. | GA4GH Data Use Ontology has no direct role recorded in Harmonize. | GA4GH Data Use Ontology has a direct role in Exchange. | GA4GH Data Use Ontology 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 | DUOGA4GH Data Use Ontology |
|---|---|
| Purpose & coverage | 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. |
| Evidence | E1 + E2 High confidence Formal statusGA4GH maintained production product ReviewSource-checked |
| Maturity | Established Production-status product with named implementations |
| Sources & links | GA4GH Data Use Ontology (opens in a new tab)Read full profile |