Prerequisites
Description
Hi,
in lines 264 to 271 in https://github.com/MIT-LCP/mimic-code/blob/main/mimic-iii/concepts/durations/vasopressor_durations.sql, vasopressor administrations from inputevents_mv are grouped based on their linkorderid, and the minimum and maximum starttime and endtime, respectively, are calculated for each group. This makes sense if the starttime of an entry equals the endtime of the previous entry, but not if there is a gap between. According to #47, this should never be the case after removing "Rewritten" entries, but I found at least one counterexample, namely linkorderid = 8781494:
select
icustay_id, linkorderid, starttime, endtime, statusdescription, itemid
FROM inputevents_mv
where linkorderid = 8781494
order by starttime
In the result, there is a ~6h gap between 2167-08-05 21:16:00 and 2167-08-06 04:01:00. To my understanding, such gaps should not be included in the final vasopressor durations.
Note: The status of the entry before the gap is "Paused". I did not investigate whether "Paused" entries always lead to gaps, but can do that if it helps.
Prerequisites
Description
Hi,
in lines 264 to 271 in https://github.com/MIT-LCP/mimic-code/blob/main/mimic-iii/concepts/durations/vasopressor_durations.sql, vasopressor administrations from
inputevents_mvare grouped based on theirlinkorderid, and the minimum and maximumstarttimeandendtime, respectively, are calculated for each group. This makes sense if thestarttimeof an entry equals theendtimeof the previous entry, but not if there is a gap between. According to #47, this should never be the case after removing "Rewritten" entries, but I found at least one counterexample, namelylinkorderid=8781494:In the result, there is a ~6h gap between
2167-08-05 21:16:00and2167-08-06 04:01:00. To my understanding, such gaps should not be included in the final vasopressor durations.Note: The
statusof the entry before the gap is "Paused". I did not investigate whether "Paused" entries always lead to gaps, but can do that if it helps.