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 multiple templates defined by the domain experts.
Regards Xudong 2016-01-25 22:25 GMT+08:00 [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
