If I had to guess, I’m sure all US EHR data holders have encountered this resistance from within their organization at some point in time. @cukarthik and friends at Columbia have been using OMOP for a long time. He might be able to provide more insight.
Education, education and then more education The power and beauty of OMOP is in the standardized data model and the terminology harmonization. The one and only one standard concept_id to represent an idea, the hierarchies, the classification concepts, domains to identify the table where the data lives, and the ability to represent your source data ‘as is’ with a 2 billionaire source concept_id make the OMOP CDM amazing!
*The ability to collaborate with like minded people all over the world is implied
I haven’t delved into Conditions, but I have started an educational series for Drugs. Similar to ICD10CM codes, folks love the NDC codes, but they aren’t standard! The series includes the OMOP basics of mapping source codes to concept_ids, CDM layout, OMOP Vocabulary tables, etc.; a library of SQL queries including how to obtain all drugs with a specified ingredient or all drugs under an ATC classification concept; a video on how to use Athena to identify drugs, ingredients or classifications of interest; a deep dive on our source data and how it fits into the CDM; future plans include Atlas, DQD, and other OHDSI tools. And it is all catered to our local users. Colorado is still in the implementation phase of this learning initiative, so the results aren’t final. RxNorm and Drugs have been well received. Say goodby to the huge time waste of string text searches on multiple source data tables!
Thank you for not adding more topics, @samart3! The EHR WG does have meetings without an agenda, so folks can bring any idea/concerns/questions to the WG for discussion. And the forums are the best place to discuss topics that involve more than EHR specific data.