Stream: Vulcan/SoA
Topic: Visit Timing and Windows
Javier Ezcurra (Apr 01 2022 at 20:13):
Hello!
In just about clinical trial SoA, visits exist that have what I'll call "relative timing" as well as visit windows. Typically, the timing of a visit is relative to "Day 1" (usually a Baseline visit). For example:
-
Baseline visit
-- Timing: Day 1 -
Visit 2:
-- Timing: Day 10
-- Visit Window: +/- 1 day -
Visit 3:
--Timing: Day 30
-- Visit Window: +/- 2 days
These relative timings have to be abstracted (as opposed to being represented as a date) because each subject in a clinical trial will start at different points in time (e.g., Subject 1 starts on May 1st; Subject 2 starts on August 5th).
Question: Has anybody figured out how to store this info in PlanDefinition? The needs on the app we're working on are:
- Need to store which visit (PlanDefinition.Action) is the "anchor" visit (the one against which the others are timed)
- Need to store the relative timing value and units
- Need to store the visit window value and units.
Last updated: Apr 12 2022 at 19:14 UTC
