Rong, thank you for the reference. I've read it, and have more doubts now! The 10.1.3 part is the one that troubles me most because it is more likely to ocurr during initial phases, for example when testing, or worse after initial deployment!
It states: --------------------------------------------------------------------------------------------------------- 10.1.3. New Versions Basic Rule: . new archetype may be neither clean superset or subset; may be incompatible . must supply a conversion argorithm for existing data (equivalent to a viewing algorithm for existing data) ---------------------------------------------------------------------------------------------------------- This algorithm must be added to working code and system must be redeployed? thanks again Rong Chen wrote: >Rodrigo Filgueira wrote: > > >>Let's say I have an archetype being used for some time and it needs to >>be modified in a way that alters paths to inputs. >>I cannot replace the original archetype with the new one because all >>previous data recorded and probably templates created based on the >>original template would stop working. So I would have to keep the old >>one and start work with the second one, and adjust templates or create >>new ones. >> >>In any case it is not clear to me what the full impact of these >>changes would be. >>Is this documented or discussed somewhere? >> >> > >It's mentioned in part 10 of "archetype system" document. > >Cheers, >Rong > > > >>cheers >> >>------------------------------------------------------------------------ >>Rodrigo Filgueira >>Asistente Docente/Investigador >>N?cleo de Ingenier?a Biom?dica, FING - UDELAR >> >> > >_______________________________________________ >openEHR-technical mailing list >openEHR-technical at openehr.org >http://www.chime.ucl.ac.uk/mailman/listinfo/openehr-technical > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20060906/cc3d19ee/attachment.html>
