Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

MIMIC-IV v3.1: subject_id incorrectly identified as admitting provider

Open Beginner friendly
#2,169 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
95/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Domain
documentation

Research direction

The issue points to a specific documentation file: MIMIC-IV v3.1 Data Description for the hosp module. Locate the file (likely in documentation or a docs folder) and find the second paragraph under provider information. Verify the current text against the admissions table schema. The fix is to change 'subject_id' to 'admit_provider_id' and ensure it links correctly to provider.provider_id. Confirm by checking the release notes mentioned.

Written by the indexing model from the issue text.

Description

I noticed a likely documentation error in the MIMIC-IV v3.1 documentation:
Location: MIMIC-IV v3.1 → Data Description → hosp → second paragraph under the provider information.
The paragraph states:
“For example, the provider who admits the patient to the hospital is documented in the admissions table as subject_id.”
This appears to be incorrect. subject_id identifies the patient, while the admitting provider is documented in admissions.admit_provider_id, which links to provider.provider_id.
This is also consistent with the MIMIC-IV v3.1 release notes under the v2.2 changes, which explicitly describe admit_provider_id as “the provider who admitted the patient.”

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

Getting set up

We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.

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.

More from MIT-LCP/mimic-code

All issues in MIT-LCP/mimic-code

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.