Re: Reference Model as Archetypes ?

On 12-12-18 15:44, Diego Boscá wrote: When I say official I refer to AOM. If AOM/ADL let's you say something we try to support it. We always 'eat' what others tools produce, and have implemented export mechanisms to be compatible with the things other tools can handle. In this particular case

Re: Reference Model as Archetypes ?

We plan in using Archie library when we migrate our tools for ADL2 :) El mié., 12 dic. 2018 15:24, Thomas Beale escribió: > You can always check conformance with the ADL Workbench, it will consume > ADL1.4 and ADL2. And Archie now produces the same regression results as > ADL WB, so it could be

Re: Reference Model as Archetypes ?

When I say official I refer to AOM. If AOM/ADL let's you say something we try to support it. We always 'eat' what others tools produce, and have implemented export mechanisms to be compatible with the things other tools can handle. In this particular case you mentioned, an exported archetype from

Re: Reference Model as Archetypes ?

You can always check conformance with the ADL Workbench, it will consume ADL1.4 and ADL2. And Archie now produces the same regression results as ADL WB, so it could be used as well, and in future, will probably become the main reference tool. - thomas

Re: Reference Model as Archetypes ?

On 12-12-18 14:49, Diego Boscá wrote: These are modifications on the parser, which parses more things than your standard parser. In fact, the editor supports legal things in ADL that other parsers don't (e.g. explicit node identifiers or existence). The generated ADL is completely fine ADL.

Re: Reference Model as Archetypes ?

These are modifications on the parser, which parses more things than your standard parser. In fact, the editor supports legal things in ADL that other parsers don't (e.g. explicit node identifiers or existence). The generated ADL is completely fine ADL. There are tools that don't comply with this

Re: use_node semantics

Hi Georg, the documentation for use_node in ADL2 is here . It applies nearly the same for use_node in ADL1.4, which is specified here

Re: Reference Model as Archetypes ?

On 12-12-18 13:48, Diego Boscá wrote: The official one, these are 'hacks' that allow you to handle requirements and edge cases only present in these RM archetypes Diego, I don't want to be harsh about LinkEhr, which is a very strong product. But this situation raises questions. I already had

use_node semantics

Hello, I am unsure about the semantics of the use_node keyword. Can the archetype branch that is attached at the place where use_node is mentioned be seen like when a preprocessor would paste the part of the referenced branch into the place where use_node is used ? In practice this could

Re: Reference Model as Archetypes ?

I don't think they are currently generated, but you can generate them if you reimport the model and select them El mié., 12 dic. 2018 a las 13:44, Georg Fette (< georg.fe...@uni-wuerzburg.de>) escribió: > Hello, > In the LinkEHR files the archetypes for the "EHR Infomation Model" are > contained

Re: Reference Model as Archetypes ?

The official one, these are 'hacks' that allow you to handle requirements and edge cases only present in these RM archetypes El mié., 12 dic. 2018 a las 13:41, Bert Verhees () escribió: > On 12-12-18 12:53, Diego Boscá wrote: > > We used that one as a basis and generalized mostly to allow the >

Re: Reference Model as Archetypes ?

Grammar (and parser classes) are derived from the original one available in the repo, so the same license applies. These are edge cases we detected the original parser didn't treat well (recursive internal references) and were also fixed. El mié., 12 dic. 2018 a las 13:19, Georg Fette (<

Re: Reference Model as Archetypes ?

Hello, In the LinkEHR files the archetypes for the "EHR Infomation Model" are contained (ACTION, CLUSTER, etc.). Are there also somewhere archetypes that describe the "Data Types Information Model" (e.g. DV_QUANTITY, DV_MEDIA, etc.). Greetings Georg --

Re: Reference Model as Archetypes ?

On 12-12-18 12:53, Diego Boscá wrote: We used that one as a basis and generalized mostly to allow the special RM 'at' codes we created. I can send you the modified grammar or the parser if you want. Wouldn't that disturb interoperability processes? One could wonder: Which one is the right

Re: Reference Model as Archetypes ?

Hi Diego, In the Archetypes contained in the LinkEHR files I am missing the subclasses that are subclassed by the root archetypes. In ACTION for example the subclass INSTRUCTION_DETAILS is used. This is used in the ACTION.adl file and it is parseable but I wonder if there is an

Re: ID namespace for composer and healthcare facility

Hi Dileep, as far as I know, all target OBJECT_IDs of the various concrete types are already globally unique. I suspect the namespace attribute will not be used in the future, or will have just informational value. It would be useful to know what other implementers currently do with this

Re: Reference Model as Archetypes ?

Hi Diego, Yes, if you have a working parser for those archetypes that would be useful. The modified grammer would also be useful. What are the copyright constraints on your parser and your grammmer file ? I managed to get one of the archetypes parsed by lowercasing the language codes and

Re: Reference Model as Archetypes ?

We used that one as a basis and generalized mostly to allow the special RM 'at' codes we created. I can send you the modified grammar or the parser if you want. El mié., 12 dic. 2018 a las 12:46, Georg Fette (< georg.fe...@uni-wuerzburg.de>) escribió: > Hi Diego, > I just tried to parse the .adl

Re: Reference Model as Archetypes ?

Hi Diego, I just tried to parse the .adl files from LinkEHR and got several Exceptions. I currently use the adl-parser from org.openehr.java-libs_v_1.0.71. Which parser can I use to parse those archetypes ? Greetings Georg --

Re: Reference Model as Archetypes ?

They are generated from different "root" XML Schemas (demographics and ehr), but in principle the contents should be the same. Models are generated in a standalone way, so no assumptions are made regarding if ehr model shares classes with demographic one (or any other model already imported). As

Re: Reference Model as Archetypes ?

Hi Diego, Thank you, that is exactly what I was looking for. In the DEMOGRAPHICS and the EHR package there are 6 archetypes which have the same name but differ only in their full path name: CLUSTER, ELEMENT, ITEM_LIST, ITEM_SINGLE, ITEM_TABLE and ITEM_TREE. Why are they two versions of those

ID namespace for composer and healthcare facility

Hi, Compositions require id_namespace for composer and healthcare facility, along with id & id_scheme, to uniquely identify them. How do we ensure universal uniqueness for such name spaces? Is there any central registry where EHR systems are supposed to register their namespaces? regards Dileep V