Re: About parallel archetype editing
Hi Igor
I understand what you mean. There is no simple way to do this - in software development, when you are editing the same segment of code in a group it nearly always comes down to a human making a decision.
The important thing is to have version control in place, so you can roll back if necessary and try to commit often and always get the latest version before you commit anything. What we tend to do in building archetypes is use a higher level tool such as a mindmap editor (see xmind as an example) to agree on the concepts and their relationships and then build the initial archetype which is then about 80% right. Then the archetype will go into the CKM where a group can comment and discuss with only a small number of people (often only one) making the changes as needed. Then there are further review rounds until there is agreement and its published as a version one archetype.
Hope this helps.
regards Hugh
On 13/07/2010 4:38 PM, Игорь Лизунов wrote:My question was about parallel adding of next one field in archetype.
For example, I have an archetype MyArch (cluster) wich contains several items (ELEMENTs) at0001...at0007.
Now I and my colleague need to change this archetype: I need to add new DV_TEXT ELEMENT 'Comments' and my colleague needs to add other field CLUSTER 'Contacts'.
In this case both my and his fields would have same IDs ''at0008". So probably it could be automatically merged to 2 different nodes both with 'at0008' ids ==> error.
So, I need to lock archetype everytime I'm editing it.
2010/7/13 Hugh Leslie <hugh.leslie@oceaninformatics.com>
Hi Igor
The AT codes are ONLY unique within the archetype that they are created in, so AT0001 will appear in every archetype as the root node. Any proper Archetype editor will make sure that when you edit an archetype, that the code in that particular archetype for any element stay the same. If the AT code for an element has to change for any reason, then the Archetype will require a new version and data created with the two archetypes will not be compatible. In general, you don't need to worry about the AT codes as the editors will look after that for you.
When you are working on an archetype in a group (or any other type of model or software artifact) you need to put in place some type of version control system, like you would for any software project that a group was working on, so you are sharing the same models. We have lots of experience with this process if you would like to know more.
Sharing archetypes is what makes openEHR work, and I would definitely encourage you to have a look at the Clinical Knowledge Manager (CKM) at www.openehr.org/knowledge which already has a whole lot of archetypes that you will need for your work. The CKM has version control built in and you will be able to see how archetypes are designed by people who have been doing it for years. While there are no Russian translations that I know of, the archetypes themselves have no primary language and can easily be translated. This means, that a Russian translation can be added to all of the archetypes in the CKM and then the data can be shared even internationally.
regards Hugh Leslie
On 13/07/2010 2:09 PM, Игорь Лизунов wrote:_______________________________________________ openEHR-clinical mailing list openEHR-clinical@openehr.org http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-clinicalHi Everyone!
We've regional openEHR project and now we develop archetypes for our regional repository.
My problem is: archetypes are developed by several organizations in parallel. Because of IDs of archetype nodes are coded with increment numbers like 'atxxxx' parallel editing by two or more people is impossible.
So, how parallel editing is realized in OpenEHR standart or why it is not supported?
Best regards and thank you for your answers
Igor Lizunov
--
________________________________________________
Dr Hugh Leslie MBBS, Dip. Obs. RACOG, FRACGP, FACHI
Clinical Director
Ocean Informatics Pty Ltd
M: +61 404 033 767 E: hugh.leslie@oceaninformatics.com W: www.oceaninformatics.com
_______________________________________________
openEHR-clinical mailing list
openEHR-clinical@openehr.org
http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-clinical
--
С уважением,
Игорь Лизунов
_______________________________________________ openEHR-clinical mailing list openEHR-clinical@openehr.org http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-clinical
--
________________________________________________
Dr Hugh Leslie MBBS, Dip. Obs. RACOG, FRACGP, FACHI
Clinical Director
Ocean Informatics Pty Ltd
M: +61 404 033 767 E: hugh.leslie@oceaninformatics.com W: www.oceaninformatics.com
_______________________________________________
openEHR-clinical mailing list
openEHR-clinical@openehr.org
http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-clinical
_______________________________________________ openEHR-clinical mailing list openEHR-clinical@openehr.org http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-clinical