Dear Paria, Thilo, Koray, Thomas and all. Since Thilo mentions mapping, here is my take...
I know that mind mapping view is available for the archetypes on the openehr site. Ok! I have always wondered about the xml schema used for the conversion from adl to mind map. Since mind maps are useful in capturing clinicians' output during a facilitation session. Is there a reversely engineered xml schema that can automatically convert mind map xml(say generated through Freemind) to the adl? If there is, I will like to have a look and if not how can one be developed. The idea is to abstract away the adl from clinicians and present only the mind maps as representative of the maximum data set of each archetype. The archetypically minded can they use xml schema and the adl to ensure all kinds of other necessary mappings for different interoperabilty requirements and interests. It is important to separate the modelling tool for clinicians (eg mind maps) from that for the 'computerati'(adl, schemas etc) What a clinician group would need to develop new archetypes is the basic knowledge of mind mapping and openehr archetype structures. Thanks. Olusegun Lagos,Nigeria Sent from my BlackBerry wireless device from MTN -----Original Message----- From: "Thilo Schuler" <[email protected]> Date: Fri, 4 Jul 2008 10:41:47 To: For openEHR clinical discussions<openehr-clinical at openehr.org> Subject: Re: Archetyping Methodology Hi P?ria, archetypes model what clinicians would want to record about one discrete clinical idea/concepts. This is done in a maximum dataset fashion (meaning a single clincician would not need certain parts of the archetype) and forms the basis for semantic interoperability. Such archetypes are reused in many different use-cases. So the 'tobacco use' archetype does NOT aim at a certain disease. It should be used e.g. in a template of a lung cancer clinic and in a GP check-up template. This is why the maximum dataset is so important -> the archetype should include what the specialist and what the GP want to record. In the use-case specific template unnecessary archetype parts can be "stripped out". What we did in the MIE session was to start the process of creating an archetype to record a patients tobacco use. Clinicians decide what goes in it (i.e. what they would normally as and note in narrative). Thus it contains statements about relevant past events like 'age commenced' and current facts e.g. 'average daily consumption' or the 'readiness to change the habit' (actually 'change' is another discrete concept and therefore modelled as a reference to another archetype). Here is the current 'tobacco use' archteype (is a specialisation of the more general 'substance use' archetype): http://svn.openehr.org/knowledge/archetypes/dev/html/en/openEHR-EHR-OBSERVATION.substance_use-tobacco.v1draft.html Your approach mentioned below seems reasonable. Step 1 would be the brainstorming (we often do this using mind-mapping software). As you correctly mentioned it is important to use existing archetypes if possible. This modularity and reusability is a strength of openEHR is what we think the main key for semantic interoperability (reusability on a large scale is only possible through the maximum dataset approach!). Hope this helped. Cheers, Thilo On Fri, Jul 4, 2008 at 9:18 AM, P?ria Kashfi <hajar.kashfi at chalmers.se> wrote: > Thank you Heather for the Link and Congrats for the new born website! > As far as I remember form the tutorial session, you-Heather- started > creating an archetype by a brain storming of what any clinician may ask > about smoking or what She may examine during the caring process of a smoker > patient,..., (I'm not sure about the kind of disease we discussed that day > but surely you remember that example) > is it what you-or any other researchers in openEHR area- wanted to show us > or I just understood it the way I am used to! > Actually, I'm really stuck into this kind of thinking about Archetypes and > Templates and maybe it's because of what we have done up to now in our > project creating forms for Clinicians. > Briefly, I can categorize what I have in my mind as the methodology of > creating an application based on openEHR as bellow: > 1- organize number of questions your have in your mind regarding this > disease > 2- Analyze questions to find if there is any scheme for Archetype or > Template in them > 3- Search for existing Archetypes that may fairly act as the basis for > templates you need for this case > 4- Create new Archetypes if needed. > 5- Combine Archetypes and create proper templates > 6- use templates in Application! > Cheers > -Paria > PhD Student > IDC | Interaction Design Collegium > Department of Computing Science and Engineering > Chalmers University of Technology > Email: hajar.kashfi at chalmers.se > Office:+46 (0)31 7725407 > Mobile Phone: +46 (0)707222815 > Postal adress: > IT University of G?teborg > 412 96 G?teborg, Sweden > Visit: Room Simula B, House Svea, Campus Lindholmen > >_______________________________________________ > openEHR-clinical mailing list > openEHR-clinical at openehr.org > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-clinical > _______________________________________________ openEHR-clinical mailing list openEHR-clinical at openehr.org http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-clinical
