low matching rate between the Matched Subset and the Clinical Database
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 82
- Forks
- 21
- Avg merge
- 35m
- Merged PRs (30d)
- 1
Description
Hi,
Thanks so much for your rich MIMIC-III. I have a question regarding the matched data. Right now we are finding a low matching rate between the Matched Subset and the Clinical Database records. The dates don’t match well in a large proportion of the cases. How should we match when the dates do not match?
SUBJECT_ID 107: 1 of 3 matches
Matched Subset Records (pXXNNNN-YYYY-MM-DD-hh-mm):
p000107-2124-01-10-05-53n
p000107-2123-07-26-03-10n
p000107-2122-05-14-21-02n
Clinical Database ADMITTIME/ DISCHTIME:
2115-02-20 17:41:00 / 2115-02-21 16:30:00
2121-11-30 19:24:00 / 2121-12-05 14:18:00
2122-05-14 19:37:00 / 2122-05-18 15:11:00
Thanks for your help,
Gene
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 by comparing the matched-subset identifiers and dates with the Clinical Database records shown for SUBJECT_ID 107. Determine the intended matching rule for date discrepancies and document or validate the expected result; done when the matching behavior and handling of mismatches are clearly established.
Written by the indexing model from the issue text.
Assessment
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100