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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130902/e4b40bdf/attachment-0001.html>

Reply via email to