subject:"Extract archetypes"

Re: Extract archetypes

2017-11-30 Thread Thomas Beale

Note that for class and property names, we tend to stick to typical 
programming convantions, which is


 * class - first letter capital
 * property / method name - first letter lower-case

One reason to do this is to be able to distinguish a class name on its 
own, e.g. in an ADL archetype, and not mix it up with a property name. 
The ADL workbench does this, and  I would argue we want to keep these rules.


Nothing is ever completely simple...

- thomas


On 30/11/2017 15:01, Pieter Bos wrote:

I agree about the case insensitivity. Archie still does this case sensitive, so 
I just created https://github.com/openEHR/archie/issues/8 (

Pieter

On 30/11/2017, 15:23, "openEHR-technical on behalf of Thomas Beale" 
 wrote:

 
 I think the string matching should be case-insensitive, and the current

 regexes allow for any case. Various tools implementers would need to
 check to see if their tools match 'ehr_extract' to 'EHR_EXTRACT' etc.
 
 - thomas
 
 
 On 30/11/2017 13:55, Bert Verhees wrote:

 > So, there are also considerations I did not see.
 >
 > I can live a few days more without having a definite policy ;-)
 > But the classes are there and people will want to use them.
 >
 > I think Thomas proposal is in line with the other rmNames, like EHR
 > and DEMOGRAPHIC (which are capitalized), and therefor indeed
 > EHR_EXTRACT seems to me the best solution. Sorry for agreeing with
 > previous suggestions.
 >
 > 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



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

Management Board, Specifications Program Lead, openEHR Foundation 

Chartered IT Professional Fellow, BCS, British Computer Society 

Health IT blog  | Culture blog 

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

Re: Extract archetypes

2017-11-30 Thread Pieter Bos

I agree about the case insensitivity. Archie still does this case sensitive, so 
I just created https://github.com/openEHR/archie/issues/8 (

Pieter

On 30/11/2017, 15:23, "openEHR-technical on behalf of Thomas Beale" 
 wrote:

I think the string matching should be case-insensitive, and the current 
regexes allow for any case. Various tools implementers would need to 
check to see if their tools match 'ehr_extract' to 'EHR_EXTRACT' etc.

- thomas

On 30/11/2017 13:55, Bert Verhees wrote:
> So, there are also considerations I did not see.
>
> I can live a few days more without having a definite policy ;-)
> But the classes are there and people will want to use them.
>
> I think Thomas proposal is in line with the other rmNames, like EHR 
> and DEMOGRAPHIC (which are capitalized), and therefor indeed 
> EHR_EXTRACT seems to me the best solution. Sorry for agreeing with 
> previous suggestions.
>
> 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: Extract archetypes

2017-11-30 Thread Bert Verhees


On 30-11-17 15:23, Thomas Beale wrote:


I think the string matching should be case-insensitive, and the 
current regexes allow for any case. Various tools implementers would 
need to check to see if their tools match 'ehr_extract' to 
'EHR_EXTRACT' etc.


This is like Diego and Pieter also suggested.
Okay, thanks.



- thomas


On 30/11/2017 13:55, Bert Verhees wrote:

So, there are also considerations I did not see.

I can live a few days more without having a definite policy ;-)
But the classes are there and people will want to use them.

I think Thomas proposal is in line with the other rmNames, like EHR 
and DEMOGRAPHIC (which are capitalized), and therefor indeed 
EHR_EXTRACT seems to me the best solution. Sorry for agreeing with 
previous suggestions.


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: Extract archetypes

2017-11-30 Thread Thomas Beale



I think the string matching should be case-insensitive, and the current 
regexes allow for any case. Various tools implementers would need to 
check to see if their tools match 'ehr_extract' to 'EHR_EXTRACT' etc.


- thomas


On 30/11/2017 13:55, Bert Verhees wrote:

So, there are also considerations I did not see.

I can live a few days more without having a definite policy ;-)
But the classes are there and people will want to use them.

I think Thomas proposal is in line with the other rmNames, like EHR 
and DEMOGRAPHIC (which are capitalized), and therefor indeed 
EHR_EXTRACT seems to me the best solution. Sorry for agreeing with 
previous suggestions.


Bert



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

Re: Extract archetypes

2017-11-30 Thread Bert Verhees


So, there are also considerations I did not see.

I can live a few days more without having a definite policy ;-)
But the classes are there and people will want to use them.

I think Thomas proposal is in line with the other rmNames, like EHR and 
DEMOGRAPHIC (which are capitalized), and therefor indeed EHR_EXTRACT 
seems to me the best solution. Sorry for agreeing with previous suggestions.


Bert


On 30-11-17 14:40, Thomas Beale wrote:


The ADL 1.4 identifier syntax is here 
, 
and permits underscores. The ADL2 syntax for the type ARCHETYPE_HRID I 
think is not visible anywhere except code, so we'll need to remedy 
that. The relevant code 
 
shows that underscores are accepted as well.


I would suggest using the proper specification name as various tools 
are starting to depend on consistent use of names across 
specifications, UML packages and classes, and archetypes. In fact I 
suspect that right now the ADL Workbench would not recognise an 
Extract archetype that didn't have EHR_EXTRACT as the RM class 
qualifier, because the relevant BMM 
 
is named that way (I haven't checked though).


I would go with the id template 
openEHR-EHR_EXTRACT-EXTRACT.something.v1.0.0. There are examples 
 
already of this in the archetype test repo.


- thomas


On 30/11/2017 12:09, Bert Verhees wrote:

On 30-11-17 13:06, Diego Boscá wrote:
Having said that, I'm not sure current regex for archetype ids 
allows the use of spaces or undescores on the rm part. I'll have to 
check that


I was too fast with my compliments ;-)
In that case, we can leave the underscore out, It remains readable.

Bert



2017-11-30 9:04 GMT-03:00 Diego Boscá >:


Hi Bert,

I would say that the "rm name" would be "EHR_Extract", as it is
the way the package is called in the documentation
http://www.openehr.org/releases/RM/latest/docs/ehr_extract/ehr_extract.html


(notice that demographics and EHR are the other package names).

After that you would put the corresponding class name to constraint

Regards

2017-11-30 8:55 GMT-03:00 Bert Verhees >:

Hi,


Since that it is so that some extract-classes derive from
Locatable, they can be used to use them as RM-class for an
archetype-definition.

But how would the ArchetypeId look like, special the rmName.
Would it be something like openEHR-Extract-Extract ?

Thanks in advance for answering

Bert


___
openEHR-technical mailing list
openEHR-technical@lists.openehr.org


http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org






-- 


VeraTech for Health SL 

Twitter LinkedIn
Maps


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

VeraTech for Health SL
+34 961071863  / +34 627015023

www.veratech.es 

Su dirección de correo electrónico junto a sus datos personales
forman parte de un fichero titularidad de VeraTech for Health SL
(CIF B98309511) cuya finalidad es la de mantener el contacto con
usted. Conforme a La Ley Orgánica 15/1999, usted puede ejercitar
sus derechos de acceso, rectificación, cancelación y, en su caso
oposición, enviando una solicitud por escrito a
verat...@veratech.es .




--

VeraTech for Health SL 

Twitter LinkedIn 
Maps 



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

VeraTech for Health SL
+34 961071863  / +34 627015023 


www.veratech.es 

Su dirección de correo electrónico junto a sus datos personales

Re: Extract archetypes

2017-11-30 Thread Thomas Beale

I spoke too fast - the ARCHETYPE_HRID syntax is specified here in the 
Archetype Identification spec. 




On 30/11/2017 13:40, Thomas Beale wrote:


The ADL 1.4 identifier syntax is here 
, 
and permits underscores. The ADL2 syntax for the type ARCHETYPE_HRID I 
think is not visible anywhere except code, so we'll need to remedy 
that. The relevant code 
 
shows that underscores are accepted as well.


I would suggest using the proper specification name as various tools 
are starting to depend on consistent use of names across 
specifications, UML packages and classes, and archetypes. In fact I 
suspect that right now the ADL Workbench would not recognise an 
Extract archetype that didn't have EHR_EXTRACT as the RM class 
qualifier, because the relevant BMM 
 
is named that way (I haven't checked though).


I would go with the id template 
openEHR-EHR_EXTRACT-EXTRACT.something.v1.0.0. There are examples 
 
already of this in the archetype test repo.


- thomas



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

Re: Extract archetypes

2017-11-30 Thread Thomas Beale

The ADL 1.4 identifier syntax is here 
, 
and permits underscores. The ADL2 syntax for the type ARCHETYPE_HRID I 
think is not visible anywhere except code, so we'll need to remedy that. 
The relevant code 
 
shows that underscores are accepted as well.


I would suggest using the proper specification name as various tools are 
starting to depend on consistent use of names across specifications, UML 
packages and classes, and archetypes. In fact I suspect that right now 
the ADL Workbench would not recognise an Extract archetype that didn't 
have EHR_EXTRACT as the RM class qualifier, because the relevant BMM 
 
is named that way (I haven't checked though).


I would go with the id template 
openEHR-EHR_EXTRACT-EXTRACT.something.v1.0.0. There are examples 
 
already of this in the archetype test repo.


- thomas


On 30/11/2017 12:09, Bert Verhees wrote:

On 30-11-17 13:06, Diego Boscá wrote:
Having said that, I'm not sure current regex for archetype ids allows 
the use of spaces or undescores on the rm part. I'll have to check that


I was too fast with my compliments ;-)
In that case, we can leave the underscore out, It remains readable.

Bert



2017-11-30 9:04 GMT-03:00 Diego Boscá >:


Hi Bert,

I would say that the "rm name" would be "EHR_Extract", as it is
the way the package is called in the documentation
http://www.openehr.org/releases/RM/latest/docs/ehr_extract/ehr_extract.html


(notice that demographics and EHR are the other package names).

After that you would put the corresponding class name to constraint

Regards

2017-11-30 8:55 GMT-03:00 Bert Verhees >:

Hi,


Since that it is so that some extract-classes derive from
Locatable, they can be used to use them as RM-class for an
archetype-definition.

But how would the ArchetypeId look like, special the rmName.
Would it be something like openEHR-Extract-Extract ?

Thanks in advance for answering

Bert


___
openEHR-technical mailing list
openEHR-technical@lists.openehr.org


http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org






-- 


VeraTech for Health SL 

Twitter LinkedIn
Maps


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

VeraTech for Health SL
+34 961071863  / +34 627015023

www.veratech.es 

Su dirección de correo electrónico junto a sus datos personales
forman parte de un fichero titularidad de VeraTech for Health SL
(CIF B98309511) cuya finalidad es la de mantener el contacto con
usted. Conforme a La Ley Orgánica 15/1999, usted puede ejercitar
sus derechos de acceso, rectificación, cancelación y, en su caso
oposición, enviando una solicitud por escrito a
verat...@veratech.es .




--

VeraTech for Health SL 

Twitter LinkedIn 
Maps 



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

VeraTech for Health SL
+34 961071863  / +34 627015023 


www.veratech.es 

Su dirección de correo electrónico junto a sus datos personales 
forman parte de un fichero titularidad de VeraTech for Health SL (CIF 
B98309511) cuya finalidad es la de mantener el contacto con usted. 
Conforme a La Ley Orgánica 15/1999, usted puede ejercitar sus 
derechos de acceso, rectificación, cancelación y, en su caso 
oposición, enviando una solicitud por escrito a verat...@veratech.es 
.




___
openEHR-technical mailing list

Re: Extract archetypes

2017-11-30 Thread Bert Verhees


On 30-11-17 13:11, Diego Boscá wrote:

underscore it is then! :D


Quick and firm

No objections

Bert



2017-11-30 9:09 GMT-03:00 Pieter Bos <pieter@nedap.com 
<mailto:pieter@nedap.com>>:


The test package is called “test_pkg” at least in adl2 – so
underscores are supported.

Pieter

From: openEHR-technical
<openehr-technical-boun...@lists.openehr.org
<mailto:openehr-technical-boun...@lists.openehr.org>> on behalf of
Diego Boscá <yamp...@gmail.com <mailto:yamp...@gmail.com>>
Reply-To: For openEHR technical discussions
<openehr-technical@lists.openehr.org
<mailto:openehr-technical@lists.openehr.org>>
Date: Thursday, 30 November 2017 at 13:06
To: For openEHR technical discussions
<openehr-technical@lists.openehr.org
<mailto:openehr-technical@lists.openehr.org>>
Subject: Re: Extract archetypes

Having said that, I'm not sure current regex for archetype ids
allows the use of spaces or undescores on the rm part. I'll have
to check that

2017-11-30 9:04 GMT-03:00 Diego Boscá <yamp...@gmail.com
<mailto:yamp...@gmail.com><mailto:yamp...@gmail.com
<mailto:yamp...@gmail.com>>>:
Hi Bert,
I would say that the "rm name" would be "EHR_Extract", as it is
the way the package is called in the documentation
http://www.openehr.org/releases/RM/latest/docs/ehr_extract/ehr_extract.html

<http://www.openehr.org/releases/RM/latest/docs/ehr_extract/ehr_extract.html>
(notice that demographics and EHR are the other package names).
After that you would put the corresponding class name to constraint
Regards

2017-11-30 8:55 GMT-03:00 Bert Verhees <bert.verh...@rosa.nl
<mailto:bert.verh...@rosa.nl><mailto:bert.verh...@rosa.nl
<mailto:bert.verh...@rosa.nl>>>:
Hi,


Since that it is so that some extract-classes derive from
Locatable, they can be used to use them as RM-class for an
archetype-definition.

But how would the ArchetypeId look like, special the rmName. Would
it be something like openEHR-Extract-Extract ?

Thanks in advance for answering

Bert


___
openEHR-technical mailing list
openEHR-technical@lists.openehr.org

<mailto:openEHR-technical@lists.openehr.org><mailto:openEHR-technical@lists.openehr.org
<mailto:openEHR-technical@lists.openehr.org>>

http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org

<http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org>


--

[eraTech for Health SL]<https://htmlsig.com/t/01C268PZ
<https://htmlsig.com/t/01C268PZ>>

[witter] <https://htmlsig.com/t/01C47QQH
<https://htmlsig.com/t/01C47QQH>> [inkedIn] 
<https://htmlsig.com/t/01C4DPJG
<https://htmlsig.com/t/01C4DPJG>> [aps] 
<https://htmlsig.com/t/01BZTWS7

<https://htmlsig.com/t/01BZTWS7>>
[https://s3.amazonaws.com/htmlsig-assets/spacer.gif
<https://s3.amazonaws.com/htmlsig-assets/spacer.gif>]

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

VeraTech for Health SL
+34 961071863
<tel:%2B34%20961071863><tel:+34%20961%2007%2018%2063> / +34
627015023 <tel:%2B34%20627015023><tel:+34%20627%2001%2050%2023>
www.veratech.es <http://www.veratech.es><http://www.veratech.es/
<http://www.veratech.es/>>

Su dirección de correo electrónico junto a sus datos personales
forman parte de un fichero titularidad de VeraTech for Health SL
(CIF B98309511) cuya finalidad es la de mantener el contacto con
usted. Conforme a La Ley Orgánica 15/1999, usted puede ejercitar
sus derechos de acceso, rectificación, cancelación y, en su caso
oposición, enviando una solicitud por escrito a
verat...@veratech.es
<mailto:verat...@veratech.es><mailto:verat...@veratech.es
<mailto:verat...@veratech.es>>.



--

[eraTech for Health SL]<https://htmlsig.com/t/01C268PZ
<https://htmlsig.com/t/01C268PZ>>

[witter] <https://htmlsig.com/t/01C47QQH
<https://htmlsig.com/t/01C47QQH>> [inkedIn] 
<https://htmlsig.com/t/01C4DPJG
<https://htmlsig.com/t/01C4DPJG>> [aps] 
<https://htmlsig.com/t/01BZTWS7

<https://htmlsig.com/t/01BZTWS7>>
[https://s3.amazonaws.com/htmlsig-assets/spacer.gif
<https://s3.amazonaws.com/htm

Re: Extract archetypes

2017-11-30 Thread Diego Boscá

underscore it is then! :D

2017-11-30 9:09 GMT-03:00 Pieter Bos <pieter@nedap.com>:

> The test package is called “test_pkg” at least in adl2 – so underscores
> are supported.
>
> Pieter
>
> From: openEHR-technical <openehr-technical-boun...@lists.openehr.org> on
> behalf of Diego Boscá <yamp...@gmail.com>
> Reply-To: For openEHR technical discussions <openehr-technical@lists.
> openehr.org>
> Date: Thursday, 30 November 2017 at 13:06
> To: For openEHR technical discussions <openehr-technical@lists.openehr.org
> >
> Subject: Re: Extract archetypes
>
> Having said that, I'm not sure current regex for archetype ids allows the
> use of spaces or undescores on the rm part. I'll have to check that
>
> 2017-11-30 9:04 GMT-03:00 Diego Boscá <yamp...@gmail.com<mailto:yamp
> e...@gmail.com>>:
> Hi Bert,
> I would say that the "rm name" would be "EHR_Extract", as it is the way
> the package is called in the documentation http://www.openehr.org/
> releases/RM/latest/docs/ehr_extract/ehr_extract.html (notice that
> demographics and EHR are the other package names).
> After that you would put the corresponding class name to constraint
> Regards
>
> 2017-11-30 8:55 GMT-03:00 Bert Verhees <bert.verh...@rosa.nl ert.verh...@rosa.nl>>:
> Hi,
>
>
> Since that it is so that some extract-classes derive from Locatable, they
> can be used to use them as RM-class for an archetype-definition.
>
> But how would the ArchetypeId look like, special the rmName. Would it be
> something like openEHR-Extract-Extract ?
>
> Thanks in advance for answering
>
> Bert
>
>
> ___
> openEHR-technical mailing list
> openEHR-technical@lists.openehr.org<mailto:openEHR-
> techni...@lists.openehr.org>
> http://lists.openehr.org/mailman/listinfo/openehr-
> technical_lists.openehr.org
>
>
> --
>
> [eraTech for Health SL]<https://htmlsig.com/t/01C268PZ>
>
> [witter] <https://htmlsig.com/t/01C47QQH>  [inkedIn]  <
> https://htmlsig.com/t/01C4DPJG>  [aps]  <https://htmlsig.com/t/
> 01BZTWS7>
> [https://s3.amazonaws.com/htmlsig-assets/spacer.gif]
>
> Diego Boscá Tomás / Senior developer
> diebo...@veratech.es<mailto:diebo...@veratech.es>
> yamp...@gmail.com<mailto:yamp...@gmail.com>
>
> VeraTech for Health SL
> +34 961071863<tel:+34%20961%2007%2018%2063> / +34 627015023
> <tel:+34%20627%2001%2050%2023>
> www.veratech.es<http://www.veratech.es/>
>
> Su dirección de correo electrónico junto a sus datos personales forman
> parte de un fichero titularidad de VeraTech for Health SL (CIF B98309511)
> cuya finalidad es la de mantener el contacto con usted. Conforme a La Ley
> Orgánica 15/1999, usted puede ejercitar sus derechos de acceso,
> rectificación, cancelación y, en su caso oposición, enviando una solicitud
> por escrito a verat...@veratech.es<mailto:verat...@veratech.es>.
>
>
>
> --
>
> [eraTech for Health SL]<https://htmlsig.com/t/01C268PZ>
>
> [witter] <https://htmlsig.com/t/01C47QQH>  [inkedIn]  <
> https://htmlsig.com/t/01C4DPJG>  [aps]  <https://htmlsig.com/t/
> 01BZTWS7>
> [https://s3.amazonaws.com/htmlsig-assets/spacer.gif]
>
> Diego Boscá Tomás / Senior developer
> diebo...@veratech.es<mailto:diebo...@veratech.es>
> yamp...@gmail.com<mailto:yamp...@gmail.com>
>
> VeraTech for Health SL
> +34 961071863<tel:+34%20961%2007%2018%2063> / +34 627015023
> <tel:+34%20627%2001%2050%2023>
> www.veratech.es<http://www.veratech.es/>
>
> Su dirección de correo electrónico junto a sus datos personales forman
> parte de un fichero titularidad de VeraTech for Health SL (CIF B98309511)
> cuya finalidad es la de mantener el contacto con usted. Conforme a La Ley
> Orgánica 15/1999, usted puede ejercitar sus derechos de acceso,
> rectificación, cancelación y, en su caso oposición, enviando una solicitud
> por escrito a verat...@veratech.es<mailto:verat...@veratech.es>.
> ___
> 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] <https://htmlsig.com/t/01C268PZ>

[image: Twitter]  <https://htmlsig.com/t/01C47QQH> [image: LinkedIn]
<https://htmlsig.com/t/01C4DPJG> [image: Maps]
<https://htmlsig.com/t/01BZTWS7>

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

VeraTech for Health SL
+34 961071863 <+34%20961%2007%2018%2

Re: Extract archetypes

2017-11-30 Thread Bert Verhees


On 30-11-17 13:06, Diego Boscá wrote:
Having said that, I'm not sure current regex for archetype ids allows 
the use of spaces or undescores on the rm part. I'll have to check that


I was too fast with my compliments ;-)
In that case, we can leave the underscore out, It remains readable.

Bert



2017-11-30 9:04 GMT-03:00 Diego Boscá >:


Hi Bert,

I would say that the "rm name" would be "EHR_Extract", as it is
the way the package is called in the documentation
http://www.openehr.org/releases/RM/latest/docs/ehr_extract/ehr_extract.html


(notice that demographics and EHR are the other package names).

After that you would put the corresponding class name to constraint

Regards

2017-11-30 8:55 GMT-03:00 Bert Verhees >:

Hi,


Since that it is so that some extract-classes derive from
Locatable, they can be used to use them as RM-class for an
archetype-definition.

But how would the ArchetypeId look like, special the rmName.
Would it be something like openEHR-Extract-Extract ?

Thanks in advance for answering

Bert


___
openEHR-technical mailing list
openEHR-technical@lists.openehr.org


http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org






-- 


VeraTech for Health SL 

Twitter LinkedIn
Maps


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

VeraTech for Health SL
+34 961071863  / +34 627015023

www.veratech.es 

Su dirección de correo electrónico junto a sus datos personales
forman parte de un fichero titularidad de VeraTech for Health SL
(CIF B98309511) cuya finalidad es la de mantener el contacto con
usted. Conforme a La Ley Orgánica 15/1999, usted puede ejercitar
sus derechos de acceso, rectificación, cancelación y, en su caso
oposición, enviando una solicitud por escrito a
verat...@veratech.es .




--

VeraTech for Health SL 

Twitter LinkedIn 
Maps 



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

VeraTech for Health SL
+34 961071863  / +34 627015023 


www.veratech.es 

Su dirección de correo electrónico junto a sus datos personales forman 
parte de un fichero titularidad de VeraTech for Health SL (CIF 
B98309511) cuya finalidad es la de mantener el contacto con usted. 
Conforme a La Ley Orgánica 15/1999, usted puede ejercitar sus derechos 
de acceso, rectificación, cancelación y, en su caso oposición, 
enviando una solicitud por escrito a verat...@veratech.es 
.




___
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: Extract archetypes

2017-11-30 Thread Pieter Bos

The test package is called “test_pkg” at least in adl2 – so underscores are 
supported.

Pieter

From: openEHR-technical <openehr-technical-boun...@lists.openehr.org> on behalf 
of Diego Boscá <yamp...@gmail.com>
Reply-To: For openEHR technical discussions 
<openehr-technical@lists.openehr.org>
Date: Thursday, 30 November 2017 at 13:06
To: For openEHR technical discussions <openehr-technical@lists.openehr.org>
Subject: Re: Extract archetypes

Having said that, I'm not sure current regex for archetype ids allows the use 
of spaces or undescores on the rm part. I'll have to check that

2017-11-30 9:04 GMT-03:00 Diego Boscá 
<yamp...@gmail.com<mailto:yamp...@gmail.com>>:
Hi Bert,
I would say that the "rm name" would be "EHR_Extract", as it is the way the 
package is called in the documentation 
http://www.openehr.org/releases/RM/latest/docs/ehr_extract/ehr_extract.html 
(notice that demographics and EHR are the other package names).
After that you would put the corresponding class name to constraint
Regards

2017-11-30 8:55 GMT-03:00 Bert Verhees 
<bert.verh...@rosa.nl<mailto:bert.verh...@rosa.nl>>:
Hi,

Since that it is so that some extract-classes derive from Locatable, they can 
be used to use them as RM-class for an archetype-definition.

But how would the ArchetypeId look like, special the rmName. Would it be 
something like openEHR-Extract-Extract ?

Thanks in advance for answering

Bert

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

--

[eraTech for Health SL]<https://htmlsig.com/t/01C268PZ>

[witter] <https://htmlsig.com/t/01C47QQH>  [inkedIn]  
<https://htmlsig.com/t/01C4DPJG>  [aps]  
<https://htmlsig.com/t/01BZTWS7>
[https://s3.amazonaws.com/htmlsig-assets/spacer.gif]

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

VeraTech for Health SL
+34 961071863<tel:+34%20961%2007%2018%2063> / +34 
627015023<tel:+34%20627%2001%2050%2023>
www.veratech.es<http://www.veratech.es/>

Su dirección de correo electrónico junto a sus datos personales forman parte de 
un fichero titularidad de VeraTech for Health SL (CIF B98309511) cuya finalidad 
es la de mantener el contacto con usted. Conforme a La Ley Orgánica 15/1999, 
usted puede ejercitar sus derechos de acceso, rectificación, cancelación y, en 
su caso oposición, enviando una solicitud por escrito a 
verat...@veratech.es<mailto:verat...@veratech.es>.

--

[eraTech for Health SL]<https://htmlsig.com/t/01C268PZ>

[witter] <https://htmlsig.com/t/01C47QQH>  [inkedIn]  
<https://htmlsig.com/t/01C4DPJG>  [aps]  
<https://htmlsig.com/t/01BZTWS7>
[https://s3.amazonaws.com/htmlsig-assets/spacer.gif]

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

VeraTech for Health SL
+34 961071863<tel:+34%20961%2007%2018%2063> / +34 
627015023<tel:+34%20627%2001%2050%2023>
www.veratech.es<http://www.veratech.es/>

Su dirección de correo electrónico junto a sus datos personales forman parte de 
un fichero titularidad de VeraTech for Health SL (CIF B98309511) cuya finalidad 
es la de mantener el contacto con usted. Conforme a La Ley Orgánica 15/1999, 
usted puede ejercitar sus derechos de acceso, rectificación, cancelación y, en 
su caso oposición, enviando una solicitud por escrito a 
verat...@veratech.es<mailto:verat...@veratech.es>.
___
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org

Re: Extract archetypes

2017-11-30 Thread Bert Verhees


Thanks Diego, that seems a good suggestion based on good reasoning.

Bert


On 30-11-17 13:04, Diego Boscá wrote:

Hi Bert,

I would say that the "rm name" would be "EHR_Extract", as it is the 
way the package is called in the documentation 
http://www.openehr.org/releases/RM/latest/docs/ehr_extract/ehr_extract.html 
(notice that demographics and EHR are the other package names).


After that you would put the corresponding class name to constraint

Regards

2017-11-30 8:55 GMT-03:00 Bert Verhees >:


Hi,


Since that it is so that some extract-classes derive from
Locatable, they can be used to use them as RM-class for an
archetype-definition.

But how would the ArchetypeId look like, special the rmName. Would
it be something like openEHR-Extract-Extract ?

Thanks in advance for answering

Bert


___
openEHR-technical mailing list
openEHR-technical@lists.openehr.org


http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org






--

VeraTech for Health SL 

Twitter LinkedIn 
Maps 



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

VeraTech for Health SL
+34 961071863  / +34 627015023 


www.veratech.es 

Su dirección de correo electrónico junto a sus datos personales forman 
parte de un fichero titularidad de VeraTech for Health SL (CIF 
B98309511) cuya finalidad es la de mantener el contacto con usted. 
Conforme a La Ley Orgánica 15/1999, usted puede ejercitar sus derechos 
de acceso, rectificación, cancelación y, en su caso oposición, 
enviando una solicitud por escrito a verat...@veratech.es 
.




___
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: Extract archetypes

2017-11-30 Thread Diego Boscá

Having said that, I'm not sure current regex for archetype ids allows the
use of spaces or undescores on the rm part. I'll have to check that

2017-11-30 9:04 GMT-03:00 Diego Boscá :

> Hi Bert,
>
> I would say that the "rm name" would be "EHR_Extract", as it is the way
> the package is called in the documentation http://www.openehr.org/
> releases/RM/latest/docs/ehr_extract/ehr_extract.html (notice that
> demographics and EHR are the other package names).
>
> After that you would put the corresponding class name to constraint
>
> Regards
>
> 2017-11-30 8:55 GMT-03:00 Bert Verhees :
>
>> Hi,
>>
>>
>> Since that it is so that some extract-classes derive from Locatable, they
>> can be used to use them as RM-class for an archetype-definition.
>>
>> But how would the ArchetypeId look like, special the rmName. Would it be
>> something like openEHR-Extract-Extract ?
>>
>> Thanks in advance for answering
>>
>> 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 961071863 <+34%20961%2007%2018%2063> / +34 627015023
> <+34%20627%2001%2050%2023>
> www.veratech.es
>
> Su dirección de correo electrónico junto a sus datos personales forman
> parte de un fichero titularidad de VeraTech for Health SL (CIF B98309511)
> cuya finalidad es la de mantener el contacto con usted. Conforme a La Ley
> Orgánica 15/1999, usted puede ejercitar sus derechos de acceso,
> rectificación, cancelación y, en su caso oposición, enviando una solicitud
> por escrito a verat...@veratech.es.
>



-- 

[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 961071863 <+34%20961%2007%2018%2063> / +34 627015023
<+34%20627%2001%2050%2023>
www.veratech.es

Su dirección de correo electrónico junto a sus datos personales forman
parte de un fichero titularidad de VeraTech for Health SL (CIF B98309511)
cuya finalidad es la de mantener el contacto con usted. Conforme a La Ley
Orgánica 15/1999, usted puede ejercitar sus derechos de acceso,
rectificación, cancelación y, en su caso oposición, enviando una solicitud
por escrito a verat...@veratech.es.
___
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org

Re: Extract archetypes

2017-11-30 Thread Diego Boscá

Hi Bert,

I would say that the "rm name" would be "EHR_Extract", as it is the way the
package is called in the documentation
http://www.openehr.org/releases/RM/latest/docs/ehr_extract/ehr_extract.html
(notice that demographics and EHR are the other package names).

After that you would put the corresponding class name to constraint

Regards

2017-11-30 8:55 GMT-03:00 Bert Verhees :

> Hi,
>
>
> Since that it is so that some extract-classes derive from Locatable, they
> can be used to use them as RM-class for an archetype-definition.
>
> But how would the ArchetypeId look like, special the rmName. Would it be
> something like openEHR-Extract-Extract ?
>
> Thanks in advance for answering
>
> 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 961071863 <+34%20961%2007%2018%2063> / +34 627015023
<+34%20627%2001%2050%2023>
www.veratech.es

Su dirección de correo electrónico junto a sus datos personales forman
parte de un fichero titularidad de VeraTech for Health SL (CIF B98309511)
cuya finalidad es la de mantener el contacto con usted. Conforme a La Ley
Orgánica 15/1999, usted puede ejercitar sus derechos de acceso,
rectificación, cancelación y, en su caso oposición, enviando una solicitud
por escrito a verat...@veratech.es.
___
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org

Extract archetypes

2017-11-30 Thread Bert Verhees


Hi,


Since that it is so that some extract-classes derive from Locatable, 
they can be used to use them as RM-class for an archetype-definition.


But how would the ArchetypeId look like, special the rmName. Would it be 
something like openEHR-Extract-Extract ?


Thanks in advance for answering

Bert


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

Re: Extract archetypes

Re: Extract archetypes

Re: Extract archetypes

Re: Extract archetypes

Re: Extract archetypes

Re: Extract archetypes

Re: Extract archetypes

Re: Extract archetypes

Re: Extract archetypes

Re: Extract archetypes

Re: Extract archetypes

Re: Extract archetypes

Re: Extract archetypes

Re: Extract archetypes

Extract archetypes

15 matches

Site Navigation

Mail list logo

Footer information