Re: About parallel archetype editing

[Sebastian Garde <sebastian.garde@oceaninformatics.com>]

Isn't the convention that in a specialised archetype newly introduced nodes get an at code à la at0.x , e.g. at0.1 for the first?
In specialisation of a specialisation it would be at0.0.1.
For specialisation an existing node at0001 it would be at0001.1, (or at0001.0.1 if it was specialised in a specialiation of an specialised archetype), etc.

With this you don't have to decide on the number of required node codes in the parent in advance.

Cheers
Sebastian


Stef Verlinden wrote:

Maybe it's also a good time (if that wasn't already done:-) to agree on the numbering is AT nodes in locally specialized archetypes.  Ny suggestion is that any specialisation should have an AT node code of 1000 (or even 10.000?) and higher. The point is that if the original archetype evolves in time and we don't do this it could occur that the 'official' AT code number start overlapping with the local specialization AT node codes. Which it that case makes that archetype worthless for local use.

Cheers,

Stef

Op 13 jul 2010, om 07:15 heeft Hugh Leslie het volgende geschreven:

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:

Hi 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

_______________________________________________
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

--
 

Dr Sebastian Garde Senior Developer Ocean Informatics

Dr. sc. hum., Dipl.-Inform. Med, FACHI

Skype: gardeseb

_______________________________________________
openEHR-clinical mailing list
openEHR-clinical@openehr.org
http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-clinical