Template Designer alternatives

Heath Frankel heath.frankel at oceaninformatics.com
Sun Feb 28 18:05:58 EST 2016

Hi Pablo,
Since templates are intended to assign terminology bindings for specific implementation, the Template Design skips the step to need to specify a coded text type and allows you to specify a terminology binding using the Value set (terminology) property as shown below.

[cid:image001.png at 01D172D2.9C4018C0]

[cid:image002.png at 01D172D3.08CCCB00]

The above tab uses the Ocean terminology service (DEMO), you can select predefined value set or select a full terminology. The Generic Value Set tab allows your own value set references

[cid:image003.png at 01D172D3.08CCCB00]

Alternatively, you can specify an inline value set using the property above as shown below. Select the Terminology checkbox, enter the code and value and finally the terminology drop down list (this needs to be last to get the + button to enable).

[cid:image004.png at 01D172D4.97251C80]

Both of these methods result in the OPT outputting a CODE_TEXT constraint.


From: openEHR-technical [mailto:openehr-technical-bounces at lists.openehr.org] On Behalf Of pablo pazos
Sent: Sunday, 28 February 2016 5:25 PM
To: openeh technical <openehr-technical at lists.openehr.org>; openehr implementers <openehr-implementers at lists.openehr.org>
Subject: Template Designer alternatives

HI all,

I tried the latest release of the TD and keeps having some constraints on modelling, like the impossibility of specifying that a DV_TEXT will be used as DV_CODED_TEXT on the data type option, or removing (0..0) slots that will not be used on the final OPT.

I'm wondering if are there any template designer alternatives to create operational templates, that allows to set DV_TEXTs as DV_CODED_TEXT only or setting the 0..0 occurrence to SLOT nodes.


Kind regards,
Eng. Pablo Pazos Gutiérrez
No virus found in this message.
Checked by AVG - www.avg.com<http://www.avg.com>
Version: 2015.0.6189 / Virus Database: 4533/11681 - Release Date: 02/22/16
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20160228/6a1661f7/attachment-0002.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 3809 bytes
Desc: image001.png
URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20160228/6a1661f7/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 42772 bytes
Desc: image002.png
URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20160228/6a1661f7/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 23061 bytes
Desc: image003.png
URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20160228/6a1661f7/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 10327 bytes
Desc: image004.png
URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20160228/6a1661f7/attachment-0003.png>

More information about the openEHR-technical mailing list