-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MIMIC-II from MIMIC-III #229
Comments
I suspect the numbers depend on exactly which version of which database you are using. For example, I have an older copy of the MIMIC-II data, version 2.6, in which d_patients has 32535 entries and admissions has 36094. Where did your number of 25549 come from? |
There is a lot of info on the various differences between MIMIC-II and MIMIC-III here: https://mimic.physionet.org/mimicdata/whatsnew/ Specifically, we note that we replaced censusevents in MIMIC-II with transfers in MIMIC-III: https://mimic.physionet.org/mimicdata/whatsnew/#censusevents-replaced-by-transfers Basically, MIMIC-II used the ICU information system to define ICU admissions. MIMIC-III uses a hospital wide patient tracking database to define ICU admissions. As a result, you get some inconsistencies, mainly revolving around administrative differences. An absolute mapping between the two is not possible. Essentially though, the patients who satisfy |
Closing as it seems we provided sufficient insight! |
Hi
Is it possible to extract MIMIC-II patients/admission episodes from MIMIC-III. Pre-2015 papers used MIMIC-II and built their models on them. For benchmarking we would still like to have access to that cohort.
Since Metavision system was introduced in MIMIC-III, we thought of separating based on the datasource but there are inconsistences:
There is a column in “icustays” table called “dbsource”, where 3 values are possible:
carevue, metavision, both.
The number of patients/admission for each value you can see in the following table:
However, there were 25549 patients in MIMIC-II database (carevue). Can you please help us?
Another solution can be to install MIMIC 2 database but that won't allow us to seamlessly exchange code/sql scripts over MIMIC-II and MIMIC-III.
The text was updated successfully, but these errors were encountered: