History paths
Rong This is an important consideration - especially if we are to get the event right. We have recently been moving away from offset to a datetime stamp for the items in the history - as this is easier and more realistic for summary data over a long period. With this change - you want to find and label the 1 minute, 5 minute and 10 minute Apgars - as the absolute time has no meaning. The Editor allows you to constrain the run time name of the event. Cheers, Sam Rong Chen wrote: Hi Thomas! A question regarding implementation of History paths in reference model: from data_structures rev1.4, p26, one of the examples is event: | HISTORY.name | EVENT.name, e.g. |history|event_3. But class EVENT has no attribute called name, it doesn't inherit LOCATABLE either. Does this imply that perhaps EVENT (or its super class EVENT_ITEM) should inherit LOCATABLE? Thanks! Rong - If you have any questions about using this list, please send a message to d.lloyd at openehr.org - If you have any questions about using this list, please send a message to d.lloyd at openehr.org
History paths
Thanks, Sam! Please see my comments below. Sam Heard wrote: Rong This is an important consideration - especially if we are to get the event right. We have recently been moving away from offset to a datetime stamp for the items in the history - as this is easier and more realistic for summary data over a long period. Good to know that, I guess it will perhaps appear in the CR list soon. With this change - you want to find and label the 1 minute, 5 minute and 10 minute Apgars - as the absolute time has no meaning. The Editor allows you to constrain the run time name of the event. My impression is that archetype can't constrain more than what reference information model can provide. In this case, there is no attribute name in the class EVENT, so it's not going to help very much even the archetype editor allows you to assign a name to EVENT. Maybe I got it wrong? Cheers, Rong Cheers, Sam Rong Chen wrote: Hi Thomas! A question regarding implementation of History paths in reference model: from data_structures rev1.4, p26, one of the examples is event: | HISTORY.name | EVENT.name, e.g. |history|event_3. But class EVENT has no attribute called name, it doesn't inherit LOCATABLE either. Does this imply that perhaps EVENT (or its super class EVENT_ITEM) should inherit LOCATABLE? Thanks! Rong - If you have any questions about using this list, please send a message to d.lloyd at openehr.org - If you have any questions about using this list, please send a message to d.lloyd at openehr.org - If you have any questions about using this list, please send a message to d.lloyd at openehr.org
History paths
Hi Thomas! A question regarding implementation of History paths in reference model: from data_structures rev1.4, p26, one of the examples is event: | HISTORY.name | EVENT.name, e.g. |history|event_3. But class EVENT has no attribute called name, it doesn't inherit LOCATABLE either. Does this imply that perhaps EVENT (or its super class EVENT_ITEM) should inherit LOCATABLE? Thanks! Rong - If you have any questions about using this list, please send a message to d.lloyd at openehr.org
