Occurrences on Top level element

Sam Heard sam.heard at oceaninformatics.com
Sun Oct 29 07:55:05 EDT 2017


Hi Leonardo

 

I think such a constraint usually belongs in the container. Do you have an example?

 

Cheers, Sam

 

From: openEHR-clinical [mailto:openehr-clinical-bounces at lists.openehr.org] On Behalf Of leonardo ornelas
Sent: Saturday, 28 October 2017 8:18 AM
To: openehr-clinical at lists.openehr.org
Subject: Occurrences on Top level element

 

Hello, my name is Leonardo Ornelas, this is my first message for this mail list. Maybe somebody could take my doubts. I'm working on a project that follows some parts of openEHR. I did an adl-core implementation on nodejs. This version makes the parser from adl to json, supports flattener of archetypes and generation of operational templates, as well as the generation of a hierarchical model of RM from Archetype / OPT. There is a person in the team in charge of creating some templates and archetypes for our needs, which led to a questioning about occurrences that he could not answer. I looked in the document but could not find it on. I wonder if in the RM model it is possible to have occurrences of a element that is root? Eg. If a CLUSTER is the first element of an archetype that cluster could have occurrence 0 .. * or 1 .. *.

 

Could the following ADL be valid?

...

definition

    EVALUATION [id1.1] matches occurrences matches {0..2} matches {

...

 

In that case, in the RM model, when in the form add a new element, could I have an EVALUDATION with the same archetype_node_id?

 

Thanks in advance.

-- 

Leonardo Ornelas

leonardo.ornelas at solutis.com.br <mailto:edijane.paim at solutis.com.br> 

www.solutis.com.br <http://www.solutis.com.br> 

 

Antes de imprimir, pense na sua responsabilidade com o meio ambiente.

As informações contidas nesta mensagem são CONFIDENCIAIS, protegidas pelo sigilo legal e por direitos autorais. A divulgação, distribuição, reprodução ou qualquer forma de utilização do teor deste documento depende de autorização do emissor, sujeitando-se o infrator às sanções legais. Caso esta comunicação tenha sido recebida por engano, favor avisar imediatamente, respondendo esta mensagem.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openehr.org/pipermail/openehr-clinical_lists.openehr.org/attachments/20171029/16dd632f/attachment-0002.html>


More information about the openEHR-clinical mailing list