Archetype relational mapping - a practical openEHR persistence solution

Interesting paper from China http://bmcmedinformdecismak.biomedcentral.com/articles/10.1186/s12911-015-0212-0 Ian Dr Ian McNicoll mobile +44 (0)775 209 7859 office +44 (0)1536 414994 skype: ianmcnicoll email: i...@freshehr.com twitter: @ianmcnicoll Co-Chair, openEHR Foundation

Re: Archetype relational mapping - a practical openEHR persistence solution

I talked about this approach with a colleague from China during MEDINFO. The problem is your schema grows with your archetypes. Also, that storing data from many templates that don't use all the fields in the archetype, will generate sparse tables (lots of null columns). I told him it

Re: Archetype relational mapping - a practical openEHR persistence solution

based on a quick look, my reaction is the same, unless they have some very interesting Archetype => Schema transformation. On 25/01/2016 14:25, pazospa...@hotmail.com wrote: I talked about this approach with a colleague from China during MEDINFO. The problem is your schema grows with your

Re: Archetype relational mapping - a practical openEHR persistence solution

Another problem is you have to convert your object oriented model (which RM is) to a relational model, which becomes complex in converting templates/aql to SQL. I have been that way. More then five years ago I left it. It is difficult doable, if you want a full featured openehr kernel. I would

Re: Archetype relational mapping - a practical openEHR persistence solution

Alas, the hyperlink seems to be broken. 25.01.2016, 16:06, "Ian McNicoll" :Interesting paper from China -- Regards, Dmitry ___ openEHR-technical mailing list openEHR-technical@lists.openehr.org

Re: Archetype relational mapping - a practical openEHR persistence solution

Actually, we use such mappings to promote some "important" elements to relational tables to get sort of indices on the data. Otherwise, I don't think we would be able to do efficient ad-hoc cross-patient queries directly on the database. Exporting data to I2B2 or SSAS would be inconvenient

RE: Archetype relational mapping - a practical openEHR persistence solution

Hi Birger, It might be this paper you are thinking of. Freire S, Sundvall E, Karlsson D, Lambrix P. Performance of XML Databases for Epidemiological Queries in Archetype-Based EHRs. Scandinavian Conference on Health Informatics 2012; October 2-3; Linköping; Sweden. P 51-57. Linköping

RE: Archetype relational mapping - a practical openEHR persistence solution

ORM is not a problem with current tools. In fact frameworks like Hibernate and Grails make Object-Relational Mapping something enjoyable to work with. I think the problem with the described approach is the growth of the relational schema when your knowledge base grows. But there are design

Re: Archetype relational mapping - a practical openEHR persistence solution

Hi Ian and all, We, openEHR Japan had an unconference with Dr Lu and he gave us a presentation for us about this research. I will ask him if the slides would be shareble. Shinji KOBAYASHI 2016-01-25 22:04 GMT+09:00 Ian McNicoll : > Interesting paper from China > > >