A comparison of Fast Healthcare Interoperability Resources and Observational Medical Mutcomes Partnership electronic health record data within the All of Us Research Program.
other
Where this comes from
- Record sourced from PubMed, PMID 42334204.
- Also identified by DOI 10.1093/jamia/ocag095.
- No licence information is recorded for this record.
- Because redistribution is not established, this page shows the abstract only. Follow the links below for the full text.
Abstract
This study compares the contents of two data standards; the Observational Medical Outcomes Partnership (OMOP) and Fast Healthcare Interoperability Resources (FHIR), highlighting their strength and weaknesses and serve as an initial step toward understanding how each standard supports secondary data analysis. Participant electronic health record data in both OMOP and FHIR formats from the All of Us Research Program (AoURP) were compared, including codeable event volume, healthcare encounters, and person timelines. A phenotype-based assessment was also conducted using Type-II Diabetes Mellitus (T2DM). Among 29 512 participants identified with overlapping FHIR and OMOP data, Median codeable event counts were comparable between FHIR and OMOP within the Measurement (OMOP = 846; FHIR = 832), Drug (OMOP = 92; FHIR = 90), and Observation (OMOP = 65; FHIR = 100) domains, but were higher in OMOP within the Condition (OMOP = 258; FHIR = 11) and Procedure (OMOP = 72; FHIR = 4) domains. Within the T2DM cohort, OMOP contained more data, except for medications. Very few participants had encounters in FHIR (1.5%) relative to OMOP (97.0%). On average, only 15.9% of visit dates overlapped in both standards, with most visit dates occurring only in OMOP (65.3%) or only FHIR (18.4%). Data in OMOP showed a higher volume of observation and procedure codeable events, reported encounters, and T2DM symptoms, complications, and comorbidities. FHIR data was able to capture data across multiple providers and health systems. Based on AoURP data, both standards were shown to support healthcare data capture, although OMOP shows greater utility for research purposes as its extract, transform, and load process enables more flexible data capture relative to extracting data from FHIR payloads. FHIR, however, captures patient-level data from beyond the health system and can thus be used to supplement OMOP.