76 Lessons learned during implementation of OMOP common data model across multiple health systems

Abstract

OBJECTIVES/GOALS: Adoption of the Observational Medical Outcomes Partnership (OMOP) common data model promises to transform large-scale observational health research. However, there are diverse challenges for operationalizing OMOP in terms of interoperability and technical skills among coordinating centers throughout the US. METHODS/STUDY POPULATION: A team from the Critical Path Institute (C-Path) collaborated with the informatics team members at Johns Hopkins to provide technical support to participating sites as part of the Extract, Transform, and Load (ETL) process linking existing concepts to OMOP concepts. Health systems met regularly via teleconference to review challenges and progress in ETL process. Sites were responsible for performing the local ETL process with assistance and securely provisioning de-identified data as part of the CURE ID program. RESULTS/ANTICIPATED RESULTS: More than twenty health systems participated in the CURE ID effort.Laboratory measures, basic demographics, disease diagnoses and problem list were more easily mapped to OMOP concepts by CURE ID partner institutions. Outcomes, social determinants of health, medical devices, and specific treatments were less easily characterized as part of the project. Concepts within the medical record presented very different technical challenges in terms of representation. There is a lack of standardization in OMOP implementation even among centers using the same electronic medical health record. Readiness to adopt OMOP varied across the institutions who participated. Health systems achieved variable level of coverage using OMOP medical concepts as part of the initiative. DISCUSSION/SIGNIFICANCE: Adoption of OMOP involves local stakeholder knowledge and implementation. Variable complexity of health concepts contributed to variable coverage. Documentation and support require extensive time and effort. Open-source software can be technically challenging. Interoperability of secure data systems presents unique problems.