Hi Mikael,
right... but the usual idea is that these codes would be used in a
post-coordinated expression. I think most of those expressions are
problematic as well.
Aside: quite what 'Abuse counselling for non-offending parent
(situation)' is doing there is another question. Or 'Both parents misuse
drugs (situation)'...
But the problem is more widespread than Situation with explicit context.
The 'Qualifier value' hierarchy is also problematic, particularly
'Context values', and the 'Temporal context' sub hierarchy. Having all
this under 'Qualifiers' is an information recording view of things, not
an ontological view. Also terms like 'Current - time specified' don't
really make sense.
'Descriptors' - a huge bag of ontologically different things lumped
together... none of these would be usefully computable as far as I can
see, since they are not connected to meaningful parents.
Then we have 'Record artifact', also informational in nature, and
specifying an ad hoc set of headings. I can't see what use this is.
- thomas
On 29/04/2016 16:37, Mikael Nyström wrote:
Hi,
I can just add that those entities Tom mentions below as
“The waters are muddied further by the attempts to represent
informational, timing and context-related entities in SNOMED CT.”
Are the clearly separated sub-hierarchy called “Situation with
explicit context”
(http://browser.ihtsdotools.org/?perspective=full&conceptId1=243796009&edition=en-edition&release=v20160131&server=http://browser.ihtsdotools.org/api/snomed&langRefset=900000000000509007)
and that sub-hierarch contains only 1 % of the concepts in SNOMED CT.
It is therefore no problem to use SNOMED CT without these concepts for
those who want to do it.
Regards
_______________________________________________
openEHR-technical mailing list
[email protected]
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
