Thanks Olef, That is very helpful. Would it be possible to send a further screenshot showing the bottom half of the screen - I would like to try and work up an example of archetyping and templating the whole form, if possible. Is this for general inspection of the oral mucosa or for a particular lesion?
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 Member of BCS Primary Health Care Specialist Group ? www.phcsg.org 2008/11/26 Olof Torgersson <oloft at chalmers.se> > The data comes from an electronic patient record. I attach two examples of > screens generated from the same xml-template specification in our formalism, > one is a java desktop application and the other a web interface. One of the > interfaces displays short term names the other doesn'tI also attach an > example from visual data analysis.Olof > > > 26 nov 2008 kl. 13.30 skrev Ian McNicoll: > > Does the data originally come directly from an electronic patient record or > are the clinicians entering the data at a later stage purely for analysis > purposes > > Can you email me a sample of a data collection form or screenshot so I can > get a better idea of the process? I am not sure if this list will accept > attachments - if not you can email me directly. > > 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 > > Member of BCS Primary Health Care Specialist Group ? www.phcsg.org > > > 2008/11/26 Olof Torgersson <oloft at chalmers.se> > >> Hi, >> Thanks for your reply. >> >> To explain further, our clinicians are used to working with data in >> Excel/SPSS and our own visual data mining tool. >> >> Then they compare values for different patient groups for >> terms/attributes/variables like Mucos-txtur. >> >> Displaying real names of nodes like >> /a/b/c/d[at0033]g/h, would not be understandable for clinicians. >> Displaying the rather descriptive phrases used for 'text', like >> 'Reaction pattern of the oral mucosa' would not be good either. A short >> agreed upon would be better. >> >> I have not yet been able to investigate if what you suggest is possible to >> achieve >> >> Regards >> >> Olof >> 26 nov 2008 kl. 01.43 skrev Ian McNicoll: >> >> Hi Olef, >> >> I would regard 'Mucos-txtur 'as part of a local terminology and the best >> way to handle it would be by binding this code to the natural language term >> of the archetype node name.. i.e 'Mucosal Reaction'->Mucos-txtur. >> >> I am not sure of the technical/governance arrangements for using such >> local terminologies with openEHR - can anyone advise? >> >> 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 >> >> Member of BCS Primary Health Care Specialist Group ? www.phcsg.org >> >> >> 2008/11/25 Olof Torgersson <oloft at chalmers.se> >> >>> 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 >>> >>> >>> >>> >>> >>> _______________________________________________ >>> 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 >> >> >> >> >> >> _______________________________________________ >> 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/9b03f703/attachment.html>
