I would like to add bindings in archetypes from SNOMED Clinical Terms,
2006 but it isn't available in the Terminology.xml file, only SNOMED
International Clinical Terms, 2002, which is pretty old. I think the
computable terminology can be improved a lot by adding more
translations etc. It is important for archetype editors and other
openEHR software have a mutual agreement on the meaning of different
openEHR codes and terminologies.
I would like to add bindings in archetypes from SNOMED Clinical Terms,
2006 but it isn't available in the Terminology.xml file, only SNOMED
International Clinical Terms, 2002, which is pretty old.
The list we use of terminologies is an NLM list, and our request to them
is currently outstanding for a definitive up-to-date list. A
human-readable list is at http://www.nlm.nih.gov/research/umls/metaa1.html, you can see that the
id SNOMEDCT_2006_01_31 is included, so we can include this ourselves.
I think the
computable terminology can be improved a lot by adding more
translations etc.
No doubt about that. I will talk with Sam about this.
It is important for archetype editors and other
openEHR software have a mutual agreement on the meaning of different
openEHR codes and terminologies.
I would like to add bindings in archetypes from SNOMED Clinical Terms,
2006 but it isn't available in the Terminology.xml file, only SNOMED
International Clinical Terms, 2002, which is pretty old.
The list we use of terminologies is an NLM list, and our request to them
is currently outstanding for a definitive up-to-date list. A
human-readable list is at http://www.nlm.nih.gov/research/umls/metaa1.html, you can see that the
id SNOMEDCT_2006_01_31 is included, so we can include this ourselves.
I think the
computable terminology can be improved a lot by adding more
translations etc.
No doubt about that. I will talk with Sam about this.
It is important for archetype editors and other
openEHR software have a mutual agreement on the meaning of different
openEHR codes and terminologies.
agree.
Actually I am thinking to include a minimum terminology service
implementation for kernel to work properly. It should at least provides
access to openEHR terminology and iso country, language codes.