SOFA calculation (derived table) - ventilation and respiration / CNS.
Open
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
- [X ] 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
Hi, We have tried analyze the hourly sofa score from mimic_derived table and suggest the following considerations
- Please be careful with SOFA-CNS score for those who are on invasive ventilation. In this case, it is hard to evaluate the CNS status. We would suggest separating those who are on invasive ventilation to a different group.
- Please check the ventilation status when evaluating SOFA-respiration score. We found a lot of patients with respiration =0 but on invasive ventilation. This is not correct. In fact, Leo Celi suggested to set SOFA respiration = 1 for those who are on HFNC / Noninvasive ventilation / Invasive vent / Tracheostomy.
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 locating the MIMIC-derived table and the existing hourly SOFA calculation for the CNS and respiration components. Review how invasive ventilation, HFNC, noninvasive ventilation, and tracheostomy are represented before deciding how the scores should be classified. Done means the derived calculations reflect the issue's proposed ventilation handling and are validated against representative records.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jupyter-notebook
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100