Persistence of Compositions

2014-02-06 Thread Birger Haarbrandt
Hi Ralph, > Am 05.02.2014 um 20:34 schrieb Ralph van Etten : > > On 02/04/14 17:33, Birger Haarbrandt wrote: > > Hi Birger, > >> 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

Persistence of Compositions

2014-02-06 Thread Ralph van Etten
On 02/05/14 20:36, Bert Verhees wrote: Hi Bert, Thanks for your kind words. > You write: > "Of course there is room for improvement and maybe it is not enough to > implement all possibilities of OpenEHR " > > I don't know how to understand this. > Do you mean that, for the moment, it is not p

Persistence of Compositions

2014-02-06 Thread Diego Boscá
applications. Thank you very much for sharing :D > > > > > Regards, > > > > Ralph van Etten > > MEDvision360 > > > > > > Best, > > Birger > > > > -- > > This e-mail message is intended exclusively for the addressee(s). Please > > inform us immediately if you are not the addressee. > > > > ___ > > openEHR-technical mailing list > > openEHR-technical at lists.openehr.org > > > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org > > ___ > openEHR-technical mailing list > openEHR-technical at lists.openehr.org > > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org > -- next part -- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20140206/ea63bc78/attachment-0001.html>

Persistence of Compositions

2014-02-06 Thread Bert Verhees
Ralph van Etten schreef op 6-2-2014 9:45: > At the moment only the functionality required for our use cases is > implemented. For instance, OpenEHR allows archetype slots with > wildcards. This is something we do not need for our usecases and > therefore we have not implemented it yet. There are ma

Persistence of Compositions

2014-02-06 Thread Bert Verhees
> > openEHR-technical mailing list > > openEHR-technical at lists.openehr.org > <mailto:openEHR-technical at lists.openehr.org> > > > > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org > > ___ > openEHR-technical mailing list > openEHR-technical at lists.openehr.org > <mailto:openEHR-technical at lists.openehr.org> > > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org > > > > > ___ > openEHR-technical mailing list > openEHR-technical at lists.openehr.org > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org -- next part -- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20140206/655ba3dd/attachment.html>

Persistence of Compositions

2014-02-06 Thread Ralph van Etten
Hi Birger, On 02/06/14 08:26, Birger Haarbrandt wrote: >> Could you tell more about why a XML database does not serve your >> needs? > > That is because we got both complex and simple data structures. For > example, we got millions of equally structured demographic data and > lab values that ca

Persistence of Compositions

2014-02-06 Thread Diego Boscá
t;> applications. Thank you very much for sharing :D >> >> > >> > Regards, >> > >> > Ralph van Etten >> > MEDvision360 >> > >> > >> >> Best, >> >> Birger >> >> >> > -- >> > This e-mail message is intended exclusively for the addressee(s). Please >> > inform us immediately if you are not the addressee. >> > >> > ___ >> > openEHR-technical mailing list >> > openEHR-technical at lists.openehr.org >> > >> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org >> >> ___ >> openEHR-technical mailing list >> openEHR-technical at lists.openehr.org >> >> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org >> > > > > ___ > openEHR-technical mailing listopenEHR-technical at > lists.openehr.orghttp://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org > > > > ___ > openEHR-technical mailing list > openEHR-technical at lists.openehr.org > > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org > -- next part -- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20140206/4983f585/attachment.html>

Persistence of Compositions

2014-02-06 Thread Bert Verhees
ssee(s). Please >> > inform us immediately if you are not the addressee. >> > >> > ___ >> > openEHR-technical mailing list >> > openEHR-technical at lists.openehr.org >> <mailto:openEHR-technical at lists.openehr.org> >> > >> >> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org >> >> ___ >> openEHR-technical mailing list >> openEHR-technical at lists.openehr.org >> <mailto:openEHR-technical at lists.openehr.org> >> >> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org >> >> >> >> >> ___ >> openEHR-technical mailing list >> openEHR-technical at lists.openehr.org <mailto:openEHR-technical at >> lists.openehr.org> >> >> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org > > > ___ > openEHR-technical mailing list > openEHR-technical at lists.openehr.org > <mailto:openEHR-technical at lists.openehr.org> > > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org > > > > > ___ > openEHR-technical mailing list > openEHR-technical at lists.openehr.org > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org -- next part -- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20140206/a8e0fa00/attachment-0001.html>