Rong Chen wrote:
>
>>
>>
>> no you got it right. I have raised a CR in your name (= induction
>> into openEHR hall of fame;-) to make EVENT inherit from LOCATABLE.
>>
>> - thomas
>>
>>
>
> Cool. Where is the CR by the way, I would like to follow it. I saw
> some openehr activities on jira.codeha
Thomas Beale wrote:
> Rong Chen wrote:
>
>> 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 th
Rong Chen wrote:
> 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 i
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 at
ype 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,
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 mode
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
LOCATAB
7 matches
Mail list logo