Vocabulary Versioning Support

We're introducing vocabulary versioning to support reproducible research and regulatory compliance requirements.

Why Versioning Matters

Healthcare research often requires using specific vocabulary versions to ensure:

• Reproducibility - Studies can be replicated with identical concept definitions
• Compliance - Regulatory submissions may require specific terminology versions
• Audit Trails - Track exactly which vocabulary version was used

How It Works

Specify the vocabulary version when creating your client:

# Python
client = omophub.OMOPHub(api_key = "oh_xxx", vocab_version="2025.2")

# R
client <- OMOPHubClient$new(api_key = "oh_xxx", vocab_version = "2025.2")

All subsequent queries will use that specific vocabulary version.

Available Versions

Default Behavior

If no version is specified, the API defaults to the latest available version. We recommend pinning to a specific version for production applications to avoid unexpected changes.

Migration Notes

Existing API keys and applications continue to work without changes. Versioning is opt-in and backward compatible.