On 02/02/2019 16:21, Pieter Bos wrote:
*From: *openEHR-technical
on behalf of Thomas
Beale
*Reply-To: *For openEHR technical discussions
*Date: *Saturday, 2 February 2019 at 15:01
*To: *"openehr-technical@lists.openehr.org"
*Subject: *Re: Rules in archetypes - what are the
From: openEHR-technical on behalf
of Thomas Beale
Reply-To: For openEHR technical discussions
Date: Saturday, 2 February 2019 at 15:01
To: "openehr-technical@lists.openehr.org"
Subject: Re: Rules in archetypes - what are the requirements?
Assuming you meant to put 'id7' as the first one,
But then you need a second language to define a function to calculate a simple
score. Without it's possible to create tooling to help modelers write at least
simple expressions. basic math and some simple 'if x is between 3 and 10, fill
this field with this value' is entirely doable without
On 02/02/2019 13:15, Ian McNicoll wrote:
Hi Pieter,
"But why would I need a function to calculate a score that is just a
sum of a number of values, instead of a few +-operators?"
It is an open question but one advantage of using the function
approach, with simple values is that it can
On 01/02/2019 14:53, Pieter Bos wrote:
About the calculation:
Ah, I see, the assignment seems like a good solution. But why would I
need a function to calculate a score that is just a sum of a number of
values, instead of a few +-operators?
well you might want to re-use that function.
Hi Pieter,
"But why would I need a function to calculate a score that is just a sum of
a number of values, instead of a few +-operators?"
It is an open question but one advantage of using the function approach,
with simple values is that it can encapsulate the algorithm without too
much
6 matches
Mail list logo
