Hi! On 5/22/07, Heather Leslie <heather.leslie at oceaninformatics.biz> wrote: > Perhaps the apparently 'hidden' reference model stuff should perhaps > even be displayed, in an uneditable format, in the Archetype Editor and > Template Designer - to make this design process more transparent and > help bridge the clinical/technical divide just a little.
This very much matches my point of view. Ideally archetype editors etc should be delivered with a built in mini-EHR system for simple testing purposes (security, scalability etc would not be in focus then). I think such a solution will come from somewhere eventually. I'd love provide something like that in the LiU Archetype Editor. I wish we had enough time and resources to implement that, currently we have to focus on other more urgent things. We do have engineering students doing master thesis work around openEHR-based GUIs though and with some luck that might provide some parts of the suggested solution. Best regards, Erik Sundvall http://www.imt.liu.se/~erisu/ Included for more context; On 5/22/07, Heather Leslie <heather.leslie at oceaninformatics.biz> wrote: > From my clinician point of view, the average clinical archetyper can > only imagine that what they see in the archetype will be what can > possibly be displayed on their User Interface. It would be ideal if we > can work to make the 'unseen' magic that comes from the reference model > clearer, as the UML diagram is (almost) totally unintelligible to > others, like me, and even if it can be understood, they may not > neccessarily be able to make the leap from the diagram to how it will > work in practice (ie a UI).
