omop-semantics
omop-semantics is a Python library for defining and managing semantic conventions on top of OMOP CDM.
It gives you a structured, versioned, portable layer for describing which OMOP concepts are valid in a given context, how they map to CDM row shapes, and what fallback concepts to use when a mapping cannot be completed. Conventions are authored in YAML, validated against schemas, and exposed as typed Python objects — not scattered across ETL code, SQL, or documentation.
Three runtime surfaces
-
Value-set runtime
Stable named concept ids for application logic:
from omop_semantics.runtime.default_valuesets import runtime -
Template/profile runtime
Compiled semantic templates and CDM profiles viaOmopSemanticEngine. -
Fallback concepts
Canonical unknown and default concepts with reason codes:
from omop_semantics.unknowns import UNKNOWN
Key properties
- Portable — no database or vocabulary graph required
- Versionable — conventions are tracked in git alongside code
- Extensible — add project-specific definitions on top of the shipped ones
- Integrates with pipelines — drives ETL logic, validation, and documentation from a single source
When to use this
Use omop-semantics if you:
- have project-specific rules about which OMOP concepts are valid,
- need consistent concept groupings across ETL and analytics,
- want semantic conventions to be explicit, testable, and versioned,
- are working in domains like oncology where OMOP alone is too permissive.
Docs
- Usage — loading paths and code patterns
- Data Model — profiles, templates, and semantic objects
- Schema & Instances — authoring assets and file organisation
- Fallback Concepts — the shipped unknown and default concepts
- Internals — package structure and load-time behaviour
1 maintainer
Metadata
1 maintainer
Release files for omop-semantics 0.6.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| omop_semantics-0.6.2.tar.gz | 202.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| omop_semantics-0.6.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 269.0 kB
Release files / omop_semantics-0.6.2.tar.gz
| Download URL | omop_semantics-0.6.2.tar.gz |
|---|---|
| Size | 202.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ba01bf589cbd7c68163390c07dfefd960780251635773d80a5a9f8243b2be8f5
|
|
BLAKE2b-256 checksum How to use checksums |
c4c889354f4c627a54490aa8d68175665f9f860c65be424e1efdffd16776adc5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 7, 2026.
Transparency logRelease files / omop_semantics-0.6.2-py3-none-any.whl
| Download URL | omop_semantics-0.6.2-py3-none-any.whl |
|---|---|
| Size | 66.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1a9ac1dd8ae2f31c8ee150b8fb9e644ee21d287b071e1d11b4258f6954bd91bb
|
|
BLAKE2b-256 checksum How to use checksums |
0aa39b71a40c0a269dffb6188f38cc908e13e2d6290f92201587d45b2bafaf8b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 7, 2026.
Transparency log
