scispace - formally typeset
Open AccessJournal ArticleDOI

Incrementally Transforming Electronic Medical Records into the Observational Medical Outcomes Partnership Common Data Model: A Multidimensional Quality Assurance Approach.

TLDR
A quality assurance (QA) process and code base is developed to accompany the incremental transformation of the Department of Veterans Affairs Corporate Data Warehouse health care database into the Observational Medical Outcomes Partnership (OMOP) CDM to prevent incremental load errors.
Abstract
Background The development and adoption of health care common data models (CDMs) has addressed some of the logistical challenges of performing research on data generated from disparate health care systems by standardizing data representations and leveraging standardized terminology to express clinical information consistently. However, transforming a data system into a CDM is not a trivial task, and maintaining an operational, enterprise capable CDM that is incrementally updated within a data warehouse is challenging. Objectives To develop a quality assurance (QA) process and code base to accompany our incremental transformation of the Department of Veterans Affairs Corporate Data Warehouse health care database into the Observational Medical Outcomes Partnership (OMOP) CDM to prevent incremental load errors. Methods We designed and implemented a multistage QA) approach centered on completeness, value conformance, and relational conformance data-quality elements. For each element we describe key incremental load challenges, our extract, transform, and load (ETL) solution of data to overcome those challenges, and potential impacts of incremental load failure. Results Completeness and value conformance data-quality elements are most affected by incremental changes to the CDW, while updates to source identifiers impact relational conformance. ETL failures surrounding these elements lead to incomplete and inaccurate capture of clinical concepts as well as data fragmentation across patients, providers, and locations. Conclusion Development of robust QA processes supporting accurate transformation of OMOP and other CDMs from source data is still in evolution, and opportunities exist to extend the existing QA framework and tools used for incremental ETL QA processes.

read more

Content maybe subject to copyright    Report

Citations
More filters
Journal ArticleDOI

Common Problems, Common Data Model Solutions: Evidence Generation for Health Technology Assessment.

TL;DR: It is shown that the common data model has the potential to facilitate access to relevant data, enable multidatabase studies to enhance statistical power and transfer results across populations and settings to meet the needs of local HTA decision makers, and validate findings.
Journal ArticleDOI

EHR-Independent Predictive Decision Support Architecture Based on OMOP.

TL;DR: An EHR-independent means of integrating prediction models for deployment in clinical settings, utilizing the widely used Observational Medical Outcomes Partnership (OMOP) common data model rather than on a proprietary EHR data structure is proposed.
Posted ContentDOI

Baseline phenotype and 30-day outcomes of people tested for COVID-19: an international network cohort including >3.32 million people tested with real-time PCR and >219,000 tested positive for SARS-CoV-2 in South Korea, Spain and the United States

Asieh Golozar, +59 more
- 27 Oct 2020 - 
TL;DR: The findings highlight the importance of large scale characterization of COVID-19 international cohorts to inform planning and resource allocation including testing as countries face a second wave of SARS-CoV-2.
References
More filters
Journal ArticleDOI

Insights From Advanced Analytics At The Veterans Health Administration

TL;DR: How advanced analysis is already supporting the VHA's activities, which range from routine clinical care of individual patients--for example, monitoring medication administration and predicting risk of adverse outcomes--to evaluating a systemwide initiative to bring the principles of the patient-centered medical home to all veterans.
Journal ArticleDOI

Feasibility and utility of applications of the common data model to multiple, disparate observational health databases

TL;DR: Standardizing data structure, content, and analytics can enable an institution to apply a network-based approach to observational research across multiple, disparate observational health databases.
Journal ArticleDOI

Transforming the Premier Perspective® hospital database to the OMOP Common Data Model

TL;DR: Comparing conditions in Premier against a claims database can provide an understanding about Premier’s potential use in pharmacoepidemiology studies that are traditionally conducted via claims databases, and adds value in conducting analyses due to successful mapping of the drugs and procedures.
Related Papers (5)