Re: Archetype relational mapping - a practical openEHR persistence solution

We haven't convert RM to relational model, it will cause lots of JOIN operation and low performance. Actually, we using "storage template", which is a specialization of archetype for storage purpose, and is generated automatically according to existing multiple templates (If more templates are

Re: Archetype relational mapping - a practical openEHR persistence solution

Dear all, I just found there are lots of comments on our recent paper. Thanks for all these comments, I will read them and reply later. @Shinji, Of course the slides could be shared. Regards Xudong 2016-01-26 10:44 GMT+08:00 Shinji KOBAYASHI : > Hi Ian and all, > > We,

Re: Archetype relational mapping - a practical openEHR persistence solution

Dear all, I just found there are lots of comments on our recent paper. Thanks for all these comments, I will read them and reply later. @Shinji, Of course the slides could be shared. Regards Xudong 2016-01-26 10:44 GMT+08:00 Shinji KOBAYASHI : > Hi Ian and all, > > We,

Re: Archetype relational mapping - a practical openEHR persistence solution

Thanks, pazospablo. Yes, you are right. There may generate sparse tables. We found the problem when we using it in the implementation. Currently, we update our method to use "storage template" to specialise the archetypes. The "storage template" will be generated automatically through combining