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 can perfectly be represented in a static data schema. > Furthermore, there is lots of catalogue data that fits best into > relational tables. (Another important reason is, that our abailable > ETL an BI tools are optimized to work with SQL Server...) Ah, yes, about the same reasons as ours. Thanks for sharing! > Are both versions available as open source? Yesterday I took a look > at it (just the code) and was impressed by your work! Yes, they will be available as open source. > I'm wondering about it's capabilities to do validation of clinical > data against archetypes. Is it possible to deserialize openEHR XML > and check it for consistency or is it a one way ticket so far? Yes it is possible. Although it is not implemented yet. So far I have only implemented serialization to openEHR XML. Deserialization will be possible, but only for the archetypes known to MEDrecord. In fact, the original idea was to just create an API which (de)serialized everything to/from XML and just stores the XML. Regards, Ralph van Etten MEDvision360 -- This e-mail message is intended exclusively for the addressee(s). Please inform us immediately if you are not the addressee.
