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á <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>>:
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
<http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org>
--
VeraTech for Health SL <https://htmlsig.com/t/000001C268PZ>
Twitter <https://htmlsig.com/t/000001C47QQH>LinkedIn
<https://htmlsig.com/t/000001C4DPJG>Maps
<https://htmlsig.com/t/000001BZTWS7>
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>.
--
VeraTech for Health SL <https://htmlsig.com/t/000001C268PZ>
Twitter <https://htmlsig.com/t/000001C47QQH>LinkedIn
<https://htmlsig.com/t/000001C4DPJG>Maps
<https://htmlsig.com/t/000001BZTWS7>
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
_______________________________________________
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
