Strange use of 'offset' as a settable RM attribute

Thomas Beale thomas.beale at openehr.org
Mon Feb 15 04:47:19 EST 2016



On 12/02/2016 04:29, Koray Atalag wrote:
>
> Hi,
>
> We noted it is possible to set values from AE/TD to a RM attribute 
> named “offset”
>
> In the specs 
> <http://www.openehr.org/releases/RM/Release-1.0.3/docs/data_structures/data_structures.html#_event_class> 
> (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?
>

it just checks that the value EVENT.offset, when called at runtime, is 
within some range or equal to some value.

> 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.
>

if EVENT.offset doesn't return a valid value, its implementation has a bug.

- thomas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20160215/eab4c6e4/attachment-0002.html>


More information about the openEHR-technical mailing list