Bert Verhees wrote: > > > So no problem at all, in the end, one could say. > ------------ > The holy grail is a more generic approach which allows archetypes > written as simple scripts which can use an information-system flexible > and even allows ad-hoc creations of archetypes. > Creating a new information-structure will then be work of days, or > maybe a few weeks, instead of months or years, and can be done by > people with not much knowledge of programming.` > > This holy grail can be reached much more simple if one has the > possibility to create a specially formed shadow-database, or better, > to do a data-migration to a new database-structure.
one way of doing this is as follows: - in openEHR 1.1, there will be an ENTRY type which looks like a CEN EN13606 ENTRY, i.e. more or less just a dumb tree structure of CLUSTERs & ELEMENTs. - you could build you shadow database using the openEHR model, which will include this ENTRY type - you could import your data by doing conversions to EN13606 style ENTRYs, which should be quite easy (since they don't force you into anything like the other openEHR ENTRY types do); legacy archetypes could be defined for each message or source db row type you get your information from - data could eventually be converted from this form to 'real' openEHR ENTRYs at some later point. The conversion is mediated by inferencing from legacy archetypes -> designed archetypes (based on GPICs in some cases, presumably) - the key to this is that a) all the hard work is done inside an openEHR environment - the models are guaranteed to be coherent (and you will be able to get free software to do it) and b) the schema of your 'shadow db' doesn't ever change. hope this helps, - thomas beale > > Unfortunately, that is not my case, I do live queries on different > datamodels and using different interfaces. Some aren't SQL-based, but > API-based, very old stuff. > So I wonder if it is possible to migrate data in live queries to a > needed generic virtual database structure. I have to study on this. > GPICs are a much easier approach in my case. -- ___________________________________________________________________________________ CTO Ocean Informatics (http://www.OceanInformatics.biz) Research Fellow, University College London (http://www.chime.ucl.ac.uk) Chair Architectural Review Board, openEHR (http://www.openEHR.org) - If you have any questions about using this list, please send a message to d.lloyd at openehr.org
