William, It is potentially dangerous ground. But ...
- Archetypes express what can be documented about a specific topic. Since such a 'Real Archetype' can or will consist of re-usable patterns, 'Real Archetypes' consist many times of a collection of sub- archetypes that express recurring patterns of documentation. In other words archetypes can and will be nested. And there must be a way to specify what archetypes are part of the ensemble at what spots. - It will create the problem for Archetype Governance. We need to have rules and ways to manage and enforce them. This needs a tool. Ocean Informatics, for this purpose, has developed the Archetype Knowledge Manager. Gerard On 14, Jun, 2008, at 7:31 , Williamtfgoossen at cs.com wrote: > > We are getting into dangerous options here: include all and exclude > all in a time series where 'all' definitely changes both with > respect to revisions of the existing ones, deletions and new to be > added might lead to inconsistent calls to archetypes over time. > > I believe such constraining should not take place on the archetype > over archetype level, but at the (OpenEHR) template level. In here > you can be explicit in what is to be included or excluded. > -- <private> -- Gerard Freriks, MD Huigsloterdijk 378 2158 LR Buitenkaag The Netherlands T: +31 252544896 M: +31 620347088 E: gfrer at luna.nl Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. Benjamin Franklin 11 Nov 1755 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20080614/8845ef4a/attachment.html>
