On 21-03-18 13:51, Thomas Beale wrote:
On 20/03/2018 23:33, A Verhees wrote:
One last remark.
There is in medical context need of a datatypes to express: "do this
one time a month, for example on a specific date".
But technically seen, this is not a duration, the maybe a need for
another datatype to express this.
Using the duration for this may be a handy shortcut in specs, but it
is not right. It is in fact misusing a datatype which does not
support this expression. The ISO string should also be changed
accordingly.
we don't really use Duration to represent 3 times / day. There are old
HL7 data types which we included in openEHR to do this, called GTS and
its children
<http://www.openehr.org/releases/RM/latest/docs/data_types/data_types.html#_time_specification_package>.
It seems that noone uses these. THere have been many other attempts to
define either types or structures, like iCal and other
calendar-related structures. But I don't see a clear winner in terms
of standards.
THe medication archetypes solve it by using multiple fields, and in
Task Planning we had to create some new time specification types as
well - CLOCK_TIME, CALENDAR_TIME, and CUSTOMARY_TIME
<http://www.openehr.org/releases/PROC/latest/docs/task_planning/task_planning.html#_specifying_time>.
You can need Duration for many purposes
Which comes to mind. How long was the patient feeling bad? How long did
the patient sleep? How long was he staying in the hospital. These are
all Durations. How long was the pregnancy time, How much time is their
between two named phases of a heartbeat
_______________________________________________
openEHR-technical mailing list
[email protected]
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
