Problems about extracting pregnancy patients from MIMIC-IV v2.2
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
- Put an X between the brackets on this line if you have done all of the following:
- Checked the online documentation: https://mimic.mit.edu/
- Checked that your issue isn't already addressed: https://github.com/MIT-LCP/mimic-code/issues?utf8=%E2%9C%93&q=
Description
Greetings! I'm trying to extract pregnant patients diagnosed with particular disease and I have already tried using itemid=225082 (chartevents) to identify those potential pregnant individuals. However, I got puzzled about the corresponding value. According to previous issue proposed by others (https://github.com/MIT-LCP/mimic-code/issues/612), could I equal value = 0 to "no pregnancy" and value = 1 to "indeed pregnancy"?
I also noted that chartevents reside in ICU module. Thus, is it possible that some pregnant patients were only documented in hosp but could not be identified by chartevents? In this reason, I'm wondering if there exists other methods to identify pregnancy? I noted your practical response in https://github.com/MIT-LCP/mimic-code/issues/1724 but the resulted sample size was still rather limited.
Thanks for your time and support.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the MIMIC-IV documentation and the linked issues 612 and 1724, focusing on chartevents itemid 225082 and the hosp data. No repository file or test is identified; done would require a documented, evidence-based method for identifying pregnancy patients and clarifying how the recorded values should be interpreted.
Written by the indexing model from the issue text.
Assessment
- Domain
- databases
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100