From e6abac686bad9aeeadcb094c10e123503799ac52 Mon Sep 17 00:00:00 2001 From: JackieMe Date: Fri, 3 Aug 2018 16:15:45 +0800 Subject: [PATCH] hadm_id written as icustay_id In the above result output `icustay_id` = 291788 has an entry for OMED, 100006 in the text below is the hadm_id. --- tutorials/cohort-selection.ipynb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tutorials/cohort-selection.ipynb b/tutorials/cohort-selection.ipynb index d23d152fa..c16cc53eb 100644 --- a/tutorials/cohort-selection.ipynb +++ b/tutorials/cohort-selection.ipynb @@ -2242,7 +2242,7 @@ "cell_type": "markdown", "metadata": {}, "source": [ - "Note how `icustay_id` = 100006 no longer has an entry for OMED above: this is because this service was given after their ICU admission, so we do not want to consider it. Also note that our join clause has `+ interval '12' hour` - this adds a bit of \"fuzziness\" to our criteria. As these times are entered asynchronously by different people in varying locations in the hospital, there can be some minor inconsistencies in the order. For example, a patient may be transferred to the surgical service for ICU admission, but the `transfertime` in *services* occurs after the `intime` in *icustays* by an hour or so. This is administrative \"noise\" - and a fuzzy interval can be useful in these cases. Again, this is a cohort selection decision - you may not want to use an interval as large as 12 hours - perhaps only 2 or 4 - though in this case there is likely to be very minor differences as 80% of patients never have a change in hospital service.\n", + "Note how `icustay_id` = 291788 no longer has an entry for OMED above: this is because this service was given after their ICU admission, so we do not want to consider it. Also note that our join clause has `+ interval '12' hour` - this adds a bit of \"fuzziness\" to our criteria. As these times are entered asynchronously by different people in varying locations in the hospital, there can be some minor inconsistencies in the order. For example, a patient may be transferred to the surgical service for ICU admission, but the `transfertime` in *services* occurs after the `intime` in *icustays* by an hour or so. This is administrative \"noise\" - and a fuzzy interval can be useful in these cases. Again, this is a cohort selection decision - you may not want to use an interval as large as 12 hours - perhaps only 2 or 4 - though in this case there is likely to be very minor differences as 80% of patients never have a change in hospital service.\n", "\n", "Finally, we want to collapse this down so we only have one service for a given ICU admission. As done earlier, we will use RANK() to do this." ]