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.
LinkEHR has the ability to import and export OPT and OET. Once you import it is just treated as an archetype, so in principle any constraint can be defined.
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.
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
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).
Both of these methods result in the OPT outputting a CODE_TEXT constraint.