Hi Birger, I work for Ocean Informatics and am sorry to hear you have not heard back from my colleagues - I have emailed you privately to follow this up. I am a clinical modeller and although I have a good grasp of openEHR technology I am not technical so take what you wish from my comments!!
Although you are correct that in theory you do not need many of the advanced features of a n openEHR server (clinical data repository) and might be able to do something simple as you have suggested, as Berty has suggested, this can be a tricky area and I would urge you to take advantage of some of the existing implementations that are in existence. openEHR can be a complex technology tand there are myriad academic attempts to do something quick and simple that tend to consume a great deal of resource and divert from the key task at hand. Peter Linhardt's offer is well worth considering since his team have practical experience of persisting and querying openEHR data. The approach I would take, (as used by Peter's team) is based on the Ocean Template Data Document approach but has no dependency on the Ocean server or any other paid-for product. There are several other non-Ocean products which use an identical approach. The basic approach is to create a template using the Ocean Template Designer which aligns to your input data as closely as possible. This template is used to export a Template Data SChema (XSD), and from that a Template data Document (instance data) is created by populating (normally via xslt) from your source data. There is a standard transform (from any TDS) to 'canonical' openEHR XML, available at http://openehr.codeplex.com/SourceControl/latest#TRUNK/TemplateDataDocument/src/TDDAdapter/XSL/TDD_to_openEHR.xsl You can then persist this to any openEHR xml-conformant server or datastore. There are other approaches such as that taken by Pablo Pazos https://code.google.com/p/open-ehr-gen-framework/ which uses a different way of creating templates. The key requirements I think you need to consider are 1. Can I easily persist and retreive openEHR compositions without getting deepely embroiled in coding? 2. Can I query the data easily (critical in your case), preferably using AQL Archetype Query Language? I still think you would be better to approach some existing server providers (or take up Peter's offer) to save you considerable effort. Once you have a better understanding of openEHR technologies, you might well decide to 'roll your own' persistence layer but that would be my last resort not my first! I hope I have managed to avoid any commercial bias here. To my knowledge at least 3 other openEHR developers are using the TDD approach. Ian On 2 September 2013 10:11, Birger Haarbrandt <birger.haarbrandt at plri.de>wrote: > Hello everybody, > > at first I'd like to introduce myself: I'm a research associate the > University of Braunschweig, Germany. We are involved in a clinical data > warehouse project at Hannover Medical School. I got a background in > biomedical informatics and computer science. > > We would like to use openEHR to generate a somewhat generic data model > that serves the need of researchers in translational medicine. I have an > architecture in mind as follows: > > Specialists create archetypes and templates for their specific domains. > Then an XSD is created from the particular template. We derive a XML > document of the XSD that is filled with data of our source systems (SAP, > HL7 v2 messages etc.) with the help of ETL-Tools (data cleaning and > stuff...). Then, the document gets validated with help of the XSD and gets > stored persistently into a XML Database (or maybe MS SQL Server 2012, we > would need to evaluate its limitations). This consolidated database serves > as repository for the creation of dedicated data marts. > > As far as I understand the architecture of openEHR, we don't need any of > the openEHR 'server' functions when our goal is to store data according to > openEHR reference model and data is just for research purposes. Is there a > trial version of the Template Designer? The sales people of Ocean Software > didn't respond yet. > > This is of course just a rough sketch but I would highly appreciate some > comments and thoughts about this approach. To be honst: at first I wanted > to give the RIM a try. Then I tried their tools. End of story. > > With kind regards, > > -- > *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 > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at lists.openehr.org > > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org > -- Dr Ian McNicoll office +44 (0)1536 414 994 fax +44 (0)1536 516317 mobile +44 (0)775 209 7859 skype ianmcnicoll ian.mcnicoll at oceaninformatics.com Clinical Modelling Consultant, Ocean Informatics, UK Director openEHR Foundation www.openehr.org/knowledge Honorary Senior Research Associate, CHIME, UCL SCIMP Working Group, NHS Scotland BCS Primary Health Care www.phcsg.org -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130902/62f0f645/attachment-0001.html>
