Sam Heard schreef: > Hi All > > The XML is used for the archetype editor and so has a real GUI use as > well. This is probably not ideal in the long term so we probably need > to separate out the GUI information from the hard openEHR terminology > that is used for processing. For me, the XML has a clear structure, easy to use, and technically well documented. As I understand from these words, this structure can be replaced, and another structure can appear.
As I understand, this means, that terminology.xml in this fashion will not be maintained for sure. Because the OpenEhr terminology is only a very small part of the terminology used in the OpenEhr kernel, it can have its own approach. That was my consideration when choosing to use the XML-file. (Other larger terminologies need possibly another approach depending on how it is available, and how large it is, internal structure, etc. (web-services, imported csv in database).) I am happy, that in my code, I seperated the data-access-methods from the terminology-interface. So if the xml-structure changes, I can switch, or because it is a small file, maintain it myself for my customers, or freeze it. > > I can understand why you want to change the wording to fit with the > technical notions - but the clinicians need to use the editor so the > names are really those that can be understood at the interface level. I now can understand that. I hope, however, the codings belonging tot the rubrics will not change, that is the most important. Because the codes are also documented in the specs and this part of the specs is declared stable in the release candidate 1.0.1, I trust it is safe to use them (mean to say, only very few changes will occur). > > There are a number of translations already in the editor xml file - > the dutch translation needs to be coordinated with Gerard Freriks who > has made a start I believe. I wait for Gerard to deliver the translation. Any idea when this will be? I would like to know because on this depends if I make a temporarily translation for myself, or wait for the one from Gerard. Which, I guess will be much better than the one I would make because of his experience in standardization-processes and his medical education. Thanks for explaining Bert _______________________________________________ openEHR-technical mailing list openEHR-technical at openehr.org http://www.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
