Hi Jacky, Yes, you are correct. Each specialisation is a separate archetype which has to obey the versioning rules.
If an archetype changes, it must check whether it remains backwardly compatible, irrespective if the change was made in the parent or child, and if the change is a breaking change, a new major version must be created, which I think is exactly what you have suggested. Ian On 22 September 2014 02:17, jacky.lauchunkin at gmail.com < jacky.lauchunkin at gmail.com> wrote: > Dear All, > I met a problem when using specialisation and version. > For example, I have two archetypes, openEHR-DEMOGRAPHIC-PERSON.patient.v1 > and openEHR-DEMOGRAPHIC-PERSON.patient-specialise.v1. Archetype > openEHR-DEMOGRAPHIC-PERSON.patient-specialise.v1 > is specialised from openEHR-DEMOGRAPHIC-PERSON.patient.v1. Let's say the > archetype openEHR-DEMOGRAPHIC-PERSON.patient-specialise.v1 have modified > for several times and its current version is v3. And now > openEHR-DEMOGRAPHIC-PERSON.patient.v1 > has upgraded to version 2, openEHR-DEMOGRAPHIC-PERSON.patient.v2. Can I > simply upgrade openEHR-DEMOGRAPHIC-PERSON.patient-specialise.v3 to > version 4 so that I can change its specilisation to > openEHR-DEMOGRAPHIC-PERSON.patient.v2? > > ------------------------------ > Best wishes? > Jacky.Lau > 2014-09-19 > > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at lists.openehr.org > > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org > -- Dr Ian McNicoll office / fax +44(0)141 560 4657 mobile +44 (0)775 209 7859 skype ianmcnicoll ian at freshehr.com Clinical modelling consultant freshEHR Director openEHR Foundation Honorary Senior Research Associate, CHIME, UCL BCS Primary Health Care www.phcsg.org -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20140922/1cbcef07/attachment.html>
