PortaVita MGRID database does exactly this job, but based on HL7 v3 templates. It allows storage of source documents, querying against Snomed CT etc on details and allows Full XML handling.
Vriendelijke groet, Dr. William Goossen Directeur Results 4 Care BV +31654614458 > Op 4 feb. 2014 om 18:00 heeft openehr-technical-request at lists.openehr.org > het volgende geschreven: > > Send openEHR-technical mailing list submissions to > openehr-technical at lists.openehr.org > > To subscribe or unsubscribe via the World Wide Web, visit > > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org > > or, via email, send a message with subject or body 'help' to > openehr-technical-request at lists.openehr.org > > You can reach the person managing the list at > openehr-technical-owner at lists.openehr.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of openEHR-technical digest..." > > > Today's Topics: > > 1. Persistence of Compositions (Birger Haarbrandt) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 04 Feb 2014 17:33:46 +0100 > From: Birger Haarbrandt <birger.haarbrandt at plri.de> > To: For openEHR technical discussions > <openehr-technical at lists.openehr.org> > Subject: Persistence of Compositions > Message-ID: <52F1166A.7080803 at plri.de> > Content-Type: text/plain; charset="iso-8859-15"; Format="flowed" > > Hey there, > > we make good progress in understanding and applying openEHR to our Data > Warehouse project. First data mappings have been done and a poc ETL > process utilizing mapforce generated c# code has been created for vital > parameters (originating from the ICU). Currently, I'm working on the > data model of the persistence layer. I know that there has been some > discussion about this topic in the past and recently. I checked > implementation examples like Pablo's ehrGEN project and Erik Sundvalls' > Liu EEE. Additionally I read a paper that gave a helpful overview about > persistence strategies and enjoyed the discussion Bert started on LinkedIn. > > To get to the point: We intend to use a mixed approach involving a MS > SQL Server. More or less static data is supposed to be in the relational > part while most clinical data (with the exception of lab values for > example) should be represented as rows of XML datatype. Erik's approach > was to develop a proprietary XML Schema to wrap compositions and > contained entries. Obviously, this might work in a native XML database > like eXist but does not serve our needs. Additionally, storing the > archetypes in a relational fashion is not be our first choice. > Therefore, I'm interested to learn if any of you has already spent some > thoughts about best practices to split compositions into individual XML > documents while keeping the relationship throughout different tables > and/or rows. > > Cheers, > > -- > *Birger Haarbrandt, M.Sc.* > > Peter L. Reichertz Institut f?r Medizinische Informatik > Technische Universit?t Braunschweig und > Medizinische Hochschule Hannover > M?hlenpfordtstra?e 23 > D-38106 Braunschweig > > T +49 (0)531 391-2129 > F +49 (0)531 391-9502 > birger.haarbrandt at plri.de > http://www.plri.de > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20140204/76c0ff91/attachment-0001.html> > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at lists.openehr.org > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org > > ------------------------------ > > End of openEHR-technical Digest, Vol 24, Issue 1 > ************************************************
