MIT-LCP / MIT-LCP/mimic-code

Patients without an icustay_id

Open
#775 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Description

There are 46520 patients admitted from the admissions and patients table, but only 46476 in the icustays table. So there is a difference of 44. I thought that MIMIC data are all patients who have stayed at the ICU, why are some patients not assigned an icustay_id?

I tried to investigate this by looking at the information from the admissions table of

SELECT * FROM admissions WHERE subject_id NOT IN 
(SELECT DISTINCT subject_id FROM icustays)

From the results of this query, we see that 20 of the 44 even have chartdata.

Next I looked at the transfers table

SELECT * FROM transfers WHERE subject_id NOT IN 
(SELECT DISTINCT subject_id FROM icustays)

It seems to me that a few of the individuals were never admitted (i.e. they did not have a row which say 'admit' in admissions table), so were they already at the hospital when the data started in be collected for MIMIC? Subject_id 736 seems to be one such individual, they have a lot of data in chartevents which pre-dates the first entry they have on the transfers table. Their first entry in transfers states that they moved out of MICU into a ward, so this would make sense.

However for most (35 of the 44) individuals they have information on their admissions. I proceeded to look at subject_id 3004 who has chartevents as well as a row saying 'admit' in admissions. They stayed in wards 45 and 49 which did not seem to correspond to a cost centre. I extracted the chartevents information we have on them with

SELECT DISTINCT c.itemid, label 
FROM chartevents c 
INNER JOIN d_items d ON c.itemid = d.itemid WHERE subject_id = 3004

which seems to suggest that they only had laboratory events.

Is my assumption correct that some of these patients were already in ICUs at the start of the recording period?
Were there any other particular reasons these 44 individuals are not assigned an icustay_id? Why were individuals such as these included?

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 MIMIC online documentation, then reproduce the stated comparisons across admissions, patients, icustays, transfers, chartevents, and d_items for the 44 patients. Check the examples for subjects 736 and 3004 and trace how ICU admission and ward data are represented. Done means documenting the reasons these patients lack an icustay_id and why they remain in the dataset.

Written by the indexing model from the issue text.

Assessment

Tech stack
sql
Domain
databases, 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.