body { line-height: 1.5; }blockquote { margin-top: 0px; margin-bottom: 0px;
margin-left: 0.5em; }div.foxdiv20140922091633861548 { }body { font-size:
10.5pt; font-family: 'Segoe UI'; color: rgb(0, 0, 0); line-height: 1.5;
}
Hi,The process might depend on the status of the archetype. If the
archetype is in draft, you don't need to change the version, but if all
archetypes are published, the process you propose seems correct.
Pablo Pazoswww.CaboLabs.com
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20140922/7e23e9bf/attachment.html>
-------------- next part --------------
_______________________________________________
openEHR-technical mailing list
openEHR-technical at lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
