On 27-01-18 11:16, Thomas Beale wrote:
Bert,
I don't disagree philosophically, but practically speaking, no SNOMED
service is going to be able to answer requests to do with unit
properties, unit conversions, or different forms of rendering, which
are all things we need to take care of
On 27-01-18 11:10, Bert Verhees wrote:
If one wants an UCUM term in the DvQuantity and another wants a SNOMED
term, it is both legal and possible.
What is preferable, that is not to us to decide while thinking about
OpenEhr.
But having said this
Until now, in practice, people use the
Bert,
I don't disagree philosophically, but practically speaking, no SNOMED
service is going to be able to answer requests to do with unit
properties, unit conversions, or different forms of rendering, which are
all things we need to take care of properly.
I actually think units is one of
On 26-01-18 10:00, Thomas Beale wrote:
The thing I am not a fan of is that units themselves become part of
terminology. This is a SNOMED direction but I think a wrong one. The
reason is that the ontology of units isn't the same as the ontology of
findings, medications and so on. In fact they
Semantic Interoperability is possible only when each. distinct domain:
has its own model
has its own rules
and always orthogonal to other models.
A terminology can be equated to a Dictionary.
A terminology is never an Encyclopedia of everything.
We need a terminology of concepts related to the
5 matches
Mail list logo
