Suggestions for improving MIMIC-IV-NOTE content
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
- 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
I suggest that the mimic-iv-note folder(mimic-code/tree/main/mimic-iv-note/buildmimic/postgres) should also have a file to verify the amount of data, such as mimic-code/blob/main/mimic-iv-ed/buildmimic/postgres/validate.sql.
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 comparing mimic-iv-note/buildmimic/postgres with mimic-iv-ed/buildmimic/postgres/validate.sql. Use the existing validate.sql as the reference for the requested data-amount verification. Done means the MIMIC-IV-NOTE PostgreSQL build includes a corresponding validation file.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 48/100