Standardizing registry data to the OMOP Common Data Model: experience from three pulmonary hypertension databases

Abstract

Background The Observational Medical Outcomes Partnership (OMOP) Common Data Model (CDM) can be used to transform observational health data to a common format. CDM transformation allows for analysis across disparate databases for the generation of new, real-word evidence, which is especially important in rare disease where data are limited. Pulmonary hypertension (PH) is a progressive, life-threatening disease, with rare subgroups such as pulmonary arterial hypertension (PAH), for which generating real-world evidence is challenging. Our objective is to document the process and outcomes of transforming registry data in PH to the OMOP CDM, and highlight challenges and our potential solutions. Methods Three observational studies were transformed from the Clinical Data Interchange Standards Consortium study data tabulation model (SDTM) to OMOP CDM format. OPUS was a prospective, multi-centre registry (2014–2020) and OrPHeUS was a retrospective, multi-centre chart review (2013–2017); both enrolled patients newly treated with macitentan in the US. EXPOSURE is a prospective, multi-centre cohort study (2017–ongoing) of patients newly treated with selexipag or any PAH-specific therapy in Europe and Canada. OMOP CDM version 5.3.1 with recent OMOP CDM vocabulary was used. Imputation rules were defined and applied for missing dates to avoid exclusion of data. Custom target concepts were introduced when existing concepts did not provide sufficient granularity. Results Of the 6622 patients in the three registry studies, records were mapped for 6457. Custom target concepts were introduced for PAH subgroups (by combining SNOMED concepts or creating custom concepts) and World Health Organization functional class. Per the OMOP CDM convention, records about the absence of an event, or the lack of information, were not mapped. Excluding these non-event records, 4% (OPUS), 2% (OrPHeUS) and 1% (EXPOSURE) of records were not mapped. Conclusions SDTM data from three registries were transformed to the OMOP CDM with limited exclusion of data and deviation from the SDTM database content. Future researchers can apply our strategy and methods in different disease areas, with tailoring as necessary. Mapping registry data to the OMOP CDM facilitates more efficient collaborations between researchers and establishment of federated data networks, which is an unmet need in rare diseases.

Transforming Estonian health data to the Observational Medical Outcomes Partnership (OMOP) Common Data Model: lessons learned

“…Previous studies have shown that one of the main difficulties during the transformation process is finding the relevant concepts [6,16,17,21,23]. This is also in line with our experience.…”

Blueprint for harmonising unstandardised disease registries to allow federated data analysis: prepare for the future

“…Other studies have used large administrative claims databases [ 33 , 34 ] or electronic medical records databases [ 35 , 36 ]. A recent study described the technicalities of harmonising standardised disease registries [ 37 ]. Our study is the first that used the OHDSI/OMOP CDM to harmonise nonstandardised national disease registries.…”

Suffering in Silence. Population-Level Detection and Risk-Prediction of Women’s Reproductive Disease from Claims Data

“…For our model engineering and evaluation we followed the research network called Observational Health Data Sciences and Informatics (OHDSI). Our dataset was mapped into the Observational Medical Outcomes Partnership Common Data Model (OMOP CDM) schema and the whole analysis was performed on this standardized database (17).…”