paused vasopressor durations

Prerequisites

• Put an X between the brackets on this line if you have done all of the following:
  • Checked the online documentation: https://mimic.mit.edu/
  • Checked that your issue isn't already addressed: https://github.com/MIT-LCP/mimic-code/issues?utf8=%E2%9C%93&q=

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 https://github.com/MIT-LCP/mimic-code/issues/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.

Start with mimic-iii/concepts/durations/vasopressor_durations.sql, especially lines 264–271, and inspect the linked issue #47. Run the provided inputevents_mv query for linkorderid 8781494, then investigate how Paused entries and gaps affect the grouped duration. Done means the duration logic reflects the expected treatment of gaps and the counterexample is covered by validation.