Re: Reference Model as Archetypes ?

[Bert Verhees]

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 you mentioned, an 
exported archetype from LinkEHR can be opened in any other archetype 
editor directly. We also gave support for OPT & OET import/export, and 
even OPTs generated this way are virtually identical to the ones 
coming from the template designer.


So yes, we have tweaked the parser to support more things, but the 
archetype creation is completely RM driven (archetypes created with 
LinkEHR are always compliant with the RM you choose). That created 
archetype can be then saved to different representations depending of 
your needs (ADL for specific tools, XML, etc).


Congratulations, I think now nobody has any doubt.

Bert



___
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org

Re: Reference Model as Archetypes ?

[Diego Boscá]

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 used as well, and in future, will probably become
> the main reference tool.
>
> - thomas
>
>
>
> ___
> openEHR-technical mailing list
> openEHR-technical@lists.openehr.org
>
> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
>
___
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org

Re: Reference Model as Archetypes ?

[Diego Boscá]

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 LinkEHR can be opened in any other archetype editor directly. We also
gave support for OPT & OET import/export, and even OPTs generated this way
are virtually identical to the ones coming from the template designer.

So yes, we have tweaked the parser to support more things, but the
archetype creation is completely RM driven (archetypes created with LinkEHR
are always compliant with the RM you choose). That created archetype can be
then saved to different representations depending of your needs (ADL for
specific tools, XML, etc).

Regards

El mié., 12 dic. 2018 15:09, Bert Verhees  escribió:

> 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. There are tools
> > that don't comply with this general ADL, and we provided an export
> > version of archetypes that produces a modified version of the ADL
> > syntax that other older and not maintained tools can parse.
> > If you want to call this subset "official archetypes" be my guest.
>
> The word "official" was used by you, I used it (in quotes) to indicate
> that we refer to the same.
>
> But it may get confusing, also because in the past there were
> discussions about LinkEhr and the Ocean archetype-editor which had
> different interpretations of the prevailing definitions. They did not
> always eat each others archetypes.
>
> I think at this point it is important to state in a simple way, then
> there will be no reason for doubt about intentions:
>
> Does the LinkEhr editor produce archetypes which are always intended to
> be completely conforming the official ADL/AOM and RM definitions?
>
> Best regards
>
> Bert
>
>
>
> ___
> openEHR-technical mailing list
> openEHR-technical@lists.openehr.org
>
> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
>

El mié., 12 dic. 2018 15:09, Bert Verhees  escribió:

> 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. There are tools
> > that don't comply with this general ADL, and we provided an export
> > version of archetypes that produces a modified version of the ADL
> > syntax that other older and not maintained tools can parse.
> > If you want to call this subset "official archetypes" be my guest.
>
> The word "official" was used by you, I used it (in quotes) to indicate
> that we refer to the same.
>
> But it may get confusing, also because in the past there were
> discussions about LinkEhr and the Ocean archetype-editor which had
> different interpretations of the prevailing definitions. They did not
> always eat each others archetypes.
>
> I think at this point it is important to state in a simple way, then
> there will be no reason for doubt about intentions:
>
> Does the LinkEhr editor produce archetypes which are always intended to
> be completely conforming the official ADL/AOM and RM definitions?
>
> Best regards
>
> Bert
>
>
>
> ___
> openEHR-technical mailing list
> openEHR-technical@lists.openehr.org
>
> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
>
___
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org

Re: Reference Model as Archetypes ?

[Thomas Beale]

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



___
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org

Re: Reference Model as Archetypes ?

[Bert Verhees]

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. There are tools 
that don't comply with this general ADL, and we provided an export 
version of archetypes that produces a modified version of the ADL 
syntax that other older and not maintained tools can parse.

If you want to call this subset "official archetypes" be my guest.


The word "official" was used by you, I used it (in quotes) to indicate 
that we refer to the same.


But it may get confusing, also because in the past there were 
discussions about LinkEhr and the Ocean archetype-editor which had 
different interpretations of the prevailing definitions. They did not 
always eat each others archetypes.


I think at this point it is important to state in a simple way, then 
there will be no reason for doubt about intentions:


Does the LinkEhr editor produce archetypes which are always intended to 
be completely conforming the official ADL/AOM and RM definitions?


Best regards

Bert



___
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org

Re: Reference Model as Archetypes ?

[Diego Boscá]

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 general ADL, and we provided an export version of archetypes that
produces a modified version of the ADL syntax that other older and not
maintained tools can parse.
If you want to call this subset "official archetypes" be my guest.


El mié., 12 dic. 2018 a las 14:28, Bert Verhees ()
escribió:

> 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 this
> discussion a few times.
>
> Especially because it is not mentioned on the LinkEhr website that it
> does not support the official OpenEhr out of the box.
>
> You should have an option in the application for creating "official"
> archetypes, this to avoid confusion.
>
> I think it is very good that you fix issues you experience, but this
> way, by implementing without explicit notifying does not seem the royal
> way.
>
> It is bad, because in this way, the OpenEhr-software-ecosystem-base may
> become too narrow, and it is easy to fix by you, as you indicate to
> Georg Fette
>
> Best regards
>
> Bert
>
> ___
> openEHR-technical mailing list
> openEHR-technical@lists.openehr.org
>
> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
>


-- 

[image: VeraTech for Health SL] 

[image: Twitter]   [image: LinkedIn]
 [image: Maps]


Diego Boscá Tomás / Senior developer
diebo...@veratech.es
yamp...@gmail.com

VeraTech for Health SL
+34 654604676 <+34%20654604676>
www.veratech.es

La información contenida en este mensaje y/o archivo(s) adjunto(s), enviada
desde VERATECH FOR HEALTH, SL, es confidencial/privilegiada y está
destinada a ser leída sólo por la(s) persona(s) a la(s) que va dirigida. Le
recordamos que sus datos han sido incorporados en el sistema de tratamiento
de VERATECH FOR HEALTH, SL y que siempre y cuando se cumplan los requisitos
exigidos por la normativa, usted podrá ejercer sus derechos de acceso,
rectificación, limitación de tratamiento, supresión, portabilidad y
oposición/revocación, en los términos que establece la normativa vigente en
materia de protección de datos, dirigiendo su petición a Avda Puerto 237,
1º, pta 1 - 46011 Valencia o bien a través de correo electrónico
d...@veratech.es

Si usted lee este mensaje y no es el destinatario señalado, el empleado o
el agente responsable de entregar el mensaje al destinatario, o ha recibido
esta comunicación por error, le informamos que está totalmente prohibida, y
puede ser ilegal, cualquier divulgación, distribución o reproducción de
esta comunicación, y le rogamos que nos lo notifique inmediatamente y nos
devuelva el mensaje original a la dirección arriba mencionada. Gracias
___
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org

Re: use_node semantics

[Thomas Beale]

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 
.


- thomas

On 12/12/2018 13:13, Georg Fette wrote:

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 create problems when a recursive insertion of the 
referenced branch is inserted, but from a logical point of view is 
that interpretation correct ?
Is an archetype using use_node-branches equivalent to an archetypes in 
which the referenced branch have been explicitely pasted into the 
use_node places ?

Greetings
Georg


--
Thomas Beale
Principal, Ars Semantica 
Consultant, ABD Project, Intermountain Healthcare 

Management Board, Specifications Program Lead, openEHR Foundation 

Chartered IT Professional Fellow, BCS, British Computer Society 

Health IT blog  | Culture blog 
 | The Objective Stance 

___
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org

Re: Reference Model as Archetypes ?

[Bert Verhees]

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 this 
discussion a few times.


Especially because it is not mentioned on the LinkEhr website that it 
does not support the official OpenEhr out of the box.


You should have an option in the application for creating "official" 
archetypes, this to avoid confusion.


I think it is very good that you fix issues you experience, but this 
way, by implementing without explicit notifying does not seem the royal way.


It is bad, because in this way, the OpenEhr-software-ecosystem-base may 
become too narrow, and it is easy to fix by you, as you indicate to 
Georg Fette


Best regards

Bert

___
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org

use_node semantics

[Georg Fette]

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 create problems when a recursive insertion of the referenced 
branch is inserted, but from a logical point of view is that 
interpretation correct ?
Is an archetype using use_node-branches equivalent to an archetypes in 
which the referenced branch have been explicitely pasted into the 
use_node places ?

Greetings
Georg

--
-
Dipl.-Inf. Georg Fette  Raum: B001
Universität WürzburgTel.: +49-(0)931-31-85516
Am Hubland  Fax.: +49-(0)931-31-86732
97074 Würzburg  mail: georg.fe...@uni-wuerzburg.de
-


___
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org

Re: Reference Model as Archetypes ?

[Diego Boscá]

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 (ACTION, CLUSTER, etc.). Are there also somewhere archetypes
> that describe the "Data Types Information Model" (e.g. DV_QUANTITY,
> DV_MEDIA, etc.).
> Greetings
> Georg
>
> --
> -
> Dipl.-Inf. Georg Fette  Raum: B001
> Universität WürzburgTel.: +49-(0)931-31-85516
> Am Hubland  Fax.: +49-(0)931-31-86732
> 97074 Würzburg  mail: georg.fe...@uni-wuerzburg.de
> -
>
>
> ___
> openEHR-technical mailing list
> openEHR-technical@lists.openehr.org
>
> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
>


-- 

[image: VeraTech for Health SL] 

[image: Twitter]   [image: LinkedIn]
 [image: Maps]


Diego Boscá Tomás / Senior developer
diebo...@veratech.es
yamp...@gmail.com

VeraTech for Health SL
+34 654604676 <+34%20654604676>
www.veratech.es

La información contenida en este mensaje y/o archivo(s) adjunto(s), enviada
desde VERATECH FOR HEALTH, SL, es confidencial/privilegiada y está
destinada a ser leída sólo por la(s) persona(s) a la(s) que va dirigida. Le
recordamos que sus datos han sido incorporados en el sistema de tratamiento
de VERATECH FOR HEALTH, SL y que siempre y cuando se cumplan los requisitos
exigidos por la normativa, usted podrá ejercer sus derechos de acceso,
rectificación, limitación de tratamiento, supresión, portabilidad y
oposición/revocación, en los términos que establece la normativa vigente en
materia de protección de datos, dirigiendo su petición a Avda Puerto 237,
1º, pta 1 - 46011 Valencia o bien a través de correo electrónico
d...@veratech.es

Si usted lee este mensaje y no es el destinatario señalado, el empleado o
el agente responsable de entregar el mensaje al destinatario, o ha recibido
esta comunicación por error, le informamos que está totalmente prohibida, y
puede ser ilegal, cualquier divulgación, distribución o reproducción de
esta comunicación, y le rogamos que nos lo notifique inmediatamente y nos
devuelva el mensaje original a la dirección arriba mencionada. Gracias
___
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org

Re: Reference Model as Archetypes ?

[Diego Boscá]

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
> > 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 grammar, which one is the right parser?
>
> Bert
>
>
>
> ___
> openEHR-technical mailing list
> openEHR-technical@lists.openehr.org
>
> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
>


-- 

[image: VeraTech for Health SL] 

[image: Twitter]   [image: LinkedIn]
 [image: Maps]


Diego Boscá Tomás / Senior developer
diebo...@veratech.es
yamp...@gmail.com

VeraTech for Health SL
+34 654604676 <+34%20654604676>
www.veratech.es

La información contenida en este mensaje y/o archivo(s) adjunto(s), enviada
desde VERATECH FOR HEALTH, SL, es confidencial/privilegiada y está
destinada a ser leída sólo por la(s) persona(s) a la(s) que va dirigida. Le
recordamos que sus datos han sido incorporados en el sistema de tratamiento
de VERATECH FOR HEALTH, SL y que siempre y cuando se cumplan los requisitos
exigidos por la normativa, usted podrá ejercer sus derechos de acceso,
rectificación, limitación de tratamiento, supresión, portabilidad y
oposición/revocación, en los términos que establece la normativa vigente en
materia de protección de datos, dirigiendo su petición a Avda Puerto 237,
1º, pta 1 - 46011 Valencia o bien a través de correo electrónico
d...@veratech.es

Si usted lee este mensaje y no es el destinatario señalado, el empleado o
el agente responsable de entregar el mensaje al destinatario, o ha recibido
esta comunicación por error, le informamos que está totalmente prohibida, y
puede ser ilegal, cualquier divulgación, distribución o reproducción de
esta comunicación, y le rogamos que nos lo notifique inmediatamente y nos
devuelva el mensaje original a la dirección arriba mencionada. Gracias
___
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org

Re: Reference Model as Archetypes ?

[Diego Boscá]

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 (<
georg.fe...@uni-wuerzburg.de>) escribió:

> 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 removing all elements that include a recursive
> use_node statement.
> Is the inability to parse use_nodes that reference a node upwards in the
> same branch of the element a bug in version 1.0.71 ?
> Greetings
> Georg
>
> --
> -
> Dipl.-Inf. Georg Fette  Raum: B001
> Universität WürzburgTel.: +49-(0)931-31-85516
> Am Hubland  Fax.: +49-(0)931-31-86732
> 97074 Würzburg  mail: georg.fe...@uni-wuerzburg.de
> -
>
>
> ___
> openEHR-technical mailing list
> openEHR-technical@lists.openehr.org
>
> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
>


-- 

[image: VeraTech for Health SL] 

[image: Twitter]   [image: LinkedIn]
 [image: Maps]


Diego Boscá Tomás / Senior developer
diebo...@veratech.es
yamp...@gmail.com

VeraTech for Health SL
+34 654604676 <+34%20654604676>
www.veratech.es

La información contenida en este mensaje y/o archivo(s) adjunto(s), enviada
desde VERATECH FOR HEALTH, SL, es confidencial/privilegiada y está
destinada a ser leída sólo por la(s) persona(s) a la(s) que va dirigida. Le
recordamos que sus datos han sido incorporados en el sistema de tratamiento
de VERATECH FOR HEALTH, SL y que siempre y cuando se cumplan los requisitos
exigidos por la normativa, usted podrá ejercer sus derechos de acceso,
rectificación, limitación de tratamiento, supresión, portabilidad y
oposición/revocación, en los términos que establece la normativa vigente en
materia de protección de datos, dirigiendo su petición a Avda Puerto 237,
1º, pta 1 - 46011 Valencia o bien a través de correo electrónico
d...@veratech.es

Si usted lee este mensaje y no es el destinatario señalado, el empleado o
el agente responsable de entregar el mensaje al destinatario, o ha recibido
esta comunicación por error, le informamos que está totalmente prohibida, y
puede ser ilegal, cualquier divulgación, distribución o reproducción de
esta comunicación, y le rogamos que nos lo notifique inmediatamente y nos
devuelva el mensaje original a la dirección arriba mencionada. Gracias
___
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org

Re: Reference Model as Archetypes ?

[Georg Fette]

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

--
-
Dipl.-Inf. Georg Fette  Raum: B001
Universität WürzburgTel.: +49-(0)931-31-85516
Am Hubland  Fax.: +49-(0)931-31-86732
97074 Würzburg  mail: georg.fe...@uni-wuerzburg.de
-


___
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org

Re: Reference Model as Archetypes ?

[Bert Verhees]

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 grammar, which one is the right parser?


Bert



___
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org

Re: Reference Model as Archetypes ?

[Georg Fette]

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 
INSTRUCTION_DETAILS.adl file somewhere, which possibly defines something 
that is not yet defined in the ACTION.adl file. Or can be assumed that 
the subclasses wherever they are mentioned are fully desribed at the 
places where they are introduced ?

Greetings
Georg

--
-
Dipl.-Inf. Georg Fette  Raum: B001
Universität WürzburgTel.: +49-(0)931-31-85516
Am Hubland  Fax.: +49-(0)931-31-86732
97074 Würzburg  mail: georg.fe...@uni-wuerzburg.de
-


___
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org

Re: ID namespace for composer and healthcare facility

[Thomas Beale]

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 attribute.


- thomas

On 12/12/2018 11:18, Dileep V S wrote:

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?





___
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org

Re: Reference Model as Archetypes ?

[Georg Fette]

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 removing all elements that include a recursive 
use_node statement.
Is the inability to parse use_nodes that reference a node upwards in the 
same branch of the element a bug in version 1.0.71 ?

Greetings
Georg

--
-
Dipl.-Inf. Georg Fette  Raum: B001
Universität WürzburgTel.: +49-(0)931-31-85516
Am Hubland  Fax.: +49-(0)931-31-86732
97074 Würzburg  mail: georg.fe...@uni-wuerzburg.de
-


___
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org

Re: Reference Model as Archetypes ?

[Diego Boscá]

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 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
>
> --
> -
> Dipl.-Inf. Georg Fette  Raum: B001
> Universität WürzburgTel.: +49-(0)931-31-85516
> Am Hubland  Fax.: +49-(0)931-31-86732
> 97074 Würzburg  mail: georg.fe...@uni-wuerzburg.de
> -
>
>
> ___
> openEHR-technical mailing list
> openEHR-technical@lists.openehr.org
>
> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
>


-- 

[image: VeraTech for Health SL] 

[image: Twitter]   [image: LinkedIn]
 [image: Maps]


Diego Boscá Tomás / Senior developer
diebo...@veratech.es
yamp...@gmail.com

VeraTech for Health SL
+34 654604676 <+34%20654604676>
www.veratech.es

La información contenida en este mensaje y/o archivo(s) adjunto(s), enviada
desde VERATECH FOR HEALTH, SL, es confidencial/privilegiada y está
destinada a ser leída sólo por la(s) persona(s) a la(s) que va dirigida. Le
recordamos que sus datos han sido incorporados en el sistema de tratamiento
de VERATECH FOR HEALTH, SL y que siempre y cuando se cumplan los requisitos
exigidos por la normativa, usted podrá ejercer sus derechos de acceso,
rectificación, limitación de tratamiento, supresión, portabilidad y
oposición/revocación, en los términos que establece la normativa vigente en
materia de protección de datos, dirigiendo su petición a Avda Puerto 237,
1º, pta 1 - 46011 Valencia o bien a través de correo electrónico
d...@veratech.es

Si usted lee este mensaje y no es el destinatario señalado, el empleado o
el agente responsable de entregar el mensaje al destinatario, o ha recibido
esta comunicación por error, le informamos que está totalmente prohibida, y
puede ser ilegal, cualquier divulgación, distribución o reproducción de
esta comunicación, y le rogamos que nos lo notifique inmediatamente y nos
devuelva el mensaje original a la dirección arriba mencionada. Gracias
___
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org

Re: Reference Model as Archetypes ?

[Georg Fette]

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

--
-
Dipl.-Inf. Georg Fette  Raum: B001
Universität WürzburgTel.: +49-(0)931-31-85516
Am Hubland  Fax.: +49-(0)931-31-86732
97074 Würzburg  mail: georg.fe...@uni-wuerzburg.de
-


___
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org

Re: Reference Model as Archetypes ?

[Diego Boscá]

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 they are archetypes from these classes on the demographic
archetypes of CKM, the classes were selected as archetypable in the RM
import process, and thus generated. They should virtually equivalent (apart
from changes in the archetype identifier).



El mié., 12 dic. 2018 a las 12:21, Georg Fette (<
georg.fe...@uni-wuerzburg.de>) escribió:

> 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 archetypes with almost identical content ?
> Greetings
> Georg
>
> --
> -
> Dipl.-Inf. Georg Fette  Raum: B001
> Universität WürzburgTel.: +49-(0)931-31-85516
> Am Hubland  Fax.: +49-(0)931-31-86732
> 97074 Würzburg  mail: georg.fe...@uni-wuerzburg.de
> -
>
>
> ___
> openEHR-technical mailing list
> openEHR-technical@lists.openehr.org
>
> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
>


-- 

[image: VeraTech for Health SL] 

[image: Twitter]   [image: LinkedIn]
 [image: Maps]


Diego Boscá Tomás / Senior developer
diebo...@veratech.es
yamp...@gmail.com

VeraTech for Health SL
+34 654604676 <+34%20654604676>
www.veratech.es

La información contenida en este mensaje y/o archivo(s) adjunto(s), enviada
desde VERATECH FOR HEALTH, SL, es confidencial/privilegiada y está
destinada a ser leída sólo por la(s) persona(s) a la(s) que va dirigida. Le
recordamos que sus datos han sido incorporados en el sistema de tratamiento
de VERATECH FOR HEALTH, SL y que siempre y cuando se cumplan los requisitos
exigidos por la normativa, usted podrá ejercer sus derechos de acceso,
rectificación, limitación de tratamiento, supresión, portabilidad y
oposición/revocación, en los términos que establece la normativa vigente en
materia de protección de datos, dirigiendo su petición a Avda Puerto 237,
1º, pta 1 - 46011 Valencia o bien a través de correo electrónico
d...@veratech.es

Si usted lee este mensaje y no es el destinatario señalado, el empleado o
el agente responsable de entregar el mensaje al destinatario, o ha recibido
esta comunicación por error, le informamos que está totalmente prohibida, y
puede ser ilegal, cualquier divulgación, distribución o reproducción de
esta comunicación, y le rogamos que nos lo notifique inmediatamente y nos
devuelva el mensaje original a la dirección arriba mencionada. Gracias
___
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org

Re: Reference Model as Archetypes ?

[Georg Fette]

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 archetypes with almost identical content ?

Greetings
Georg

--
-
Dipl.-Inf. Georg Fette  Raum: B001
Universität WürzburgTel.: +49-(0)931-31-85516
Am Hubland  Fax.: +49-(0)931-31-86732
97074 Würzburg  mail: georg.fe...@uni-wuerzburg.de
-


___
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org

ID namespace for composer and healthcare facility

[Dileep V S]

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 S
*Founder*
HealtheLife Ventures LLP
m: +91 9632888113
a: 106, Innovation Centre, IIIT, Electronics City, Bangalore 560100
w: healthelife.in  e: dil...@healthelife.in
___
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org