Over 8% of chartevents have charttime > storetime
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 3.4k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
How do we interpret events where the observation/measurement occurs after it has been manually input/validated?
From the docs (https://mimic.mit.edu/docs/iv/modules/icu/chartevents/):
charttimerecords the time at which an observation was made, and is usually the closest proxy to the time the data was actually measured.storetimerecords the time at which an observation was manually input or manually validated by a member of the clinical staff.
Histogram of differences between charttime and storetime where charttime > storetime:
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the ICU chartevents documentation linked in the issue and compare its definitions of charttime and storetime with the reported histogram. Investigate why charttime can exceed storetime and document a clear interpretation for these records, including what users should understand about the timestamps.
Written by the indexing model from the issue text.
Assessment
- Domain
- databases, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100