Populate the OCL OMOP-Standard source with OMOP concepts referenced by CIEL

[filiperochalopes]

User story

As a CIEL curator, I want an OMOP-Standard source in OCL containing the OMOP Standard concepts referenced by CIEL so CIEL mappings can point to a maintained OCL representation of those standard concepts.

Use case

CIEL concepts mapped to OMOP Standard concepts should reference the OMOP-Standard source in OCL. The source should contain only the OMOP concepts currently needed by CIEL rather than importing the complete OMOP vocabulary.

Important

Scope limitation: OMOP currently contains more than 11 million concepts, with approximately 2–3 million Standard Concepts alone. Synchronizing the complete OMOP vocabulary into OCL is not considered feasible at this time due to the storage, indexing, synchronization, and maintenance costs involved. Therefore, this initiative is intentionally limited to importing only the subset of OMOP Standard concepts that are already referenced by CIEL mappings. This provides the interoperability benefits required by CIEL while keeping the source manageable. Expanding beyond this subset should be treated as a separate scalability initiative.

Requirements

• Use the existing OCL source:
  • https://app.openconceptlab.org/#/orgs/OHDSI/sources/OMOP-Standard/
• Identify all OMOP Standard concepts currently referenced by CIEL.
• Populate OMOP-Standard with only those concepts required by CIEL.
• Use Athena as the reference for the current CIEL vocabulary/mapping context:
  • https://athena.ohdsi.org/search-terms/terms?domain=Condition&vocabulary=CIEL&page=1&pageSize=15&query=
• Define the minimum OMOP attributes that should be represented in OCL.
• Review the existing omop-loinc OCL source as a reference for OMOP metadata representation (Did @jamlung-ri buid it?):
  • https://app.openconceptlab.org/#/orgs/omop/sources/omop-loinc/?q=&isTable=true&isList=false&page=2
• Avoid importing unnecessary OMOP metadata when it is not required for CIEL mapping/lookup.
• Ensure CIEL mappings can use OMOP-Standard as their external mapping source.
• Define a reproducible process to refresh the source when new OMOP concepts are referenced by CIEL.

Acceptance criteria

• OMOP-Standard contains every OMOP Standard concept currently required by CIEL mappings.
• Concepts not referenced by CIEL are not imported unless explicitly required.
• The selected OMOP attributes are documented and consistently populated.
• CIEL mappings can resolve their target codes against the populated OMOP-Standard source.
• The population/update process can be rerun when CIEL adds new OMOP mappings.

Questions to be decided @askanter @jamlung-ri

• Should OMOP-Standard remain public?
• Which attributes from the OMOP concept model are actually required in OCL?
• Should the existing omop-loinc representation be reused directly or simplified for this source?
• Which OMOP vocabularies/domains should be included initially based on the mappings currently present in CIEL?
• What should be the authoritative process for detecting new CIEL → OMOP mappings that require source updates?

More details

Context

The OMOP-Standard source has already been created under the OHDSI organization in OCL.

The objective is not to mirror the complete OMOP vocabulary. The initial scope is to populate only the OMOP Standard concepts that are actually referenced by CIEL.

There is already an OCL representation of OMOP/LOINC that can be reviewed as a model for which OMOP attributes are useful, although it may contain more metadata than this use case requires.

Joe may have additional context on the design of the existing OMOP source and should be consulted before finalizing the attribute set.

[filiperochalopes]

[ocl-automation]

Automated Triage — 2026-08-07

Dimension	Score
Complexity	4
Scope	3
Clarity	3
Dependency	2
Risk	3

Decision: decision/planning-needed
Type: type/feature
Signals: none

Complex integration requiring design decisions about data synchronization, mapping relationships, and selective import logic across multiple vocabulary systems. Moderate scope within the OCL/CIEL domain but missing implementation details like sync frequency and conflict resolution.

---

Generated by ticket-triage pipeline v3. Model: anthropic/claude-sonnet-4 (openrouter).

[filiperochalopes]

Status:

[askanter]

DId you get any feedback from @jamlung-ri regarding prior work in the are of creating sources for OMOP?

[filiperochalopes]

Nop @askanter. WOuld be nice to have a feedback @jamlung-ri https://openmrs.slack.com/archives/C0A99PV25NG/p1786113030771809

[jamlung-ri]

Linking the previous work I did for creating content in OMOP:

See this organization on Staging for content: https://app.staging.openconceptlab.org/#/orgs/OHDSI/sources/

All the files for this content load should be in this folder: https://drive.google.com/drive/folders/1ANX5YDcGwuh_LOyTR1DeMfuvnbTtf9Ak?usp=sharing