Re: poor version management in archetype editor

[Thomas Beale <thomas.beale@oceaninformatics.com>]

The tool on its own does not do version management - just as Word does 
not version manage the documents you create with it. This is not to say 
that the way revisions and versions are managed inside the tools could 
not be improved, and there is a forthcoming proposal for governance of 
archetypes and template that will deal with these issues. Community 
input will be welcome. This proposal wont change the need for tools like 
Subversion, and will provide guidance on how to use it to support a 
repository of archetypes, and merging archetypes from multiple sources. 
Richard Kavanagh's group have already created a good methodology within 
the NHS and he mentions he would be happy to share it.

- thomas beale


Williamtfgoossen@cs.com wrote:
> Dear all,
>
> Currently underway in making archetypes using the Ocean archetype 
> editor we encounter a major flaw in the tool.
>
> It is impossible to maintain version management, which leads to many 
> inconsistencies in the archetypes.
>
> Also, while participating in the review of archetypes such as blood 
> pressure, the old (before review) and the new (after review) have the 
> same version.
>
> I think this is a very urgent matter to solve, otherwise we will end 
> up with heaps of archetypes on the same subject that are different.
>
> In particular a requirement is that an author, while developing, is 
> able to have a versioning structure that allows going back to earlier 
> versions, or work on improvements while not changing an existing 
> version directly.
>
> In other words: missing versioning is making it hard to produce 
> archetypes.
>
> Sincerely yours,
>
> dr. William TF Goossen
> director
> Results 4 Care b.v.
> De Stinse 15
> 3823 VM Amersfoort
> the Netherlands
> email: Results4Care@cs.com
> phone + 31654614458
> fax +3133 2570169
> www.results4care.nl
> Dutch Chamber of Commerce number: 32133713
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> openEHR-clinical mailing list
> openEHR-clinical@openehr.org
> http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-clinical


--
	*Thomas Beale
Chief Technology Officer, Ocean Informatics 
<http://www.oceaninformatics.com/>*

Chair Architectural Review Board, /open/EHR Foundation 
<http://www.openehr.org/>
Honorary Research Fellow, University College London 
<http://www.chime.ucl.ac.uk/>


*
*