MIT-LCP / MIT-LCP/mimic-code

Missing social history makes automated medical coding challenging

Open
#1,663 1 comment 1 reaction 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

Prerequisites
Description

Automated medical coding (also called medical code prediction) is a growing machine learning task that aims to predict medical codes given a discharge summary. MIMIC-IV has become a popular dataset to train and evaluate such models. However, there is an issue. Since your de-identification algorithm removed the social history section, certain annotated medical codes are impossible to predict. For instance, the medical codes representing whether the patient smokes (e.g., F17.210 and Z87.891) are often annotated in MIMIC-IV without being mentioned in the discharge summary. This is because of the missing social history.

The consequences of the missing section are that the models are trained on labels that are impossible to predict and are evaluated unfairly every time the necessary information would have been in the social history. Consequently, MIMIC-IV is a noisier dataset for automated medical coding than MIMIC-III (MIMIC-III contains the social history).

Is there a way to de-identify the discharge summaries without removing the social histories?

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

Start by reviewing the MIMIC-IV online documentation and the issue's examples of missing social history and affected codes. Determine whether discharge summaries can retain social histories while meeting de-identification requirements; done would require a documented, validated approach rather than a small repository edit.

Written by the indexing model from the issue text.

Assessment

Tech stack
machine-learning
Domain
data, machine-learning
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.