Possible unknown issue with Archetype Editor
Specifications say clearly that a constraint reference is a restriction over primitive strings (5.4.1 'constrains on strings' from ADL specifications). In that case you should put a CODE_PHRASE and then put a constraint reference on the code attribute, as CODE_PHRASE is an object where you provide things as codes and terminology identification. As there is no standard syntax of what the constraint reference query will return you will never know how to parse it directly. 2012/9/14 Ian McNicoll : > Hi Diego, > > I am not sure that I understand your point. A couple of these > archetypes fail the Archetype Workbench parser but this is nothing to > do with the constraint references, which only some of these archetypes > contain. > > The problem that Athanasios has identified is simply that the Ocean > Archetype Editor does not support Demographic archetypes - nice piece > of work for someone to do during a long rainy weekend ;-). > > The 'constraint reference' you mentioned is completely legal ADL and > is agnostic of the underlying RM. > > I agree that the way to go is separate the model and parser and this > is exactly how the new ADL1.5 parser is working but the current Eifell > and Java parsers do support the Demographics model correctly. It is > the Archetype Editor itself that does not support Demographics, not > the underlying parser. > > Ian > > On 13 September 2012 11:06, Diego Bosc? wrote: >> Hello Athanasios, >> >> Those archetypes have parts that do not follow openEHR model. All >> share the same issue, they have a 'constraint reference' inside a >> defining code attribute. The correct is a 'CODE_PHRASE' class. >> I think this is a clear example of why we should keep the model >> outside the parser: This archetype is syntactically valid, but not >> semantically. >> >> Regards >> >> 2012/9/13 Athanasios Anastasiou : >>> Hello everyone >>> >>> Is there a known problem with the following archetypes? >>> openEHR-DEMOGRAPHIC-CLUSTER.individual_credentials_iso.v1 >>> openEHR-DEMOGRAPHIC-CLUSTER.person_additional_data_br.v1 >>> openEHR-DEMOGRAPHIC-CLUSTER.person_birth_data.v1 >>> >>> If not, could there be something with the Archetype Editor? It refuses to >>> load these archetypes properly whether it's from the "Open from web" option >>> or by trying to open an ADL downloaded straight from the CKM. >>> >>> Additional information attached. >>> >>> Looking forward to hearing from you >>> Athanasios Anastasiou >>> >>> >>> ARCHETYPE EDITOR: >>> I wanted to have a look at the Demographic/Address/Address/"Healthcare >>> provider address" archetype and i chose to do it through the Archetype >>> Editor (AE) version 2.2.735 beta to be able to save any modifications i >>> might have wanted to apply. >>> >>> Two versions of the AE gave me the same error: 2.2.3[something] and the >>> latest 2.2.735 beta >>> >>> PROBLEM: >>> *) The AE partially opens a Demographics archetype through the "Open From >>> Web" option >>> *) The AE fails to load a Demographics archetype in ADL format coming from a >>> fresh checkout from the CKM >>> >>> REPLICATING THE PROBLEM: >>> "Open From Web" >>> 1) File -> Open From Web >>> 2) Search: Demographics >>> 3) Select: one of >>> Cluster/[individual_credentials_iso.v1,person_additional_data_br.v1, >>> person_birth_data.v1] >>> 4) OK >>> >>> ERRORS: >>> Incorrect format does not conform to reference model (x7) >>> INFO - Archetype [archetypeID] Semantics VALIDATED >>> (ADL_INTERFACE.parse_archetype) >>> INFO - Archetype [archetypeID] Syntax VALIDATED >>> (ADL_INTERFACE.parse_archetype) >>> >>> "Open from downloaded ADL" >>> 1) Download "individual_credentials_iso.v1" from CKM >>> 1) File-> Open >>> 2) Select: individual_credentials_iso.v1 >>> 3) OK >>> >>> ERRORS: >>> 1) Error loading: ITEM_STRUCTURE = ADDRESS->ITEM_TREE (x2) >>> 2) Loads everything EXCEPT the archetype's definition >>> >>> ___ >>> openEHR-technical mailing list >>> openEHR-technical at lists.openehr.org >>> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org >> >> ___ >> 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 +44 (0)1536 414 994 > fax +44 (0)1536 516317 > mobile +44 (0)775 209 7859 > skype ianmcnicoll > ian.mcnicoll at oceaninformatics.com > > Clinical Modelling Consultant, Ocean Informatics, UK > Director openEHR Foundation www.openehr.org/knowledge > Honorary Senior Research Associate, CHIME, UCL > SCIMP Working Group, NHS Scotland > BCS Primary Health Care www.phcsg.org > > ___ > openEHR-technical mailing list > openEHR-technical at lists.openehr.org > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
Possible unknown issue with Archetype Editor
Hi Diego, I am not sure that I understand your point. A couple of these archetypes fail the Archetype Workbench parser but this is nothing to do with the constraint references, which only some of these archetypes contain. The problem that Athanasios has identified is simply that the Ocean Archetype Editor does not support Demographic archetypes - nice piece of work for someone to do during a long rainy weekend ;-). The 'constraint reference' you mentioned is completely legal ADL and is agnostic of the underlying RM. I agree that the way to go is separate the model and parser and this is exactly how the new ADL1.5 parser is working but the current Eifell and Java parsers do support the Demographics model correctly. It is the Archetype Editor itself that does not support Demographics, not the underlying parser. Ian On 13 September 2012 11:06, Diego Bosc? wrote: > Hello Athanasios, > > Those archetypes have parts that do not follow openEHR model. All > share the same issue, they have a 'constraint reference' inside a > defining code attribute. The correct is a 'CODE_PHRASE' class. > I think this is a clear example of why we should keep the model > outside the parser: This archetype is syntactically valid, but not > semantically. > > Regards > > 2012/9/13 Athanasios Anastasiou : >> Hello everyone >> >> Is there a known problem with the following archetypes? >> openEHR-DEMOGRAPHIC-CLUSTER.individual_credentials_iso.v1 >> openEHR-DEMOGRAPHIC-CLUSTER.person_additional_data_br.v1 >> openEHR-DEMOGRAPHIC-CLUSTER.person_birth_data.v1 >> >> If not, could there be something with the Archetype Editor? It refuses to >> load these archetypes properly whether it's from the "Open from web" option >> or by trying to open an ADL downloaded straight from the CKM. >> >> Additional information attached. >> >> Looking forward to hearing from you >> Athanasios Anastasiou >> >> >> ARCHETYPE EDITOR: >> I wanted to have a look at the Demographic/Address/Address/"Healthcare >> provider address" archetype and i chose to do it through the Archetype >> Editor (AE) version 2.2.735 beta to be able to save any modifications i >> might have wanted to apply. >> >> Two versions of the AE gave me the same error: 2.2.3[something] and the >> latest 2.2.735 beta >> >> PROBLEM: >> *) The AE partially opens a Demographics archetype through the "Open From >> Web" option >> *) The AE fails to load a Demographics archetype in ADL format coming from a >> fresh checkout from the CKM >> >> REPLICATING THE PROBLEM: >> "Open From Web" >> 1) File -> Open From Web >> 2) Search: Demographics >> 3) Select: one of >> Cluster/[individual_credentials_iso.v1,person_additional_data_br.v1, >> person_birth_data.v1] >> 4) OK >> >> ERRORS: >> Incorrect format does not conform to reference model (x7) >> INFO - Archetype [archetypeID] Semantics VALIDATED >> (ADL_INTERFACE.parse_archetype) >> INFO - Archetype [archetypeID] Syntax VALIDATED >> (ADL_INTERFACE.parse_archetype) >> >> "Open from downloaded ADL" >> 1) Download "individual_credentials_iso.v1" from CKM >> 1) File-> Open >> 2) Select: individual_credentials_iso.v1 >> 3) OK >> >> ERRORS: >> 1) Error loading: ITEM_STRUCTURE = ADDRESS->ITEM_TREE (x2) >> 2) Loads everything EXCEPT the archetype's definition >> >> ___ >> openEHR-technical mailing list >> openEHR-technical at lists.openehr.org >> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org > > ___ > 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 +44 (0)1536 414 994 fax +44 (0)1536 516317 mobile +44 (0)775 209 7859 skype ianmcnicoll ian.mcnicoll at oceaninformatics.com Clinical Modelling Consultant, Ocean Informatics, UK Director openEHR Foundation www.openehr.org/knowledge Honorary Senior Research Associate, CHIME, UCL SCIMP Working Group, NHS Scotland BCS Primary Health Care www.phcsg.org
Possible unknown issue with Archetype Editor
Hello Ian Thank you very much for your response. That's good to know also. All the best Athanasios Anastasiou On 13/09/2012 18:56, Ian McNicoll wrote: > Hi Athanasios > > The demographic archetypes were built by Brazilian colleagues who did > some of the editing manually and also made use of the LinkEHR > archetype editor. > > It is actually quite easy to edit the DEMOGRAPHIC Cluster archetypes > in the ocean editor by hacking the archetypeid to EHR-CLUSTER and then > changing it back again after using AE. > > Ian > > Dr Ian McNicoll > Clinical modelling consultant Ocean Informatics > Mobile +44 (0) 775 209 7859 > Skype imcnicoll > > On 13 Sep 2012, at 11:11, Athanasios Anastasiou > wrote: > >> Hello Peter and Diego >> >> Thank you very much for the quick responses. I did briefly go through the >> structures to spot the differences and i am really glad to see that someone >> has already done this :-) >> >> Anyway, i thought that it was strange for these to appear on the CKM without >> loading properly through the AE (otherwise how where they composed?) but >> after the responses it makes sense. >> >> All the best >> Athanasios Anastasiou >> >> >> >> On 13/09/2012 11:06, Peter Gummer wrote: >>> Athanasios Anastasiou wrote: >>> Is there a known problem with the following archetypes? openEHR-DEMOGRAPHIC-CLUSTER.individual_credentials_iso.v1 openEHR-DEMOGRAPHIC-CLUSTER.person_additional_data_br.v1 openEHR-DEMOGRAPHIC-CLUSTER.person_birth_data.v1 If not, could there be something with the Archetype Editor? It refuses to load these archetypes properly whether it's from the "Open from web" option or by trying to open an ADL downloaded straight from the CKM. >>> >>> >>> Hi Athanasios, >>> >>> Definitely a known issue ;-) >>> >>> The Archetype Editor has only ever worked with the openEHR-EHR reference >>> model. It was always planned to add support for openEHR-DEMOGRAPHIC, but >>> improving the support for openEHR-EHR has always been a bigger priority. >>> >>> You would be able to load these archetypes in the ADL Workbench, but it >>> doesn't have editing capability. ADL Workbench can validate the archetypes, >>> however, which is useful if you have edited the ADL in a text editor. >>> >>> Peter >>> >>> >>> ___ >>> openEHR-technical mailing list >>> openEHR-technical at lists.openehr.org >>> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org >>> >> >> ___ >> openEHR-technical mailing list >> openEHR-technical at lists.openehr.org >> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org > > ___ > openEHR-technical mailing list > openEHR-technical at lists.openehr.org > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org >
Possible unknown issue with Archetype Editor
Athanasios Anastasiou wrote: > Is there a known problem with the following archetypes? > openEHR-DEMOGRAPHIC-CLUSTER.individual_credentials_iso.v1 > openEHR-DEMOGRAPHIC-CLUSTER.person_additional_data_br.v1 > openEHR-DEMOGRAPHIC-CLUSTER.person_birth_data.v1 > > If not, could there be something with the Archetype Editor? It refuses to > load these archetypes properly whether it's from the "Open from web" option > or by trying to open an ADL downloaded straight from the CKM. Hi Athanasios, Definitely a known issue ;-) The Archetype Editor has only ever worked with the openEHR-EHR reference model. It was always planned to add support for openEHR-DEMOGRAPHIC, but improving the support for openEHR-EHR has always been a bigger priority. You would be able to load these archetypes in the ADL Workbench, but it doesn't have editing capability. ADL Workbench can validate the archetypes, however, which is useful if you have edited the ADL in a text editor. Peter
Possible unknown issue with Archetype Editor
Hi Athanasios The demographic archetypes were built by Brazilian colleagues who did some of the editing manually and also made use of the LinkEHR archetype editor. It is actually quite easy to edit the DEMOGRAPHIC Cluster archetypes in the ocean editor by hacking the archetypeid to EHR-CLUSTER and then changing it back again after using AE. Ian Dr Ian McNicoll Clinical modelling consultant Ocean Informatics Mobile +44 (0) 775 209 7859 Skype imcnicoll On 13 Sep 2012, at 11:11, Athanasios Anastasiou wrote: > Hello Peter and Diego > > Thank you very much for the quick responses. I did briefly go through the > structures to spot the differences and i am really glad to see that someone > has already done this :-) > > Anyway, i thought that it was strange for these to appear on the CKM without > loading properly through the AE (otherwise how where they composed?) but > after the responses it makes sense. > > All the best > Athanasios Anastasiou > > > > On 13/09/2012 11:06, Peter Gummer wrote: >> Athanasios Anastasiou wrote: >> >>> Is there a known problem with the following archetypes? >>> openEHR-DEMOGRAPHIC-CLUSTER.individual_credentials_iso.v1 >>> openEHR-DEMOGRAPHIC-CLUSTER.person_additional_data_br.v1 >>> openEHR-DEMOGRAPHIC-CLUSTER.person_birth_data.v1 >>> >>> If not, could there be something with the Archetype Editor? It refuses to >>> load these archetypes properly whether it's from the "Open from web" option >>> or by trying to open an ADL downloaded straight from the CKM. >> >> >> Hi Athanasios, >> >> Definitely a known issue ;-) >> >> The Archetype Editor has only ever worked with the openEHR-EHR reference >> model. It was always planned to add support for openEHR-DEMOGRAPHIC, but >> improving the support for openEHR-EHR has always been a bigger priority. >> >> You would be able to load these archetypes in the ADL Workbench, but it >> doesn't have editing capability. ADL Workbench can validate the archetypes, >> however, which is useful if you have edited the ADL in a text editor. >> >> Peter >> >> >> ___ >> openEHR-technical mailing list >> openEHR-technical at lists.openehr.org >> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org >> > > ___ > openEHR-technical mailing list > openEHR-technical at lists.openehr.org > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
Possible unknown issue with Archetype Editor
Hello Athanasios, Those archetypes have parts that do not follow openEHR model. All share the same issue, they have a 'constraint reference' inside a defining code attribute. The correct is a 'CODE_PHRASE' class. I think this is a clear example of why we should keep the model outside the parser: This archetype is syntactically valid, but not semantically. Regards 2012/9/13 Athanasios Anastasiou : > Hello everyone > > Is there a known problem with the following archetypes? > openEHR-DEMOGRAPHIC-CLUSTER.individual_credentials_iso.v1 > openEHR-DEMOGRAPHIC-CLUSTER.person_additional_data_br.v1 > openEHR-DEMOGRAPHIC-CLUSTER.person_birth_data.v1 > > If not, could there be something with the Archetype Editor? It refuses to > load these archetypes properly whether it's from the "Open from web" option > or by trying to open an ADL downloaded straight from the CKM. > > Additional information attached. > > Looking forward to hearing from you > Athanasios Anastasiou > > > ARCHETYPE EDITOR: > I wanted to have a look at the Demographic/Address/Address/"Healthcare > provider address" archetype and i chose to do it through the Archetype > Editor (AE) version 2.2.735 beta to be able to save any modifications i > might have wanted to apply. > > Two versions of the AE gave me the same error: 2.2.3[something] and the > latest 2.2.735 beta > > PROBLEM: > *) The AE partially opens a Demographics archetype through the "Open From > Web" option > *) The AE fails to load a Demographics archetype in ADL format coming from a > fresh checkout from the CKM > > REPLICATING THE PROBLEM: > "Open From Web" > 1) File -> Open From Web > 2) Search: Demographics > 3) Select: one of > Cluster/[individual_credentials_iso.v1,person_additional_data_br.v1, > person_birth_data.v1] > 4) OK > > ERRORS: > Incorrect format does not conform to reference model (x7) > INFO - Archetype [archetypeID] Semantics VALIDATED > (ADL_INTERFACE.parse_archetype) > INFO - Archetype [archetypeID] Syntax VALIDATED > (ADL_INTERFACE.parse_archetype) > > "Open from downloaded ADL" > 1) Download "individual_credentials_iso.v1" from CKM > 1) File-> Open > 2) Select: individual_credentials_iso.v1 > 3) OK > > ERRORS: > 1) Error loading: ITEM_STRUCTURE = ADDRESS->ITEM_TREE (x2) > 2) Loads everything EXCEPT the archetype's definition > > ___ > openEHR-technical mailing list > openEHR-technical at lists.openehr.org > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
Possible unknown issue with Archetype Editor
Hello Peter and Diego Thank you very much for the quick responses. I did briefly go through the structures to spot the differences and i am really glad to see that someone has already done this :-) Anyway, i thought that it was strange for these to appear on the CKM without loading properly through the AE (otherwise how where they composed?) but after the responses it makes sense. All the best Athanasios Anastasiou On 13/09/2012 11:06, Peter Gummer wrote: > Athanasios Anastasiou wrote: > >> Is there a known problem with the following archetypes? >> openEHR-DEMOGRAPHIC-CLUSTER.individual_credentials_iso.v1 >> openEHR-DEMOGRAPHIC-CLUSTER.person_additional_data_br.v1 >> openEHR-DEMOGRAPHIC-CLUSTER.person_birth_data.v1 >> >> If not, could there be something with the Archetype Editor? It refuses to >> load these archetypes properly whether it's from the "Open from web" option >> or by trying to open an ADL downloaded straight from the CKM. > > > Hi Athanasios, > > Definitely a known issue ;-) > > The Archetype Editor has only ever worked with the openEHR-EHR reference > model. It was always planned to add support for openEHR-DEMOGRAPHIC, but > improving the support for openEHR-EHR has always been a bigger priority. > > You would be able to load these archetypes in the ADL Workbench, but it > doesn't have editing capability. ADL Workbench can validate the archetypes, > however, which is useful if you have edited the ADL in a text editor. > > Peter > > > ___ > openEHR-technical mailing list > openEHR-technical at lists.openehr.org > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org >
Possible unknown issue with Archetype Editor
Hello everyone Is there a known problem with the following archetypes? openEHR-DEMOGRAPHIC-CLUSTER.individual_credentials_iso.v1 openEHR-DEMOGRAPHIC-CLUSTER.person_additional_data_br.v1 openEHR-DEMOGRAPHIC-CLUSTER.person_birth_data.v1 If not, could there be something with the Archetype Editor? It refuses to load these archetypes properly whether it's from the "Open from web" option or by trying to open an ADL downloaded straight from the CKM. Additional information attached. Looking forward to hearing from you Athanasios Anastasiou ARCHETYPE EDITOR: I wanted to have a look at the Demographic/Address/Address/"Healthcare provider address" archetype and i chose to do it through the Archetype Editor (AE) version 2.2.735 beta to be able to save any modifications i might have wanted to apply. Two versions of the AE gave me the same error: 2.2.3[something] and the latest 2.2.735 beta PROBLEM: *) The AE partially opens a Demographics archetype through the "Open From Web" option *) The AE fails to load a Demographics archetype in ADL format coming from a fresh checkout from the CKM REPLICATING THE PROBLEM: "Open From Web" 1) File -> Open From Web 2) Search: Demographics 3) Select: one of Cluster/[individual_credentials_iso.v1,person_additional_data_br.v1, person_birth_data.v1] 4) OK ERRORS: Incorrect format does not conform to reference model (x7) INFO - Archetype [archetypeID] Semantics VALIDATED (ADL_INTERFACE.parse_archetype) INFO - Archetype [archetypeID] Syntax VALIDATED (ADL_INTERFACE.parse_archetype) "Open from downloaded ADL" 1) Download "individual_credentials_iso.v1" from CKM 1) File-> Open 2) Select: individual_credentials_iso.v1 3) OK ERRORS: 1) Error loading: ITEM_STRUCTURE = ADDRESS->ITEM_TREE (x2) 2) Loads everything EXCEPT the archetype's definition
