Hi Athanasios,
see the ADL 1.5 spec <http://www.openehr.org/svn/specification/TRUNK/publishing/architecture/am/adl1.5.pdf> section 5.3.9.3 for the rules. - thomas On 10/04/2012 17:11, Athanasios Anastasiou wrote: > Hello everyone > > How do the "includes / excludes" fields of an Archetype Slot get > interperted to conclude with one set of rules about which archetypes > are allowed to be attached to a slot? > > Browsing through various archetypes i am noticing that some slots will > only have one or more "includes" while others have one or more > "includes" and ".*" at the "excludes" field. > > Are these two fields to be cascaded? (i.e. Include everything that > satisfies the include condition and then FROM THE INCLUDED LIST > exclude everything that satisfies the exclude condition) > > Or would they operate in parallel? (i.e. Get everything that satisfies > the include condition, Get everything that satisfies the exclude > condition, merge the two sets. The merged set governs what is allowed > to be included to a particular slot). > > > And, are the following equivalent? > > "include > archetype_id/value matches {/openEHR-EHR-CLUSTER\.address\.v1/} > exclude > archetype_id/value matches {/.*/}" > > This means "Include ONLY an address" (?) > In this case it makes sense to evaluate the include/exclude fields in > parallel. > > "include > archetype_id/value matches > {/openEHR-EHR-CLUSTER\.telecom_details\.v1/}" > > (In this case there was no exclude) > This must mean "Include ONLY telecom_details" (?) > > > A secondary question, is there any case where it might be required to > "Include" or "Exclude" an archetype with a condition other than its > name / class? I am asking this because the "includes" / "excludes" are > Assertions but all archetypes i have seen so far "match" the > archetype_id/value only. > > Looking forward to hearing from you > Athanasios Anastasiou > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at lists.openehr.org > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org > > -- Ocean Informatics *Thomas Beale Chief Technology Officer, Ocean Informatics <http://www.oceaninformatics.com/>* Chair Architectural Review Board, /open/EHR Foundation <http://www.openehr.org/> Honorary Research Fellow, University College London <http://www.chime.ucl.ac.uk/> Chartered IT Professional Fellow, BCS, British Computer Society <http://www.bcs.org.uk/> Health IT blog <http://www.wolandscat.net/> * * -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20120410/34bd88a1/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: ocean_full_small.jpg Type: image/jpeg Size: 5828 bytes Desc: not available URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20120410/34bd88a1/attachment.jpg>
