Stream: Vulcan/SoA
Topic: Next Question ...
Hugh Glover (Jan 14 2021 at 19:55):
Can we think more about the timing within a schedule? We need to represent:
- days (time) between activities - one way is to relate each activity to the one before, another is to relate each to a single fixed anchor date, are there others?
- windowing of dates - is this a per visit thing or is it a blanket across all visits? How would we handle exceptions?
Geoff Low (Jan 14 2021 at 20:43):
We've been talking about that; the two possibilities (assuming use of PlanDefinition) are to define a duration of the action using the timing[x] or through the use of the relatedAction.offsetDuration/Range (using the actionId to cross reference). With the relationship the link can be forward or backward looking (or at the same time). Some activities run continuously (eg collection of CM/AE) - the windowing can be done with offsetRange - but you lose the target day (ie Visit 2 happens 21 days after visit 1 +/- 2 days) - that might be a candidate for an extension as the +/- can be asymmetric about the target day
Hugh Glover (Jan 14 2021 at 22:19):
The exact same question about duration and range has just been asked on the #implementers stream!
Last updated: Apr 12 2022 at 19:14 UTC
