Cargando…

Transforming the Premier Perspective® Hospital Database into the Observational Medical Outcomes Partnership (OMOP) Common Data Model

BACKGROUND: The Observational Medical Outcomes Partnership (OMOP) Common Data Model (CDM) has been implemented on various claims and electronic health record (EHR) databases, but has not been applied to a hospital transactional database. This study addresses the implementation of the OMOP CDM on the...

Descripción completa

Detalles Bibliográficos
Autores principales: Makadia, Rupa, Ryan, Patrick B.
Formato: Online Artículo Texto
Lenguaje:English
Publicado: AcademyHealth 2014
Materias:
Acceso en línea:https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4371500/
https://www.ncbi.nlm.nih.gov/pubmed/25848597
http://dx.doi.org/10.13063/2327-9214.1110
_version_ 1782363054704427008
author Makadia, Rupa
Ryan, Patrick B.
author_facet Makadia, Rupa
Ryan, Patrick B.
author_sort Makadia, Rupa
collection PubMed
description BACKGROUND: The Observational Medical Outcomes Partnership (OMOP) Common Data Model (CDM) has been implemented on various claims and electronic health record (EHR) databases, but has not been applied to a hospital transactional database. This study addresses the implementation of the OMOP CDM on the U.S. Premier Hospital database. METHODS: We designed and implemented an extract, transform, load (ETL) process to convert the Premier hospital database into the OMOP CDM. Standard charge codes in Premier were mapped between the OMOP version 4.0 Vocabulary and standard charge descriptions. Visit logic was added to impute the visit dates. We tested the conversion by replicating a published study using the raw and transformed databases. The Premier hospital database was compared to a claims database, in regard to prevalence of disease. FINDINGS: The data transformed into the CDM resulted in 1% of the data being discarded due to data errors in the raw data. A total of 91.4% of Premier standard charge codes were mapped successfully to a standard vocabulary. The results of the replication study resulted in a similar distribution of patient characteristics. The comparison to the claims data yields notable similarities and differences amongst conditions represented in both databases. DISCUSSION: The transformation of the Premier database into the OMOP CDM version 4.0 adds value in conducting analyses due to successful mapping of the drugs and procedures. The addition of visit logic gives ordinality to drugs and procedures that wasn’t present prior to the transformation. 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. CONCLUSION AND NEXT STEPS: The conversion of the Premier database into the OMOP CDM 4.0 was completed successfully. The next steps include refinement of vocabularies and mappings and continual maintenance of the transformed CDM.
format Online
Article
Text
id pubmed-4371500
institution National Center for Biotechnology Information
language English
publishDate 2014
publisher AcademyHealth
record_format MEDLINE/PubMed
spelling pubmed-43715002015-04-06 Transforming the Premier Perspective® Hospital Database into the Observational Medical Outcomes Partnership (OMOP) Common Data Model Makadia, Rupa Ryan, Patrick B. EGEMS (Wash DC) Informatics BACKGROUND: The Observational Medical Outcomes Partnership (OMOP) Common Data Model (CDM) has been implemented on various claims and electronic health record (EHR) databases, but has not been applied to a hospital transactional database. This study addresses the implementation of the OMOP CDM on the U.S. Premier Hospital database. METHODS: We designed and implemented an extract, transform, load (ETL) process to convert the Premier hospital database into the OMOP CDM. Standard charge codes in Premier were mapped between the OMOP version 4.0 Vocabulary and standard charge descriptions. Visit logic was added to impute the visit dates. We tested the conversion by replicating a published study using the raw and transformed databases. The Premier hospital database was compared to a claims database, in regard to prevalence of disease. FINDINGS: The data transformed into the CDM resulted in 1% of the data being discarded due to data errors in the raw data. A total of 91.4% of Premier standard charge codes were mapped successfully to a standard vocabulary. The results of the replication study resulted in a similar distribution of patient characteristics. The comparison to the claims data yields notable similarities and differences amongst conditions represented in both databases. DISCUSSION: The transformation of the Premier database into the OMOP CDM version 4.0 adds value in conducting analyses due to successful mapping of the drugs and procedures. The addition of visit logic gives ordinality to drugs and procedures that wasn’t present prior to the transformation. 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. CONCLUSION AND NEXT STEPS: The conversion of the Premier database into the OMOP CDM 4.0 was completed successfully. The next steps include refinement of vocabularies and mappings and continual maintenance of the transformed CDM. AcademyHealth 2014-11-11 /pmc/articles/PMC4371500/ /pubmed/25848597 http://dx.doi.org/10.13063/2327-9214.1110 Text en All eGEMs publications are licensed under a Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 License http://creativecommons.org/licenses/by-nc-nd/3.0/
spellingShingle Informatics
Makadia, Rupa
Ryan, Patrick B.
Transforming the Premier Perspective® Hospital Database into the Observational Medical Outcomes Partnership (OMOP) Common Data Model
title Transforming the Premier Perspective® Hospital Database into the Observational Medical Outcomes Partnership (OMOP) Common Data Model
title_full Transforming the Premier Perspective® Hospital Database into the Observational Medical Outcomes Partnership (OMOP) Common Data Model
title_fullStr Transforming the Premier Perspective® Hospital Database into the Observational Medical Outcomes Partnership (OMOP) Common Data Model
title_full_unstemmed Transforming the Premier Perspective® Hospital Database into the Observational Medical Outcomes Partnership (OMOP) Common Data Model
title_short Transforming the Premier Perspective® Hospital Database into the Observational Medical Outcomes Partnership (OMOP) Common Data Model
title_sort transforming the premier perspective® hospital database into the observational medical outcomes partnership (omop) common data model
topic Informatics
url https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4371500/
https://www.ncbi.nlm.nih.gov/pubmed/25848597
http://dx.doi.org/10.13063/2327-9214.1110
work_keys_str_mv AT makadiarupa transformingthepremierperspectivehospitaldatabaseintotheobservationalmedicaloutcomespartnershipomopcommondatamodel
AT ryanpatrickb transformingthepremierperspectivehospitaldatabaseintotheobservationalmedicaloutcomespartnershipomopcommondatamodel