The mimiciv and mimiciv-v3_1 database on BigQuery, which one should we use?
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 3.4k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
MIMIC official website stated：“MIMIC-IV v3.1 is now available on BigQuery. Users may request access via PhysioNet. Currently, MIMIC-IV v3.1 is available on the mimiciv_v3_1_hosp and mimiciv_v3_1_icu schemas. MIMIC-IV v2.2 is available on the mimiciv_v2_2_hosp and mimiciv_v2_2_icu datasets as well as the mimiciv_hosp and mimiciv_icu datasets. On November 25th 2024, we will replace the data on mimiciv_hosp and mimiciv_icu with MIMIC-IV v3.1.”
The data on mimiciv is so different from data on mimiciv_v3_1 (BigQuery platform). The data on mimiciv is so different from data on mimiciv_v3_1 (BigQuery platform). If, as the official website stated, the mimiciv database was replaced with v3.1 on November 25th, 2024, the distribution of ICU types should not differ this much.
The mimiciv and mimiciv-v3_1 database on BigQuery, which one should we use?
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
No repository file or test is identified. Begin by comparing the BigQuery mimiciv and mimiciv_v3_1 datasets with the official MIMIC-IV v3.1 statement, including the listed schemas and ICU distributions. Done means establishing which dataset should be used and explaining the reported differences.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- google-cloud
- Domain
- cloud, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100