Hi Leo Persistent is a feature that has meaning and cannot be changed at runtime. It means that the data goes on being relevant and does not apply to one clinical event. It also means that updates are not fixing errors or incompleteness - they are a new statement of the information. The old data are not invalidated for the period that was covered.
So you can think of persistent compositions as Managed Lists (current medications, allergies etc) I wondered how you were interpreting it? Cheers, Sam > -----Original Message----- > From: openehr-technical-bounces at openehr.org [mailto:openehr-technical- > bounces at openehr.org] On Behalf Of Leonardo Moretti > Sent: 03 March 2009 23:43 > To: openehr-technical at openehr.org > Subject: Definition of persistence for a composition > > > Hi all, > I'd like to define persistence for a composition dinamically (and not > statically in an archetype), because this property changes depending on > application or application context. > > If I'd like to define a composition as persistent, could I define this > into > a template? Is this the correct way to use templates? Moreover, in some > particular case, I don't exclude to change persistence attribute for a > compositon at run-time, depending of application context. > > Any other suggestions? > leo > -- > View this message in context: http://www.nabble.com/Definition-of- > persistence-for-a-composition-tp22306941p22306941.html > Sent from the openehr-technical mailing list archive at Nabble.com. > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at openehr.org > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
