Agree - by 'remove', I mean set occurences to 0, not remove it altogether. Ian
Dr Ian McNicoll mobile +44 (0)775 209 7859 office +44 (0)1536 414994 skype: ianmcnicoll email: [email protected] twitter: @ianmcnicoll Co-Chair, openEHR Foundation Management Board Director, freshEHR Clinical Informatics Director, HANDIHealth CIC Hon. Senior Research Associate, CHIME, UCL On 3 May 2015 at 11:45, Diego Boscá <[email protected]> wrote: > I assumed that it was an optional slot, if not you could never "remove" it. > > 2015-05-03 12:37 GMT+02:00 Ian McNicoll <[email protected]>: > > Hi Diego, > > > > My understanding is that ADL 1.4 does not formally support slot closures > or > > indeed setting ocurrences of any element to 0 in > specialisations/templates. > > > > Certainly not supported in the openEHR Archetype Editor. > > > > Ian > > > > Dr Ian McNicoll > > mobile +44 (0)775 209 7859 > > office +44 (0)1536 414994 > > skype: ianmcnicoll > > email: [email protected] > > twitter: @ianmcnicoll > > > > Co-Chair, openEHR Foundation Management Board > > Director, freshEHR Clinical Informatics > > Director, HANDIHealth CIC > > Hon. Senior Research Associate, CHIME, UCL > > > > On 3 May 2015 at 10:08, Diego Boscá <[email protected]> wrote: > >> > >> Can't this be achieved creating an specialization and then using that in > >> the TD? > >> > >> El 3/5/2015 9:27, "Ian McNicoll" <[email protected]> escribió: > >>> > >>> Hi Pablo, > >>> > >>> This is not possible. The ability to 'close' a slot comes with ADL1.5/2 > >>> > >>> Ian > >>> > >>> Dr Ian McNicoll > >>> mobile +44 (0)775 209 7859 > >>> office +44 (0)1536 414994 > >>> skype: ianmcnicoll > >>> email: [email protected] > >>> twitter: @ianmcnicoll > >>> > >>> Co-Chair, openEHR Foundation Management Board > >>> Director, freshEHR Clinical Informatics > >>> Director, HANDIHealth CIC > >>> Hon. Senior Research Associate, CHIME, UCL > >>> > >>> On 3 May 2015 at 03:49, pablo pazos <[email protected]> wrote: > >>>> > >>>> Hi, I'm creating a template from the Encounter archetype using the TD. > >>>> > >>>> That archetype has a slot in the compo.context.other_context. I don't > >>>> use that slot so I don't want it to appear in my final OPT, but I > couldn't > >>>> find any way in the TD to let me remove that node or put 0..0 on the > >>>> cardinality, so the exported OPT has the slot. > >>>> > >>>> Is there any way to do this? Maybe other OPT designers? > >>>> > >>>> I'm using TD v2.6.1214Beta > >>>> > >>>> Thanks! > >>>> > >>>> -- > >>>> Kind regards, > >>>> Eng. Pablo Pazos Gutiérrez > >>>> http://cabolabs.com > >>>> > >>>> _______________________________________________ > >>>> openEHR-technical mailing list > >>>> [email protected] > >>>> > >>>> > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org > >>> > >>> > >>> > >>> _______________________________________________ > >>> openEHR-technical mailing list > >>> [email protected] > >>> > >>> > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org > >> > >> > >> _______________________________________________ > >> openEHR-technical mailing list > >> [email protected] > >> > >> > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org > > > > > > > > _______________________________________________ > > openEHR-technical mailing list > > [email protected] > > > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org > > _______________________________________________ > openEHR-technical mailing list > [email protected] > > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org >
_______________________________________________ openEHR-technical mailing list [email protected] http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
