Strange use of 'offset' as a settable RM attribute

Koray Atalag k.atalag at
Thu Feb 11 23:29:48 EST 2016


We noted it is possible to set values from AE/TD to a RM attribute named "offset"
In the specs<> (looked at >1.0.1) it is not a regular attribute but a function which returns a computed value using diff HISTORY.origin and EVENT.time
Note that this diff can also be a negative value - which doesn't seem to be supported by AE/TD or in instance data

An example ADL:

POINT_EVENT[at0002] occurrences matches {0..*} matches {        -- Any event
               offset matches {
                              DV_DURATION matches {
                                             value matches {|PT0.125S|}

Isn't this weird?
I would expect this to return a value if a valid ISO8601 time has been entered for both HISTORY.origin and EVENT.time but not set as an attribute directly.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the openEHR-technical mailing list