Hi Silje,
I'm not sure enough of the requirement, but this ADL logic
<http://www.openehr.org/releases/AM/latest/docs/ADL2/ADL2.html#_reference_model_type_refinement>
may be what you are looking for. See the DV_TEXT/DV_CODED_TEXT just
before the following heading after that section.
The basic logic of this is described here
<http://www.openehr.org/releases/AM/latest/docs/ADL2/ADL2.html#_narrowed_subtype_constraints>.
Although these are references from ADL2, they should apply in ADL 1.4 as
well.
- thomas
On 17/01/2017 07:49, Bakke, Silje Ljosland wrote:
Hi,
We’re trying to finalise the pattern for exclusion archetypes, and
would like to use the element names to carry some flavor differences
such as “no known history of …” and “no evidence of …”. We’ve
considered adding a runtime name constraint to make some level of
standardization of these statements, but at the same time we recognize
that there will be considerable variation in what will be required as
statements in different use cases. So what we’d like to do is to use a
kind of “optional runtime name constraint”, or “runtime name
suggestion”. We know this isn’t supported by tooling atm, but is it
allowed by the specs? If so, how can it be done?
Kind regards,
*Silje Ljosland Bakke*
**
_______________________________________________
openEHR-technical mailing list
[email protected]
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
