Hi, Thanks for your reply. I'm aware of the at-codes and that archetypes can (and do) exist in multiple languages.
However, this means that a term/attribute/variable ( or whatever you call the parents of actual data-items) have names like /a/b/c/d[at0033]g/h, which are not understandable for clinicians. Now imagine that you want to analyze some clinical data using Excel, SPSS, or some visual data mining tool. Then one does not want to display at-codes, and displaying the rather descriptive 'text'-phrases is not optimal either. It would be better to have a short agreed upon name. Regards Olof 25 nov 2008 kl. 23.47 skrev Hugh Leslie: > Hi Olof > > This is exactly how openEHR works. If you have a look at the > underlying adl for the archetype you will see that each semantic > element is assigned an 'at' code which is your idea of a language > independent term. The text and the description that is shown in the > tools is actually in a language based ontology section in the adl > and each archetype can have one or more languages in its ontology. > Archetypes themselves have no language primacy and there are now > many archetypes that have multiple languages. > > If you are using the openEHR clinical knowledge manager (at > www.openehr.org/knowledge) > then you can set the language that you want to view the archetype > in. The Ocean archetype editor allows you to view archetypes in > different languages as well and translate the archetypes as I assume > does the Java AE. In the Ocean editor, there is a Language menu > where you can add a new language or select to view one already > present. An example to look at is the Blood Pressure archetype that > already has a number of translations. > > regards Hugh > > Olof Torgersson wrote: >> >> Hi, >> >> In openEHR there are two labels 'text' and 'description' used. >> >> For instance >> >> text = "Increased bowel sounds" >> description="Bowel sounds are more intense than normal" >> >> In the tools I have tested 'text' is used as a label to input fields. >> >> To me it would have been more natural to have 3 items, let's say >> 'term', 'text' and 'description' where term could be some agreed >> upon language independent code and text and description are >> localised into different languages. >> >> I guess this has been considered, but my question then is if >> something like this was considered what were the reasons for >> discarding >> such an approach? >> >> Regards >> >> Olof Torgersson >> >> --- >> Olof Torgersson >> >> Associate Professor >> Department of Computer Science and Engineering >> Chalmers University of Technology and G?teborg University >> SE-412 96 G?teborg, Sweden >> >> email: oloft at chalmers.se >> phone: +46 31 772 54 06 >> >> >> >> >> >> >> __________ Information from ESET NOD32 Antivirus, version of virus >> signature database 3640 (20081125) __________ >> >> The message was checked by ESET NOD32 Antivirus. >> >> http://www.eset.com >> _______________________________________________ >> openEHR-technical mailing list >> openEHR-technical at openehr.org >> http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical >> >> >> >> __________ Information from ESET NOD32 Antivirus, version of virus >> signature database 3640 (20081125) __________ >> >> The message was checked by ESET NOD32 Antivirus. >> >> http://www.eset.com >> > > -- > ________________________________________________ > Dr Hugh Leslie MBBS, Dip. Obs. RACOG, FRACGP, FACHI > Clinical Director > Ocean Informatics Pty Ltd > M: +61 404 033 767 E: hugh.leslie at oceaninformatics.com W: > www.oceaninformatics.com > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at openehr.org > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical --- Olof Torgersson Associate Professor Department of Computer Science and Engineering Chalmers University of Technology and G?teborg University SE-412 96 G?teborg, Sweden email: oloft at chalmers.se phone: +46 31 772 54 06 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20081126/49afc4c9/attachment.html>
