MIT-LCP / MIT-LCP/mimic-code

Identification of time stamps for intraoperative and postoperative period for cardiac surgery patients in MIMIC-IV

Open
#1,805 0 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
  1. Could you help me identify the time stamps for start and end of surgical procedure (e.g. cardiac surgery) in MIMIC-IV.
    The surgical procedure is identified by icd_code from procedures_icd table however, the surgical procedure's start and end times are not explicitly mentioned in the procedureevents table. There are multiple events in the procedureevents table such as 'OR received', 'invasive ventilation', 'chest intubation' etc. Is there a way to find the timestamps so as to find the duration of surgery (corresponding to the icd_code from procedures_icd table)? With such timestamps one can also identify other events strictly during the surgery such as blood loss volume.
  2. Usually patients have extended ICU stay post-surgery for close monitoring of patient's condition, however, I note that MAX(procedureevents.endtime) for a given patient is similar to icustays.outtime. How does one identify the postoperative period in ICU?

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-IV documentation and the procedures_icd, procedureevents, and icustays tables named in the issue. Compare their available timestamps and definitions to determine whether surgical and postoperative periods can be identified; done means providing a documented, reproducible interpretation or confirming that the requested timestamps are unavailable.

Written by the indexing model from the issue text.

Assessment

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