RapidMiner

MIMIC database is interested in AWS

Super Contributor

MIMIC database is interested in AWS

Hi,
I got a mail from Ken Pierce (Ken Pierce <kpierce@mit.edu>) were the interest for moving the MIMIC-II database (http://www.physionet.org/physiobank/database/mimicdb/ to AWS is expressed.
https://docs.google.com/forms/d/1Nl-ZzMPBDH6-ImrFPE3HfCrrvku50UfcY8UWwK3czeA/viewform?uspsend_form
I sent a reply to consider use of RM for that as presented in https://www.youtube.com/watch?v=zToFij3SW8k
I keep you all in touch
Sven
4 REPLIES
Regular Contributor

Re: MIMIC database is interested in AWS

So exciting I can barely contain myself, but is it wise to put people's email addresses out there?

H
Super Contributor

Re: MIMIC database is interested in AWS

Hi,
MIMIC-III clinical database has been recently published. It now consists of more recent data making this database very interesting to use and demonstrate the potential of RM for the medical community. Another advantage is the fact it now consists of 23 comma-delimited (CSV) files, with fields separated by commas and text strings are surrounded by double quotes. Two checksum files are also provided, allowing the integrity of the data to be checked before and after decompression.Uncompressed size must be around 40GB.
https://physionet.org/works/MIMICIIIClinicalDatabase/files/
Previously I used the MIMIC-II database in a RM-Radoop-Hive configuration https://www.youtube.com/watch?v=zToFij3SW8k.
Which solution would best suite the use for the MIMIC-III? Any proposals?
Sven
Moderator

Re: MIMIC database is interested in AWS

Hi sven,
40GB looks like a handleable data size for a standard database.
But it depends a bit on what you want to do with it.

Cheers,
Martin
--------------------------------------------------------------------------
Head of Data Science Services at RapidMiner
Regular Contributor

Re: MIMIC database is interested in AWS

As they say, size isn't everything, it depends on what you want to do with it.

H