Part two is of course, generating templates, and we almost have the
GUI's in place.
It is the enormous collection of medical datastructures which can be the
source of many generated EPD-software.
Bert
On 29-04-16 08:50, Bert Verhees wrote:
Hi,
I got an idea when reading the nice story from Heather on LinkedIn. In
fact it is hers idea, but in a opposing way.
https://www.linkedin.com/pulse/journey-interoperability-part-i-heather-leslie
https://www.linkedin.com/pulse/journey-interoperability-part-ii-heather-leslie
I wonder in how far it is feasible and useful to create archetypes
from SNOMED concepts, it would be possible to generate them, with
attributes and so on.
In a few hours time, one would have a complete forest with archetypes,
including ontology in more languages.
Maybe some smart handling, filtering, combining can create a better
collection, also looking at the paths, so that there are similar paths
for similar situations, to keep the number of different datapoints
low, which can help creating a faster key-value storage.
I don't know how it is about copyright, with members, and licensing,
that should be looked at.
The argument that SNOMED is fragmented should not count, I think
(however without having an expertise on this), because, when working
with handwritten archetypes will always be incomplete and fragmented.
Bert
_______________________________________________
openEHR-technical mailing list
[email protected]
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
