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 the things we should just do properly,
and in only one way for openEHR. I can't imagine why anyone would use
SNOMED for units instead of a proper units service that supported the
above, even if they use SNOMED for everything else. There is of course
nothing preventing anyone adding bindings from SNOMED to the units paths
in archetypes.
- thomas
On 27/01/2018 10:10, Bert Verhees wrote:
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 all have different
ontologies, and trying to jam them all into SNOMED CT under a single
meta- model is problematic at best.
But OpenEhr is a registering system, so if archetypes will be written
to define datasets which use a SNOMED-term, then OpenEhr supports
that, because OpenEhr supports archetypes.
You cannot negate termbindings on AOM/ADL-level in expressing (for
example), we do not accept SNOMED (only UCUM) at this point, it is the
archetype-designer who decides that. I think that is one of the best
features of OpenEhr, the semantic standards are by the user to define.
OpenEhr facilitates. There is the success factor of OpenEhr.
The solution Diego described yesterday works perfect for many point of
views and fits in the OpenEhr paradigms.
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.
Best regards
Bert
_______________________________________________
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
--
Thomas Beale
Principal, Ars Semantica <http://www.arssemantica.com>
Consultant, ABD Team, Intermountain Healthcare
<https://intermountainhealthcare.org/>
Management Board, Specifications Program Lead, openEHR Foundation
<http://www.openehr.org>
Chartered IT Professional Fellow, BCS, British Computer Society
<http://www.bcs.org/category/6044>
Health IT blog <http://wolandscat.net/> | Culture blog
<http://wolandsothercat.net/>
_______________________________________________
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
