Problem with version and specialisation

2014-09-22 Thread jacky.lauchun...@gmail.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

Problem with version and specialisation

2014-09-22 Thread pazospa...@hotmail.com
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: #39;Segoe UI#39;; color: rgb(0, 0, 0); line-height: 1.5; } Hi,The process might depend on the status of the

Problem with version and specialisation

2014-09-22 Thread Sam Heard
Subject: Problem with version and specialisation 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

Problem with version and specialisation

2014-09-22 Thread Ian McNicoll
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,