Unable to Access Derived Tables for MIMIC-IV v3.1 on BigQuery – Possible Issue with Table References
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 3.4k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
I’m currently working with the MIMIC-IV v3.1 dataset on Google BigQuery (mimiciv_3_1_hosp and mimiciv_3_1_icu) and wanted to use the mimiciv_derived tables provided in your official GitHub repository. However, we are unable to access or generate these derived tables directly in BigQuery.
After reviewing the SQL scripts for generating derived tables such as the Charlson Comorbidity Index, I noticed that the code references an older dataset version, specifically:
sql
FROM physionet-data.mimiciv_hosp.diagnoses_icd
Whereas the current version we’re using is structured as:
sql
FROM physionet-data.mimiciv_3_1_hosp.diagnoses_icd
This mismatch might be the reason we’re unable to use or recreate the derived tables in the current version.
Could you please clarify:
1.Is there an updated version of the derived queries compatible with MIMIC-IV v3.1 on BigQuery?
2.If not, is there a plan to release updated versions that reference the current table structures?
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 derived-table SQL scripts, including the Charlson Comorbidity Index query, and compare their table references with the MIMIC-IV v3.1 dataset names shown in the issue. Check whether the queries can run against the v3.1 structures and identify the scope of any required reference updates. Done means establishing compatibility or documenting the needed version-specific queries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sql
- Domain
- data, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100