search

MIT-LCP / mimic-iii-paper

Repository for the paper describing MIMIC-III
http://www.nature.com/articles/sdata201635
73 stars 38 forks source link

Unification of tables would be in line with evolution of shared dataset models #12

Closed tompollard closed 8 years ago

tompollard commented 8 years ago

The MIMIC-III data structure is obviously a reflection of the underlying data sources, and an effort to continue with some consistency from MIMIC-II. But ideally such a dataset would unify procedures, for example, into a single table rather than having a CPT events table and ICD procedure table. Such unification would require a more robust vocabulary approach but would be more in line the evolution of shared dataset models (e.g., OMOP CDM). Similarly, DATETIMEEVENTS seem like a complicating table that may have better logical homes for its constituent data.

tompollard commented 8 years ago

We acknowledge that the data model could be improved and we have taken on board these suggestions. While there is no perfect solution, our approach is to encourage researchers to develop database views where appropriate and share the relevant code via the MIMIC Code Repository. Alongside the work of the community, we will continue to develop the MIMIC over time.

The “Data tables” section was updated to clarify these points: https://github.com/MIT-LCP/mimic-iii-paper/commit/7513b29b6f8a4962ff7f54707d3cccc1cffacaa7#diff-a45f2757f94fd2337ebf7ddd018c11a2L230

tompollard commented 8 years ago

"In some cases it would be possible to merge tables - for example, the D_ICD_PROCEDURES and CPTEVENTS tables both contain detail relating to procedures and could be combined - but our approach is to keep the tables independent for clarity, since the data sources are significantly different. Rather than combining the tables within MIMIC data model, we suggest researchers develop database views and transforms as appropriate."