Thanks Heath, Setting a value constraint makes sense - do you allow negative offset? We have some time series observation data where offset is negative. In practice it doesn't make much sense but in reality it exists.
I can also imagine the sort of problems you may be facing - does this mean we should perhaps define priority/preference over EVENT.time vs. EVENT.offset. Obviously we got a problem when both exists. Cheers, -koray From: openEHR-technical [mailto:[email protected]] On Behalf Of Heath Frankel Sent: Monday, 15 February 2016 7:53 p.m. To: For openEHR technical discussions Subject: Re: Strange use of 'offset' as a settable RM attribute Does our opt validator validate a data instance against this? Yes. It causes all sorts of problems in scenarios like apgar when event times are real rather than derived from the origin and this constraint. Regards Heath On Sun, Feb 14, 2016 at 11:34 AM -0800, "Ian McNicoll" <[email protected]<mailto:[email protected]>> wrote: Thanks Heath, That makes sense. Does OceanEHR validate the constraint? Ian Dr Ian McNicoll mobile +44 (0)775 209 7859 office +44 (0)1536 414994 skype: ianmcnicoll email: [email protected]<mailto:[email protected]> twitter: @ianmcnicoll [https://docs.google.com/uc?id=0BzLo3mNUvbAjT2R5Sm1DdFZYTU0&export=download] Co-Chair, openEHR Foundation [email protected]<mailto:[email protected]> Director, freshEHR Clinical Informatics Ltd. Director, HANDIHealth CIC Hon. Senior Research Associate, CHIME, UCL On 14 February 2016 at 19:02, Heath Frankel <[email protected]<mailto:[email protected]>> wrote: Hi Koray, This is a constraint on the value that origin function returns rather than indicating it is a settable attribute. This was how Sam defined the events on an apgar score, 1 min, 5 min, etc. Regards Heath _____________________________ From: Ian McNicoll <[email protected]<mailto:[email protected]>> Sent: Sunday, February 14, 2016 5:10 AM Subject: Re: Strange use of 'offset' as a settable RM attribute To: For openEHR technical discussions <[email protected]<mailto:[email protected]>> Hi Koray, I agree - can you create a JIRA PR at ... https://openehr.atlassian.net/projects/AEPR/issues/AEPR-45?filter=allopenissues Ian Dr Ian McNicoll mobile +44 (0)775 209 7859<tel:+44%20775%20209%207859> office +44 (0)1536 414994<tel:+44%201536%20414994> skype: ianmcnicoll email: [email protected]<mailto:[email protected]> twitter: @ianmcnicoll [https://docs.google.com/uc?id=0BzLo3mNUvbAjT2R5Sm1DdFZYTU0&export=download] Co-Chair, openEHR Foundation [email protected]<mailto:[email protected]> Director, freshEHR Clinical Informatics Ltd. Director, HANDIHealth CIC Hon. Senior Research Associate, CHIME, UCL On 12 February 2016 at 04:29, Koray Atalag <[email protected]<mailto:[email protected]>> 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? 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. Cheers, -koray _______________________________________________ openEHR-technical mailing list [email protected]<mailto:[email protected]> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org _______________________________________________ openEHR-technical mailing list [email protected]<mailto:[email protected]> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
_______________________________________________ openEHR-technical mailing list [email protected] http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
