HL7®, FHIR® and the flame Design mark are the registered trademarks of Health Level Seven International and are used with per mission. November 20-22, Amsterdam | @HL7 @FirelyTeam | #fhirdevdays | www.devdays.com Mapping FHIR to OMOP CDM SeyedSohrab Hejazi
11
Embed
Mapping FHIR to OMOP CDM - FHIR DevDays · Sohrab Hejazi, Azadeh Nassirian Technical University of Dresden Institute of Medical Informatics and Biometry . Created Date: 12/6/2019
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
HL7®, FHIR® and the flame Design mark are the registered trademarks of Health Level Seven International and are used with per mission.
November 20-22, Amsterdam | @HL7 @FirelyTeam | #fhirdevdays | www.devdays.com
Mapping FHIR to OMOP CDM
SeyedSohrab Hejazi
Using FHIR as an Intermediate Platform
FHIR Clinical
Datawarehouse
transMART
OMOP
cBioPortal
XNAT
i2b2
OMOP Common Data Model
• The Observational Medical Outcomes Partnership (OMOP) Common Data Model (CDM) allows for the systematic analysis of disparate observational databases.
• Bringing data into a common format (data model) as well as a common terminologies (vocabulary).
• Once a database has been converted to the OMOP CDM, evidence can be generated using standardized analytics tools.
• Mandatory fields in OMOP vs. optional items in FHIR.
• Mandatory element in OMOP but there is no relevant value in FHIR.
• Different code for the unit
• "U/L": in FHIR enzyme unit per liter but the appropriate element in OMOP is [U]/L as unit per liter.
• Using an extension to insert data in FHIR
• for example secondary diagnoses in Condition resource.
• Using fact_relationship table in OMOP to show the relationship between primary and secondary diagnoses.
Open Issues
• Constraints due to German source data
• The reason of admission can not be documented in FHIR (only with extension is possible).
• The cause of admission (e.g. emergency) just partially can be documented in FHIR.
• The reason of dismission just partially can be documented in FHIR.
• German level of diagnosis surely (only with extension is possible).
• Data loss
• Name does not exist in OMOP
• Image data like DICOM, PDF etc. cannot be inserted (but meta data)
• Status in observation (there is no measurement_status in OPOP)
Deployment
• MIRACUM consortium in the Medical Informatics Initiative
• The goal is to take advantage of digitalization in medicine, to link data and generate medical knowledge, and to develop and apply innovative IT solutions for a better, data-based healthcare delivery system.
• Sharing of data accross ten university hospitals for medical research
• FHIR to OMOP essential component in the Data Integration Center (DIC)