Improved EVENT model
The utility of point-in-time and interval events has become clear
during archetype design analysis of clinically measured phenomena.
To further improve the representation of interval events, we should
allow for:
- optional record how many samples were taken in each interval event
  (and/or sample width of original sampling leading to an interval
  event).
- variance and/or other measures during interval
- a way of allowing one interval event to capture samples within +/-
  xxx, i.e. outer limits to still call it one event.
- to make archetyping clearer, maybe separate out EVENT, POINT_EVENT,
  INTERVAL_EVENT
Status
Assignee
JeffJ
Reporter
(Sam Heard) inactive
Change Description
Changes are as follows:
- create EVENT, POINT_EVENT, INTERVAL_EVENT classes, with EVENT as the
superclass
- rename HISTORY.items to HISTORY.events so as to improve readability
of paths.
- move all semantics to do with interval events to INTERVAL_EVENT
- allow multiple {math_function, value} pairs, modelled as
Hash<T:ITEM_STRUCTURE, DV_CODED_TEXT>, where the DV_CODED_TEXT codes
for math functions like average, min, max etc. This allows e.g. +/-
limits to be included in the same event as the average
- add summary information structure to HISTORY, allowing multimedia
or other textual summary version of history to be included - typically
for image from imaging lab which goes with data, or even on its own
- add HISTORY.duration: DV_DURATION, to indicate complete length of
history.
- remove EVENT.is_point_in_time
Approved By
ARB
Components
Fix versions
Priority
Minor