A few weeks ago some of us had a look at the openEHR terminology, and identified some of the problems on this wiki page <http://www.openehr.org/wiki/display/spec/openEHR+Terminology>. One of the (obvious) conclusions was that the Archetype Editor 'terminology' needs to be its own thing, since it is full of GUI terms. The rest of the terminology (derived from the openEHR Terminology spec) needs to be treated differently.
In the long term, some of it might be replaced by SNOMED CT terms for some of the things like 'participation types'; some of it will remain, and would go into an openEHR SNOMED CT extension. In the shorter term we have to be more pragmatic, and the obvious approach seems to be to start from the Java project version of the terminology files, now located in the knowledge2 repository <http://www.openehr.org/svn/knowledge2/TRUNK/terminology/>. On inspection of these, there are some obvious errors and shortcomings, notably a new 'multimedia types' group in the openEHR terminologies containing extra IANA media types (aka MIME types) that should have gone into the IANA media types codeset in the other file. We need to address these problems ASAP, and I think that can be done simply. We also need to decide on the file format, and translation approach. The wiki page gives some ideas on this. The Archetype Editor should therefore start using these standard files for the main openEHR vocabularies and codesets, and limit the contents of its own terminology to its own (localisable) UI strings & error messages, as for any normal application. This probably should morph into the standard i18n format for Microsoft applications, rather than maintaining its own form. - thomas On 24/06/2012 10:09, Peter Gummer wrote: > pablo pazos wrote: > >> I have some proposals that might improve some aspects of the AE: >> ... >> - the translation is very poor, how can I translate the GUI terms? > That would be great, Pablo. > > Under the directory where Archetype Editor is installed, there's a directory > called "Terminology". You can edit the terminology.xml that you find there. > It's pretty straightforward to edit the XML directly, but there's a program > called openEHR_Translation.exe in the same directory which you'll probably > find makes it easier. > > If you send me your improved copy of terminology.xml, I'll commit your > changes to the Archetype Editor Subversion repository. > > >> - is there some way to do a search on the AE GUI that consumes a search >> service on the CKM to find, download and edit/specialize archetypes from the >> CKM directly from the AE? > In the Tools | Options dialog, select the File Locations tab. Turn on the > "Enable Internet Search" check box. (The URL should be > http://openehr.org/knowledge/services/ArchetypeFinderBean?wsdl) > > Then, under the File menu, you'll see an option to "Open from Web?" This > allows you to get archetypes directly from CKM. > > Peter > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at lists.openehr.org > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org > * * -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20120624/e32df1a4/attachment-0001.html>
