RE: Template Designer alternatives

2016-03-02 Thread pablo pazos 
Hi Heath, I think this would work for my needs, will try it on the weekend and 
get back here if I find any issues.
Thanks a lot!

-- 
Kind regards,
Eng. Pablo Pazos Gutiérrez
http://cabolabs.com

From: heath.fran...@oceaninformatics.com
To: openehr-technical@lists.openehr.org; openehr-implement...@lists.openehr.org
Subject: RE: Template Designer alternatives
Date: Sun, 28 Feb 2016 23:05:58 +









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.
 

 

 
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.
 
Heath
 


From: openEHR-technical [mailto:openehr-technical-boun...@lists.openehr.org]
On Behalf Of pablo pazos

Sent: Sunday, 28 February 2016 5:25 PM

To: openeh technical <openehr-technical@lists.openehr.org>; openehr 
implementers <openehr-implement...@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.


 


Thanks!


 



-- 

Kind regards,

Eng. Pablo Pazos Gutiérrez

http://cabolabs.com





No virus found in this message.

Checked by AVG - www.avg.com

Version: 2015.0.6189 / Virus Database: 4533/11681 - Release Date: 02/22/16




___
openEHR-implementers mailing list
openehr-implement...@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-implementers_lists.openehr.org
  ___
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org

RE: Template Designer alternatives

2016-02-28 Thread Heath Frankel 
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@01D172D2.9C4018C0]

[cid:image002.png@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@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@01D172D4.97251C80]

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

Heath

From: openEHR-technical [mailto:openehr-technical-boun...@lists.openehr.org] On 
Behalf Of pablo pazos
Sent: Sunday, 28 February 2016 5:25 PM
To: openeh technical ; openehr 
implementers 
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.

Thanks!


--
Kind regards,
Eng. Pablo Pazos Gutiérrez
http://cabolabs.com

No virus found in this message.
Checked by AVG - www.avg.com
Version: 2015.0.6189 / Virus Database: 4533/11681 - Release Date: 02/22/16
___
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org

RE: Template Designer alternatives

2016-02-28 Thread pablo pazos 
Is there an open source version? Until I have some funding can't buy any 
licenses. Thanks!

-- 
Kind regards,
Eng. Pablo Pazos Gutiérrez
http://cabolabs.com

Date: Sun, 28 Feb 2016 08:43:23 +0100
Subject: Re: Template Designer alternatives
From: yamp...@gmail.com
To: openehr-technical@lists.openehr.org
CC: openehr-implement...@lists.openehr.org

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. 
Regards 
El 28/2/2016 7:56, "pablo pazos" <pazospa...@hotmail.com> escribió:



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.
Thanks!

-- 
Kind regards,
Eng. Pablo Pazos Gutiérrez
http://cabolabs.com   

___

openEHR-technical mailing list

openEHR-technical@lists.openehr.org

http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org


___
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org   
  ___
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org

Re: Template Designer alternatives

2016-02-27 Thread Diego Boscá 
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.

Regards
El 28/2/2016 7:56, "pablo pazos"  escribió:

> 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.
>
> Thanks!
>
>
> --
> Kind regards,
> Eng. Pablo Pazos Gutiérrez
> http://cabolabs.com 
> 
>
> ___
> openEHR-technical mailing list
> openEHR-technical@lists.openehr.org
>
> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
>
___
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org