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:[email protected]] *On Behalf Of
*Ian McNicoll
*Sent:* Tuesday, January 17, 2017 12:17 PM
*To:* For openEHR technical discussions
<[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
<[email protected]
<mailto:[email protected]>> wrote:
_______________________________________________
openEHR-technical mailing list
[email protected]
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
