OMOP CDM
- Stage boundary
- No direct role is recorded for Plan, Acquire, Exchange.
- Known limitation
- ETL is expensive, source nuance can be compressed, and vocabulary maintenance is an ongoing operational dependency.
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
OMOP CDMData 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 |
|---|---|---|---|---|---|
| OMOP CDMData model / schema | OMOP Common Data Model has no direct role recorded in Plan. | OMOP Common Data Model has no direct role recorded in Acquire. | OMOP Common Data Model has a direct role in Harmonize. | OMOP Common Data Model has no direct role recorded in Exchange. | OMOP Common Data Model 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 | OMOP CDMOMOP Common Data Model |
|---|---|
| Purpose & coverage | Relational structure, conventions, and standardized vocabularies for longitudinal observational health data. Best fitMulti-source cohort analytics, patient-level prediction, characterization, and network studies after ETL. |
| Readiness stages | HarmonizeLearn + reuse |
| AI-ready contribution | A consistent longitudinal feature surface is valuable for ML, but label design, missingness, site shift, and temporal leakage remain local responsibilities. |
| First limitation to test | ETL is expensive, source nuance can be compressed, and vocabulary maintenance is an ongoing operational dependency. |
| Evidence | E1 + E2 High confidence Formal statusCurrent CDM 5.4 ReviewSource-checked |
| Maturity | Established Broad network research use |
| Sources & links | OHDSI OMOP CDM documentation (opens in a new tab)Read full profile |