Re: Latest ADL / AOM 1.5 & template specification drafts
On 08-Mar-10 11:25, Thomas Beale wrote: > > A new draft is now up of the AOM 1.5 at > http://www.openehr.org/svn/specification/TRUNK/publishing/architecture/am/adl1.5.pdf > . This draft adds in group construct, providing the same capability as > XML schema choice/sequence/group for ordering elements within > container > attributes. The AOM constraint model with this added in looks as > follows: > http://www.openehr.org/wiki/download/attachments/196633/AOM_with_group.png Hi Thomas, Thanks for the new draft: adl_1.5. I imagine that openEHR is the art-of-the-possible so I really value your latest updates: In Section 6 - Assertions I note the the advent (in standard cADL syntax) of Rules involving QUERY RESULTS from a data or knowledge context - for example (from Section 6.5.5): $has_diabetes:Boolean ::= query("ehr", "has_diagnosis", "snomed_ct:1234567") $is_female:Boolean ::= query("ehr", "is_female") Does this kind of rule provide some sort of basis for implementing generalized methods (I'm thinking of OOD association relationships) at the archetype level? Archetyped objects - with their hermetically sealed inner states - probably need to share some state info in order to do useful EHR-related work. And the way in which that state needs to be shared may reflect semantic order of the modeled EHR beyond that established by the containment/inheritance constraints envisaged by openEHR at the RM and CKM level. Are we sure that this "semantic order" is best left to a set of external queries and, or, relegated to details of local template modeling? My pet ruse with openEHR has been that when we get down to the perspective of the data entry GUI - the validity of the data-input may depend on knowledge hermetically hidden way in another archetyped object - and I'd like a principled way of generalizing the validation rule (for reuse) - who knows: it might even be important semantic element of the pattern of system of archetypes. And informal semi-structured querying such as query("ehr", "is_female") still seems a bit of an abdication of responsibility to me. Gavin Brelstaff CRS4 Sardinia Italy. _______________________________________________ openEHR-technical mailing list openEHR-technical@openehr.org http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
