MIT-LCP / MIT-LCP/mimic-code

Questions regarding MIMIC-III Waveform

Open
#1,277 0 comments 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

Prerequisites
Description

Hello, I am working with ECG data from MIMIC-III Waveform Database Matched Subset and ECG notes from NOTEEVENTS. What I currently want to do is to map ECG data with their corresponding ECG notes, but I've encountered some problems while doing so.

  1. I already know that there is no charttime with ECG notes, but I am wondering if there are any routines for when the ECG notes were charted (e.g., practitioners usually chart the ECG notes every 9:00 am, ...).
  2. I think it is not feasible to chart ECG notes from the entire ECG data since the ECG records are too long (several hours / days). Are there any metadata that pinpoints or at least roughly shows when the ECG notes are charted from the corresponding ECG data? In other words, any indication that shows which part of the ECG data the practitioner looked at in order to chart ECG notes.
  3. Lastly, I found that there are multiple ECG notes which are charted at the same date (actually, same subject_id, hadm_id, chartdate). Is there any way to identify which one is the first, second, ..., and so on?

Thank you in advance!
Jungwoo Oh

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 with the linked MIMIC-III Waveform Database Matched Subset documentation and the NOTEEVENTS data referenced in the issue. Determine whether the three requested relationships—note charting time, the reviewed waveform segment, and ordering notes on the same date—are documented or represented in available metadata; done means providing supported answers or documenting that the metadata is unavailable.

Written by the indexing model from the issue text.

Assessment

Domain
data
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.