MIT-LCP / MIT-LCP/mimic-code

BigQuery Access Denied - received confirmation email but cannot query

Open
#1,986 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Jupyter Notebook
Stars
3.4k
Forks
1.7k
PR merge metrics
No merged PRs in 30d

Description

Problem

I have completed all required steps to access MIMIC-IV on BigQuery,
but I am still receiving "Access Denied" errors when attempting to query.

Steps Completed

  • PhysioNet credentialing: approved
  • CITI training: submitted and approved
  • DUA signed for MIMIC-IV v3.1
  • DUA signed for MIMIC-IV-Note v2.2
  • DUA signed for eICU v2.0
  • Gmail added and verified in PhysioNet cloud settings
  • Clicked "Request access using Google BigQuery" for all three datasets
  • Received confirmation emails for all three datasets

Error Message

Access Denied: Table physionet-data:mimiciv_v3_1_hosp.patients:
User does not have permission to query table
physionet-data:mimiciv_v3_1_hosp.patients, or perhaps it does not exist.

Environment

  • Google Cloud Project: mimic-research-492706
  • Billing: active (linked to billing account)
  • physionet-data datasets visible in BigQuery sidebar:
    eicu_crd, mimiciv_3_1_hosp, mimiciv_3_1_icu, mimiciv_note
  • Query runs from project: mimic-research

What I Tried

  • Clicked "Request access using Google BigQuery" multiple times
  • Tried querying from both mimic-research and mimic-sclc projects
  • Waited several hours after receiving confirmation emails
  • Hard refreshed BigQuery page (Ctrl+Shift+R)

Question

Could you please verify that my Gmail has been correctly added
to the BigQuery IAM permissions for physionet-data?

Thank you.

Physionet user name: hanlyi
Gmail: han970820@gmail.com

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No repository file, test, or code entry point is identified; start by reviewing the BigQuery access requirements and the reported project and dataset names. Confirm whether the user's Gmail account has the required permissions and whether the documented access flow matches the error; done means the requester can query the stated table or receives a clear diagnosis.

Written by the indexing model from the issue text.

Assessment

Tech stack
google-cloud
Domain
authorization, cloud, databases
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.