ITEM_TREE[at0001] matches { -- Tree
items cardinality matches {1..*; unordered} matches {
CLUSTER[at0009] occurrences matches {0..1} matches { -- Flavour
name matches {
DV_TEXT matches {*}
DV_CODED_TEXT matches {
defining_code matches {
[local::
at0010, -- asdasd
at0011] -- asdasda
}
}
}
....The main issue is that though the the Archetype Editor will read that construct, it loses the internal codes if the archetype is changed i.e it does not write the data back out again. Ian Dr Ian McNicoll mobile +44 (0)775 209 7859 office +44 (0)1536 414994 skype: ianmcnicoll email: [email protected] twitter: @ianmcnicoll Co-Chair, openEHR Foundation [email protected] Director, freshEHR Clinical Informatics Ltd. Director, HANDIHealth CIC Hon. Senior Research Associate, CHIME, UCL On 17 January 2017 at 12:36, Thomas Beale <[email protected]> wrote: > > It should be the same as for ADL2 except of course, stick to using the > correct at-codes, i.e. 'at0004' etc, rather than id-codes. SO I think the > example from the ADL 2 spec is pretty close to the one you want, with > at-codes, and terminal constraints they way you want. > > definition > ... > name ∈ { > DV_CODED_TEXT[id79] ∈ { > defining_code ∈ {[ac1]} > } > DV_TEXT[id14] ∈ { > value ∈ {/.+/} -- non-empty string > } > } > ... > terminology > ... > term_bindings = < > ["snomed_ct"] = < > ["ac1"] = <http://snomed.info/123456789> -- any SNOMED CT code > > > > > > > - thomas > > On 17/01/2017 11:23, Bakke, Silje Ljosland wrote: > > Thanks! If I knew the syntax I could hack the ADL and test how TD handles > it. J > > > > Regards, > *Silje* > > > > *From:* openEHR-technical [mailto:openehr-technical- > [email protected] <[email protected]>] *On > Behalf Of *Ian McNicoll > *Sent:* Tuesday, January 17, 2017 12:17 PM > *To:* For openEHR technical discussions <openehr-technical@lists. > openehr.org> <[email protected]> > *Subject:* Re: Runtime name suggestions? > > > > Hi Silje > > As Thomas has noted, it is possible in adl but is not supported in > archetype editor. That is probably fixable but I'm not sure currently how > template designer would handle it. > > Ian > > On Tue, 17 Jan 2017 at 11:03, Bakke, Silje Ljosland <silje.ljosland.bakke@ > nasjonalikt.no> wrote: > > > > _______________________________________________ > openEHR-technical mailing list > [email protected] > http://lists.openehr.org/mailman/listinfo/openehr- > technical_lists.openehr.org >
_______________________________________________ openEHR-technical mailing list [email protected] http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
