What's new in MIMIC-IV?
Many users will be familiar with MIMIC-III, the predecessor of MIMIC-IV. A number of improvements have been made, including simplifying the structure, adding new data elements, and improving the usability of previous data elements.
The structure of MIMIC-IV is necessarily different than MIMIC-III. In MIMIC-III, the set of tables were given as one large set, with no obvious differentiation between them. In MIMIC-IV, we explicitly state the source database of each table. Not only does this clarify the data provenance, but it answers many questions regarding data coverage. For example, as the CHARTEVENTS table is sourced from the ICU clinical information system, it will only provide data for patients while they are in an ICU. Conversely, the LABEVENTS table is sourced from the hospital database, and consequently contains information for a patient’s entire hospital stay.
MIMIC-IV contains data from 2008 - 2019 (inclusive). Biomarkers which have been more recently introduced will be available.
CareVue is no more
As the update covers the years 2008 - 2019, the CareVue clinical information system is no longer relevant, as it was not used during that time period. The implications are:
itemidin d_items with a value less than 220000 are no longer relevant.
- The inputevents_cv table has been removed. The inputevents_mv table was renamed inputevents. The structure is otherwise unchanged.
- The procedureevents_mv table has been renamed procedureevents.
icustay_id is now
Eventually, stays across different areas of the hospital will be indexed by a unique
stay_id, such that a stay in the emergency department, ICU, and operating room will all be distinct and referred to by the same identifier. In preparation for this change,
icustay_id has been renamed
Years are included
The date-shift strategy in MIMIC has changed. Instead of releasing the day of the week and the season, we have released the approximate year of patient admission. This allows studying patients over time as care practices change.
Audit trails are removed
MIMIC-III contained a number of rows associated with auditing clinical documentation. These rows were marked as erroneous in various ways (
error = 1,
statusdescription = ‘Rewritten’). These rows have been removed in MIMIC-IV.
Chest x-ray data
Imaging data is also an entirely new addition to MIMIC. The MIMIC-CXR database is publicly available. Notably, the
subject_id identifier used in the MIMIC-CXR database is consistent with the
subject_id used in MIMIC-IV. Therefore, all chest x-rays in MIMIC-CXR are linkable to patient stays in MIMIC-IV.
Table-wise improvements over MIMIC-III
A number of enhancements have been made to tables which may be familiar to you from MIMIC-III. Entirely new tables have also been added.
emar and emar_detail
Two entirely new tables are made available, sourced from the relatively newly installed electronic Medicine Administration Record (eMAR) system. Bedside staff will scan barcodes for each individual formulary unit of a medication when administering it. This allows for a granular, high resolution record of when a medication was given.
- Reference ranges are now available.
- A specimen identifier (
specimen_id) allows users to group all measurements made for a single specimen (e.g. all blood gas measurements from the same sample of blood).
- A priority column indicates the priority level of the laboratory measure.
- Now contains the name of the test performed.
- Instead of
enddate, prescriptions now has
- This means all prescriptions now have the date and time of start/stop
- In an internal assessment, only 10 prescriptions were missing the start hour, and 1650 prescriptions were missing the stop hour (there are over 17 million rows in this table).
- We cannot guarantee the start time is the first instance of patient administration (as these are prescriptions), but the added resolution should help in research studies.
formulary_drug_cdhave been removed.
drug_name_poe, when not null, was always equal to
drugis the displayed drug name in the EHR, and is more reliable than
formulary_drug_cdwas an internal ontology that did not provide additional information over
- New columns!
pharmacy_id- to link to the pharmacy table which has additional information about the prescription
doses_per_24_hrsprovides the number of doses per 24 hours prescribed by this row.
Was this page helpful?
Glad to hear it! Please raise an issue here to tell us how we can improve.
Sorry to hear that. Please raise an issue here to tell us how we can improve.