MIT-LCP / MIT-LCP/mimic-code

Huge inconsistencies in patientweight in inputevents

Open
#1,539 3 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

Discussed in https://github.com/MIT-LCP/mimic-code/discussions/1535

Originally posted by mpierrau May 2, 2023
Hi!

I have been working on MIMIC-IV for some time and recently discovered that the column patientweight has some extreme inconsistencies for some stay_id which I fail to find a reasonable explanation.

There are multiple rows with starttime within minutes but with different patientweight. I understand this can happen, but the problem is that some differences are extremely big -- like tens of kilos difference.

I've been parsing MIMIC-IV using Python so I don't have a nice reproducible SQL code for you, but you can have a look at for example stay_id's:
39615949 (diff 170 kg between starttime 2145-10-06 20:52:00 and starttime 2145-10-06 22:31:00)
35032951 (diff 23 kg)
38680231 (diff 25 kg)
33230840 (diff 107 kg)
...

Can you provide a reason for why this is?

Is daily weight (itemid 224639 in chartevents) or admission weight (itemid 226512 in chartevents) a better option?

Kindly,
Magnus

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 by comparing the inputevents patientweight rows for the listed stay_id values, then compare them with chartevents itemids 224639 and 226512. The issue names no repository files or tests, so first identify the MIMIC-IV data-loading or query entry points and reproduce the reported weight differences. Done means documenting a supported explanation and determining which weight source is appropriate.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, sql
Domain
data, databases
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.