Hi Tom, Would this be a template on the EHR_EXTRACT? Heath
> -----Original Message----- > From: openehr-technical-bounces at openehr.org [mailto:openehr-technical- > bounces at openehr.org] On Behalf Of Thomas Beale > Sent: Sunday, 5 April 2009 6:50 PM > To: For openEHR technical discussions > Subject: Re: Definition of persistence for a composition > > Leonardo Moretti wrote: > > Hi Sam, > > thanks for your reply. I try to explain which is my issue. > > Generally in an application form we can have persistent and not > persistent > > data. Actually template specifications allow at most one composition > in each > > template, but this means that a template contains or all persistent > data or > > all not persistent data. > > In order to define template with both persistent and not persistent > data, we > > should be able to have template with more than one composition. Has > anyone > > solved this problem? > > > > leo > > > * > It is not currently in the template concept, but it has been talked > about. The design question is whether we should have 'multi-root point' > templates, or whether there should be a construct at a higher level > than > a template which puts templated top-level objcets (like Compositions) > together, and which allows not only multiple templates, each of which > could be from a different data source, but other, external data > sources, > i.e. other databases in the environment. It would also be able to > include queries, so that some fields would be the results of this, > rather than entry fields. This concept might be thought of as a 'form' > or 'data package' of some kind. > > I am in favour of this higher level concept, which allows each included > template and other data items to be bound to different data sources. > > - thomas beale > > * > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at openehr.org > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
