Thanks for your reply. I'll check your hints. A more concrete version along the same lines. I have a system developed for the domain of oral medicine during a number of years. During this time the clinicians involved have agreed upon names for various terms (corresponding to node names I believe).
For instance Mucos-txtur denotes the pattern of reaction of the oral mucosa and has a set of possible values defined by the clinicians. On screen Mucos-txtur is not displayed, but a suitable phrase in natural language. When modelling the same information in openEHR I would like to keep the name Mucos-txtur, but if I do that it will be displayed on screen in both the archetype and template editor as the label for the input field. While this can be changed in the template editor it is not really a nice solution. regards Olof 25 nov 2008 kl. 23.53 skrev Ian McNicoll: > Hi Olef, > > The text is the Node name, the Description is simply a more detailed > explanation of the meaning of the node. Further term bindings are > indeed possible... > > In the Archetype Editor, have a look at the Details tab and then at > the "Node meaning in Terminologies". It is possible to bind one or > more external terms to any local term in openEHR- this is a quick > way of binding the node name. > > Also look at the Terminology Tab near the top of the screen, then > Term Bindings, where any local text term can be bound to a single > external term. It is also possible to bid any local term to an > external termset via the Constraints tab. In the absence of any > universally agreed formal method of describing termsets, this > currently uses a descriptive 'placeholder' e.g is_a Cardiac Disease. > > Have a look in the Reference model specification for the DV_TEXT > type for more detailed information on Term binding, constraints > > http://www.openehr.org/releases/1.0.1/architecture/rm/ > data_types_im.pdf > > Cheers, > Ian > > Dr Ian McNicoll > office / fax +44(0)141 560 4657 > mobile +44 (0)775 209 7859 > skype ianmcnicoll > ian at mcmi.co.uk > > Clinical Analyst - Ocean Informatics ian.mcnicoll at oceaninformatics.com > BCS Primary Health Care Specialist Group ? www.phcsg.org > > > 2008/11/25 Olof Torgersson <oloft at chalmers.se> > 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 > > > > > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at openehr.org > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical > > > _______________________________________________ > 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/7dfab4e6/attachment.html>
