Adjust HISTORY
Raise CR
Analysis
Resolution
Raise CR
Analysis
Resolution
Description
Activity
Show:
Thomas Beale
updated the WorkflowAugust 11, 2008 at 10:18 PMCopy of ARB CR
ARB CR
Thomas Beale
updated the WorkflowAugust 11, 2008 at 10:14 PMARB CR
Copy of ARB CR
openEHR admin
updated the WorkflowAugust 11, 2008 at 10:05 PMCopy of ARB CR
ARB CR
openEHR admin
updated the WorkflowAugust 11, 2008 at 9:58 PMARB CR
Copy of ARB CR
openEHR admin
updated the WorkflowMarch 12, 2008 at 4:21 AMCR
ARB CR
(Sam Heard) inactive
created the IssueMarch 31, 2002 at 11:00 PMFixed
Assignee
Reporter
(Sam Heard) inactive
(Sam Heard) inactivePriority
Created March 31, 2002 at 11:00 PM
Updated January 6, 2006 at 12:00 AM
Resolved January 6, 2006 at 12:00 AM
There are various proposals to change HISTORY<T>, as follows:
instead of using origin & offsets, use absolute times in each EVENT
remove SINGLE_EVENT and simplify class structure back to just
HISTORY and EVENT
make it optional (AG) because many instances of OBSERVATION will
not specifically record their own observation time - they
'inherit' the time of the clinical session. (TB: I agree with
the point - in today's GP consults - since there is almost no
automated recording of anything, but disagree with the solution.
Recording of observation time is essential, and even if the
absolute times of multiple observations in a GP consult are
uninteresting, the order may be significant.
A further requirement which has come to light during archetype
and system-building in Australia is that state:ITEM_STRUCTURE
should be available on EVENT, since it is usual to record
state at the time of the data event, rather than as a separate
time series on OBSERVATION, which it is currently. The latter is
not incorrect and should be retained; but the addition of EVENT.state
will handle the more common clinical cases.