The OMOP Common Data Model is managed by the OHDSI CDM Working Group. The formal remit of the CDM Working Group (WG) is to hear proposals for change, ratifying only those with valid use cases and data to support them. Then, once ratified, these proposals are incorporated into the next version of the CDM. In the past, this was done by the WG alone. The group would invite others from around the community to present use cases for change and suggestions for improvement. The WG would then vote on the proposals and a new CDM version would be released after a certain period of time or if enough proposals were voted in. This approach worked when the community was smaller but as it is growing rapidly the CDM WG needed to adapt the refresh cycle such that everyone has an opportunity to weigh in on the proposed changes.

Looking to make a change or addition to the OMOP CDM? Please answer the questions in the decision tree to point you in the right direction.

CDM Refresh Cycle

1. Define New Version

The image above describes the new CDM refresh cycle. It begins with defining a new version. Proposals are heard over the course of a year according to the CDM Request Process and the ratified changes are added to the roadmap until such time that there are enough updates to warrant a new version of the model.

Looking to open a proposal to change or augment the CDM? Please follow the questions in the decision tree to help you determine what you will need.

2. Sign off from Work Groups

Each member of the CDM WG is a liaison for another workgroup in the community. They are responsible for presenting the proposed changes to the CDM and collecting the feedback. This has resulted in very helpful suggestions from the EHR, Data Quality, Device, HADES, and ACHILLES groups. This outreach has proven to be very effective and should result in a very stable version.

3. Release DDLs

After all changes and suggestions are agreed upon by the community and work groups the next step is to generate the DDLs. For example, the CDM WG hosted a hackathon on August 18-19, 2021. During this time the group created an R package to automatically generate the DDLs and the code to instantiate an empty CDM instance. Changes were made to v5.3 to generate v5.4 and the repository was refactored.

4. Software Update

There will be period of time once the DDLs are ready to allow the software and methods developers to prepare for the official release of the CDM. This is meant to serve as a buffer so that once the community starts adopting the new model, the tools and methods will be ready to support it.

5. Community Support

This is the final stage of the CDM refresh cycle. Once the DDLs are ready and the software and tools supports the new version, the CDM WG will work to help the community convert their data to the new model.

CDM WG Meeting Information

The CDM working group meets the first and third Tuesday of the month. See below for links to the meetings.

Every first Tuesday of the month at 10am est Teams Meeting

Every third Tuesday of the month at 1pm est Teams Meeting

Note These were recently changed from a Skype meeting to a Microsoft Teams meeting. If you do you have access to the OHDSI Teams Tenet, please contact Clair Blacketer at .