asyml / asyml/ForteHealth

Create an example for MIMIC-III clinical note pipeline.

Open
#64 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
14
Forks
5
PR merge metrics
No merged PRs in 30d

Description

I had this idea because I wanted to have a pipeline that had the ability to cover all of our processors (in the NLP field) as much as possible. And I think the mimic-iii data satisfies that.

In this example, we should try to use all the processors we have, for example, if our sample data is selected from a patient's self-report or query or clinical diagnose records (maybe a covid-19 patient), which describes their physical condition, e.g., with A symptoms and without B symptoms (Negation Context Detect), and then give a diagnosis based on the symptom description (ICD Coding). The user description may have a more specific time, such as how it was last night, how it was last month, so that it can be extended to the Temporal domain. ( I know the temporal related processors may be not completed, we can just work on all the things we have currently).

But it may be hard to find a piece of data that covers all the processors, for this issue, maybe we can just concatenate them to achieve what we want.

Possible included components:
1. Sentence Segmenter
2. Tokenizer
3. Bio NER Tagger
4. Negation Context
5. ICD Coding
6. Temporal Mention Tagging
7. Temporal Relation Extraction
8. Deidentification

(Just ignore the processors we do not have currently)

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the currently available processors listed in the issue: sentence segmentation, tokenization, biomedical NER, negation context, ICD coding, temporal tagging and relation extraction, and deidentification. Determine which processors and MIMIC-III sample data are available, then define an example pipeline that uses as many as possible while excluding unavailable components. Done means the repository contains a runnable clinical-note example covering the selected processors.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.