On 29-04-16 18:02, Ian McNicoll wrote:
Hi Bert,
"I think that every leaf-node in an Archetype can be encoded in
SNOMED, don't you think?"
I'm afraid not even close, especially when you take into account the
changes in the meaning of datapoints that apply when used in differing
contexts. When doing modelling for histopathologym I was not even
close to getting 50% binding of SNOMED to archetype leaf-nodes, ands
histopath is one of the better covered parts.
Leaf-node datapoints should not have much context. Like observable items
like Body Temperature, it should be there as a lego brick, and receive
its context where used in an archetype, but this is a simple item. The
problem is of course that there is need for complex structures like
there probably are for histopathologym
So I agree that SNOMED is not fit for the purpose I made up. It is far
from complete, and it has another purpose. I am convinced by now.
That is too bad. It seemed like some elegant idea, generating archetypes
from a hierarchical collection which contains very many connected
datapoints, like SNOMED does. So I think the collection needs another
purpose to start off with. Dedicated to archetype-leafnodes, with
according paths.
I wonder, would it be possible to generate a subset of SNOMED which
would be usable for archetypes?
Or is it a future plan from IHTSDO to work on such a refset?
These questions may be understood as rhetorical.
Thanks
Bert
_______________________________________________
openEHR-technical mailing list
[email protected]
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
