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 McNicollDate: Mon, Jan 25, 2016 10:06To:
For openEHR technical discussions;Subject:Archetype relational mapping - a
practical openEHR persistence solutionInteresting 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: [email protected]
twitter: @ianmcnicoll
Co-Chair, openEHR Foundation [email protected], 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
