"It is still in ADL2, but harmless, so I would leave it in the specs and
advise tool developers to ignore it, if that is the consensus."
That would be my preference. Perhaps add a note to the specs explaining why
it is being deprecated (if others agree).
Ian
Dr Ian McNicoll
mobile +44 (0)775 209
It is still in ADL2, but harmless, so I would leave it in the specs and
advise tool developers to ignore it, if that is the consensus.
- t
On 09/10/2018 06:29, Sebastian Garde wrote:
Assumed value was a slick idea at the time, but I do agree with your
sentiments now:
* it is hardly or n
Assumed value was a slick idea at the time, but I do agree with your sentiments
now:
* it is hardly or not at all processable,
* where there is widespread consensus on something it may well be assumed
automatically by clinicians – but this is not because someone put the assumed
value in
Hi Heather,
Purely technically, I think the answer is "false" - since assumed values are an
available independent of their context (e.g. data or state).
But for all practical modelling I think the answer is "true" - assumed_value
should really be used for protocol/state, but not data.
As for the
4 matches
Mail list logo
