How to identify septic shock patients in mimic iv 2.2 database using sql code.
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
Hello, Recently, I have been trying to extract patients with septic shock in the ICU and have encountered some difficulties.
Previously, I saw an discussion on how to identify septic shock patients, and I was greatly inspired by it. However, I do not quite understand how the third standard is expressed in SQL code in mimic iv 2.2 database.
"3.Patients with septic shock can be identified with a clinical construct of sepsis with persisting hypotension requiring
vasopressors to maintain MAP ≥65 mm Hg and having a serum lactate level >2 mmol/L(18 mg/dL) despite adequate volume resuscitation."
May I ask if you can share similar SQL code examples for my reference?Thank you very much!
similar issues: Onset time of septic shock #576
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 with the MIMIC documentation and the related issue, Onset time of septic shock #576, to understand the existing septic-shock definition and MIMIC-IV 2.2 data structures. Determine whether the requested SQL example belongs in an existing query or documentation location; done means providing a reviewed, reproducible example that addresses the third criterion and is consistent with the documented data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sql
- Domain
- databases
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100