2012
DOI: 10.1136/amiajnl-2011-000376
|View full text |Cite
|
Sign up to set email alerts
|

Validation of a common data model for active safety surveillance research

Abstract: There was acceptable representation of the data from 10 observational databases in the OMOP CDM using the standardized terminologies selected, and a range of analytic methods was developed and executed with sufficient performance to be useful for active safety surveillance.

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1

Citation Types

1
353
0
1

Year Published

2014
2014
2023
2023

Publication Types

Select...
8
1

Relationship

0
9

Authors

Journals

citations
Cited by 422 publications
(384 citation statements)
references
References 6 publications
1
353
0
1
Order By: Relevance
“…OHDSI's Common Data Model (18), originally developed as part of the Observational Medical Outcomes Partnership (19), is a deep information model that specifies how to encode and store clinical data at a fine-grained level, ensuring that the same query can be applied consistently to databases around the world. OHDSI has chosen data integration standards that dovetail with those of the United States government and the international community, and it also supplies tools and mapping tables for converting data from other standards.…”
mentioning
confidence: 99%
“…OHDSI's Common Data Model (18), originally developed as part of the Observational Medical Outcomes Partnership (19), is a deep information model that specifies how to encode and store clinical data at a fine-grained level, ensuring that the same query can be applied consistently to databases around the world. OHDSI has chosen data integration standards that dovetail with those of the United States government and the international community, and it also supplies tools and mapping tables for converting data from other standards.…”
mentioning
confidence: 99%
“…We should agree on a common analytic data model (such as OMOP's common data model) into which data from any EHR can be translated. 10 We must agree on definitions of conditions and outcomes, cognizant of messy EHR data and balancing sensitivity and specificity. For example, there are multiple different published definitions of "diabetes" that variably use recorded diagnoses, test -8-results, and pharmacy data that, when applied to a single EHR, produce different sets of patients.…”
Section: Getting Therementioning
confidence: 99%
“…[1][2][3][4][5][6] Within these diverse research networks, health care data collected at delivery settings such as hospitals or clinics are extracted, transformed, and loaded (ETL) from their local formats to a common structure and semantic, which is often referred to as the Common Data Model (CDM). [7][8][9] The ETL processes to transform data into a CDM are usually resource-intensive and error-prone due to numerous technical challenges. Further, because these challenges are often underestimated by germane data institutions, there tends to be under-investment in ETL.…”
Section: Introductionmentioning
confidence: 99%
“…In order to address site specific differences, data sharing networks define a CDM that delineates single data structures and values that are allowed for each variable. 8,[10][11][12][13] Data contributors are required to transform their local data into the CDM structures in accordance with the precise definitions provided by the CDM developers. In addition to organizational and regulatory requirements, there are numerous technical processes associated with creating a CDM from an existing clinical system.…”
Section: Introductionmentioning
confidence: 99%