Database Open Access

MIMIC-IV demo data in the OMOP Common Data Model

Michael Kallfelz Anna Tsvetkova Tom Pollard Manlik Kwong Gigi Lipori Vojtech Huser Jeffrey Osborn Sicheng Hao Andrew Williams

Published: June 21, 2021. Version: 0.9

When using this resource, please cite: (show more options)
Kallfelz, M., Tsvetkova, A., Pollard, T., Kwong, M., Lipori, G., Huser, V., Osborn, J., Hao, S., & Williams, A. (2021). MIMIC-IV demo data in the OMOP Common Data Model (version 0.9). PhysioNet.

Please include the standard citation for PhysioNet: (show more options)
Goldberger, A., Amaral, L., Glass, L., Hausdorff, J., Ivanov, P. C., Mark, R., ... & Stanley, H. E. (2000). PhysioBank, PhysioToolkit, and PhysioNet: Components of a new research resource for complex physiologic signals. Circulation [Online]. 101 (23), pp. e215–e220.


In this project, the MIMIC-IV demo database was used to create an Observational Medical Outcomes Partnership (OMOP) Common Data Model (CDM) instance. The transformation was built making use of template scripts and concept mappings from a previous project for converting MIMIC-III data to the OMOP CDM, while adjusting the logic and extending the mappings to be compliant with MIMIC-IV. The desired outcome was to establish and improve ways of transforming observational data collected in an intensive care environment to the OMOP CDM.


The Observational Medical Outcomes Partnership (OMOP) was a public-private partnership established in the US to inform the appropriate use of observational healthcare databases for studying the effects of medical products. A core output of this project was the OMOP Common Data Model (CDM) which represents healthcare data from diverse sources in a consistent and standardized way. Such models allow portability of analysis and development of tools that facilitate research [1-3].

MIMIC is an electronic health record database that is widely used around the world in research and education [4,5]. We carried out work to convert the latest version of MIMIC - MIMIC-IV - into the Observational Medical Outcomes Partnership (OMOP) model [3].

This project outlines development of a demo version of the dataset, based on a 100 patient subset of the full MIMIC-IV dataset. The following three modules of the MIMIC-IV dataset were included:

  • core: patient stay information (i.e. admissions and transfers)
  • hosp: hospital level data for patients: labs, micro, and electronic medication administration
  • icu: Event tables from the ICU, similar to those in MIMIC-III [6,7]

As a proof of concept, waveform files from the MIMIC waveform repository were processed to extract features for inclusion in the OMOP transform [8]. Measurements were linked to the respective origin waveform file.

Motivations for this project were to:

  1. Facilitate greater use of MIMIC-IV data by making it accessible in the widely-used OMOP CDM format;
  2. Enable use of OHDSI tools on the MIMIC-IV data;
  3. Provide the OHDSI, PhysioNet, and other OMOP-using research communities with a dataset that can be used for demonstrations and education; and
  4. Investigate the feasibility of converting ICU waveform and “numerics” data to standardized concepts in the OMOP CDM, so that methods can be developed to conduct research that requires both waveform features and related clinical data.

The project used the Achilles [9] data characterization tool to provide plausibility and comprehensiveness reports on the transform, as well as insights into adherence of the data to the OMOP model conventions. 


We used SQL (wrapped in Python) to convert data in MIMIC format into the OMOP CDM. Documented ETL code is available at the project repository on GitHub [10]. The OMOP model philosophy is to use standard concepts (a set of accepted target terminologies) to represent the data. For example, drug exposure data are captured using RxNorm concepts. We used OMOP vocabulary tables to map concepts. To capture source concepts, the ETL conversion uses local concepts (assigning a concept_id in the 2 billion number range; an OMOP model convention) and then creates a mapping to a respective standard target concept. Mapping tables used as part of the ETL are available in the project repository (see "custom_mapping_csv").

We used prior mappings published at the repository [11] of a prior mapping project [12] as a foundation and added many more mappings to achieve a higher coverage. For many source codes, existing OMOP concepts from standardized vocabularies such as LOINC or ICD10 were used.

Mapping for missing relationships was done in several stages. First, suggested mappings were generated computationally ("suggestions"). For concepts with no suggestions, a manual mapping was created. Second, an expert with a medical background manually reviewed all mapping for accuracy. Third, mapping was reviewed again by a larger team after execution of data quality checks.

We used several approaches to assess the quality of the conversion. We applied OHDSI data quality tools (Data Quality Dashboard, DQD) [13] and data characterization tools (Achilles) [9], both built in R. The project repository contains the JSON from the most recent Achilles and DQD run and documentation on which data quality errors remained. The majority of data quality issues identified by these tools relate to the MIMIC de-identification timeshift.

The project was carried out in fall 2020 and spring 2021 with updates to ETL made by OHDSI community researchers building on prior work on the ETL for MIMIC-III to OMOP. Meeting minutes of OHDSI interest group that worked on the project in 2020 are available at the Wiki page of the repository [10]. SQL ETL code is optimized to be executed in Google BigQuery.

Ongoing maintenance of the mapping and ETL is expected to be carried out by OHDSI researchers making pull requests to the GitHub repository. The code is made public primarily to enable such community collaboration. Updates may consist of improvements of the ETL, improvement to the concept mapping, responses to updates and changes in MIMIC data releases or changes to the OMOP Common Data Model (CDM). A readme file in the repository contains a point of contact who will review ETL additions submitted by the community via pull requests. 

Data Description

Data is organized into folders. The dataset is limited only to patients included in the demo subset (100 patients).

  • 1_omop_data_csv: Contains a set of CSV files, one for each OMOP table. First row of each file contains column headers. Columns follow the OMOP model specification. See github repository for scripts that generated files in the omop_data_csv. A detailed description of the OMOP model is available in textbook format at [3] (chapter 4). For OMOP vocabulary tables, only local concepts (>2B range) are provided. For the remaining vocabulary content, users should follow standard mechanisms for obtaining OMOP vocabulary tables. See [14], chapter 5, section 5.1.2: ‘Access to the Standardized Vocabularies’). If a file has no rows (only column headers), no MIMIC data was transformed into that specific OMOP table.
  • 2_achilles_json_data: JSON files generated by the Achilles data characterization tool [9]. The JSON files can be used in conjunction with the Achilles Web application to browse aggregate data characterizations.
  • 3_data_quality_dashboard_files: JSON files that are generated by the Data Quality Dashboard [13].

Usage Notes

CSV files can be downloaded and used directly to learn explore the OMOP CDM. The size of the demo dataset is small and data can be kept in memory. However, most OHDSI analytical packages require the data to be in a database. For the latest documentation and issues (for the demo or full dataset), please refer to the project repository on GitHub [10]. The ETL code is designed for both the demo and full datasets. The mappings in the ETL are not limited to concepts present in the demo data but cover the complete spectrum of the full (non-demo) data.


For help with implementing the MIMIC-IV OMOP CDM or to discuss use cases with the community, users can create a forum posting at [15] . If ETL logic errors or incorrect custom mappings are found, issues can be raised through the project’s GitHub repository [10]. Users are encouraged to contribute code improvements and concept mappings via pull requests. To request elevated privileges on the project repository, please raise an issue.

Tools and resources

One of the benefits of transforming MIMIC to the OMOP CDM is that the data becomes accessible to the OMOP tools and resources. OMOP’s main data quality tool is the Data Quality Dashboard (see textbook [14], chapter 15 ‘Data Quality’). Numerous tools for data analysis (for data characterization, population level estimation or patient level prediction) exist (see textbook [14], chapter 8 ‘OHDSI Analytics Tools’).

Known limitations

Currently, free-text notes are not populated in the OMOP CDM and several MIMIC concepts are not adequately mapped to standard concepts. The emar and emar_detail tables from the “hosp” module have not been used for additional detail extraction. Drug exposure entries were populated from the prescriptions and pharmacy tables. The inputevents and outputevents have not yet been incorporated in the conversion.

Release Notes

Version 0.9: This release represents an initial version of the conversion. We hope to address limitations identified by the community in future versions. Users should watch the project repository [2] for updates. The project describes work on the MIMIC-IV demo (a 100 patient subset of MIMIC-IV).


This work was, in part, supported by a grant from Bill and Melinda Gates foundation. VH contribution to this work was carried out with support from National Library of Medicine (NLM), National Institutes of Health. TP was supported by the National Institute of Biomedical Imaging and Bioengineering (NIBIB) under NIH grant number R01EB030362.

Conflicts of Interest

The authors have no conflicts of interest to declare.


  1. Hripcsak G, Duke JD, Shah NH, et al. Observational Health Data Sciences and Informatics (OHDSI): Opportunities for Observational Researchers. Stud Health Technol Inform. 2015;216:574-8. PMC4815923.
  2. Overhage JM, Ryan PB, Reich CG, Hartzema AG, Stang PE. Validation of a common data model for active safety surveillance research. J Am Med Inform Assoc. 2012 Jan-Feb;19(1):54–60. Epub 2011 Oct 28
  3. Observational Medical Outcomes Partnership website: [Accessed: 21 June 2021]
  4. Johnson, A., Bulgarelli, L., Pollard, T., Horng, S., Celi, L. A., & Mark, R. (2021). MIMIC-IV (version 1.0). PhysioNet.
  5. Johnson, Alistair EW, David J. Stone, Leo A. Celi, and Tom J. Pollard. “The MIMIC Code Repository: enabling reproducibility in critical care research.” Journal of the American Medical Informatics Association (2017): ocx084.
  6. Johnson, A. E. W., Pollard, T. J., Shen, L., Lehman, L. H., Feng, M., Ghassemi, M., Moody, B., Szolovits, P., Celi, L. A., & Mark, R. G. (2016). MIMIC-III, a freely accessible critical care database. Scientific Data, 3, 160035.
  7. Johnson, A., Pollard, T., & Mark, R. (2016). MIMIC-III Clinical Database (version 1.4). PhysioNet.
  8. Moody, B., Moody, G., Villarroel, M., Clifford, G., & Silva, I. (2020). MIMIC-III Waveform Database (version 1.0). PhysioNet.
  9. OHDSI Achilles Data Characterization Tool: [Accessed: 21 June 2021]
  10. MIMIC to OMOP ETL on GitHub: [Accessed: 21 June 2021]
  11. MIMIC-III OMOP Concept Mapping: [Accessed: 21 June 2021]
  12. Nicolas Paris, Adrien Parrot. MIMIC in the OMOP Common Data Model. medRxiv 2020.08.14.20175141; doi:
  13. OHDSI Data Quality Dashboard: [Accessed: 21 June 2021]
  14. OHDSI Documentation: [Accessed: 21 June 2021]
  15. OHDSI Community Forum: [Accessed: 21 June 2021]

Parent Projects
MIMIC-IV demo data in the OMOP Common Data Model was derived from: Please cite them when using this project.

Access Policy:
Anyone can access the files, as long as they conform to the terms of the specified license.

License (for files):
Open Data Commons Open Database License v1.0

Corresponding Author
You must be logged in to view the contact information.


Total uncompressed size: 73.0 MB.

Access the files
Folder Navigation: <base>/1_omop_data_csv
Name Size Modified
Parent Directory
2b_concept.csv (download) 502.8 KB 2021-05-17
2b_concept_relationship.csv (download) 395.3 KB 2021-05-17
2b_vocabulary.csv (download) 2.1 KB 2021-05-17
attribute_definition.csv (download) 104 B 2021-05-17
care_site.csv (download) 2.8 KB 2021-05-17
cdm_source.csv (download) 449 B 2021-05-17
cohort.csv (download) 66 B 2021-05-17
cohort_attribute.csv (download) 126 B 2021-05-17
cohort_definition.csv (download) 168 B 2021-05-17
condition_era.csv (download) 265.6 KB 2021-05-17
condition_occurrence.csv (download) 2.7 MB 2021-05-17
cost.csv (download) 386 B 2021-05-17
death.csv (download) 1.0 KB 2021-05-17
device_exposure.csv (download) 603.3 KB 2021-05-17
dose_era.csv (download) 9.4 KB 2021-05-17
drug_era.csv (download) 580.0 KB 2021-05-17
drug_exposure.csv (download) 3.3 MB 2021-05-17
fact_relationship.csv (download) 91.6 KB 2021-05-17
location.csv (download) 107 B 2021-05-17
measurement.csv (download) 47.5 MB 2021-05-17
metadata.csv (download) 118 B 2021-05-17
note.csv (download) 212 B 2021-05-17
note_nlp.csv (download) 191 B 2021-05-17
observation.csv (download) 4.3 MB 2021-05-17
observation_period.csv (download) 6.8 KB 2021-05-17
payer_plan_period.csv (download) 368 B 2021-05-17
person.csv (download) 8.2 KB 2021-05-17
procedure_occurrence.csv (download) 2.3 MB 2021-05-17
provider.csv (download) 218 B 2021-05-17
specimen.csv (download) 25.4 KB 2021-05-17
visit_detail.csv (download) 3.6 MB 2021-05-17
visit_occurrence.csv (download) 148.0 KB 2021-05-17