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 added, the "storage template" will be updated, but in real case, it will not be updated too often).
Best Regards Xudong 2016-01-26 1:42 GMT+08:00 Bert Verhees <[email protected]>: > 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 never recommend going this way, unless someone has a really smart > idea. > > It can work for a light featured openehr light derived application model. > > Best regards > Bert > Op 25 jan. 2016 15:26 schreef "[email protected]" < > [email protected]>: > >> 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 was >> easier to do an ORM from the IM, because the schema doesn't change and >> allows to store data from any archetype/template. But they already have a >> system working this way. >> >> >> Sent from my LG Mobile >> >> ------ Original message------ >> >> *From: *Ian McNicoll >> >> *Date: *Mon, Jan 25, 2016 10:06 >> >> *To: *For openEHR technical discussions; >> >> *Subject:*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 <+44%20(0)775%20209%207859> >> office +44 (0)1536 414994 <+44%20(0)1536%20414994> >> skype: ianmcnicoll >> email: [email protected] >> twitter: @ianmcnicoll >> >> Co-Chair, openEHR Foundation [email protected] >> Director, freshEHR Clinical Informatics Ltd. >> Director, HANDIHealth CIC >> Hon. Senior Research Associate, CHIME, UCL >> >> _______________________________________________ >> openEHR-technical mailing list >> [email protected] >> >> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org >> > > _______________________________________________ > openEHR-technical mailing list > [email protected] > > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org >
_______________________________________________ openEHR-technical mailing list [email protected] http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
