In Vocab workgroup meeting at OHDSI EU 2022 right now. Per @mik 's suggestion, I’m posting a forum thread to initiate a discussion about how to handle SNOMED and what may be possible in the future.
Currently (@Dymshyts @Christian_Reich , correct me if i got it wrong), we ingest SNOMED-US, SNOMED-UK ,and SNOMED-International, and then we create one composite SNOMED version based on the de-duplicated union of those concepts. Since each of those 3 vocabularies have their own release cadence, this results in a challenge of when to create the SNOMED composite for use in OHDSI vocabulary. This challenge limits the number of SNOMED releases and also can produce apparent inconsistencies between versions.
A question raised during the workgroup discussion: could we treat the 3 vocabularies are separate vocabs, rather than create a composite? or could we decide to focus only on one SNOMED vocab (international?) to be our primary standard? or some other ideas of how to maintain SNOMED (and its associated source code vocabulary mapping) to minimize the delay new versions cause to the OHDSI integrated release?
Perhaps we could get perspectives from our friends at SNOMED to establish recommended best practice.