On Wed, 2004-03-03 at 03:04, Thomas Beale wrote: > I have to admit that it is only now that we have begun to write primers > of various kinds to help understanding - they will start to appear on > the web. But in the end, nothing substitutes for presentations and > interactive communication...
Pedagogic and didactic materiel are useful, but the thing which will really win people over is the availability of an openEHR storage/query engine. Until then, for many of us, openEHR remains an extremely interesting theoretical thought experiment. But as we all know, the gap between theory and practise tends to be small in theory but large in practise. My concerns are that: a) the storage/query engine will be much harder to build and validate than anyone thinks; b) when used to model and capture a wide range of real-life information, either openEHR RM (reference model) or the Archetype definition language or its conceptual underpinnings will be found to have significant gaps, which then need to be plugged, possibly in messy and inelegant ways - that is a common pattern: a beautifully simple idea ends up as a big, sprawling mess (no, I didn't mention Java...). I am not saying that either of these things will happen, but their possibility needs to go into the openEHR risk equation, at least until there is more documented and, ideally, first-hand experience with it. Regarding documented experience, is there a bibliography anywhere of published evaluations of actual implementations of openEHR, or of its predecessor GEHR? That would help. I've read the theory of openEHR several times, but I'd love to read about some practical experiences with it in pilot systems. -- Tim C PGP/GnuPG Key 1024D/EAF993D0 available from keyservers everywhere or at http://members.optushome.com.au/tchur/pubkey.asc Key fingerprint = 8C22 BF76 33BA B3B5 1D5B EB37 7891 46A9 EAF9 93D0
signature.asc
Description: This is a digitally signed message part
