MIT-LCP / MIT-LCP/mimic-code

How much of MIMIC-IV is MIMIC-III?

Open
#1,521 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Jupyter Notebook
Stars
3.4k
Forks
1.7k
PR merge metrics
No merged PRs in 30d

Description

Prerequisites
Description

There are multiple issues regarding how much MIMIC-III and MIMIC-IV overlap. Most of those had the goal of merging the two datasets, and that problem is now solved by the CareVue dataset. However, I had trouble finding a good solution for basically the opposite operation; instead of merging III and IV, I'm looking for a way to remove data that was in III and is now also in IV. Background is that our team trained ML models on III and would now like to verify our results on the unseen IV data. I'm sure you're all aware of the problem that results in evaluating on data that has been used for training.

Since there does not seem to be a good way of linking the two datasets to filter for data in III, the question arises: how much of MIMIC-IV consists of MIMIC-III data? Does the 2008-2012 period in MIMIC-IV purely or mainly consist of MIMIC-III data, or was additional data added in that time period?

Also, to verify: is my assumption correct, that after adjusting for the anchor year shift, all data up to and including 2014 is potentially contaminated due to the anchor year group size?

Similar Issues

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the online documentation and the related issues 1331, 815, and 994. Investigate the relationship between MIMIC-III, MIMIC-IV, and the CareVue dataset, including the anchor-year period, then document a supported answer about overlap and potential contamination.

Written by the indexing model from the issue text.

Assessment

Domain
data, documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.